Back Forward More about Dynamic System Settings data instances
 

  1. About 
  2. New 
  3. Settings 
  4. History 
  5. More... 

Contrasting system setting rules with dynamic system setting data instances

Use System Setting rules (Rule-Admin-System-Settings rule type), not Dynamic System Settings (Data-Admin-System-Settings) to hold important constant values in your application that are the same in every deployed copy of your application. Use Dynamic System Settings when the values may differ from site to site — such as URLs, user names, or port numbers — and may be set programmatically.

Creating new dynamic system settings

Your application can create, set, or query instances of this class using Java methods in the PublicAPI PRSystemSettings interface:

Accessing dynamic system settings from a Data Page

The standard DataPages rule Declare_CachedDataSystemSettings creates a Node-scope declare page, refreshed every 10 minutes, containing your system settings. Fetching a value from this in-memory page — by referencing a property — is faster than using the PublicAPI functions listed above, as no database accesses are required. If your application includes dynamic system settings that are frequently accessed, you can override the default load activity LoadDataSystemSettings for this Data Page rule to include them on the data page rule. In your activity, use the function rule @getDataSystemSetting() to look up the value.

Notes

Some Dynamic System Settings instances are created automatically during installation or upgrade of a PRPC system.

Related topics About System Settings rules
About Data Pages
Standard rules Atlas — Initial Dynamic System Settings data instances

Up About Dynamic System Settings data instances