|
|
More about Application rulesWhere used at runtime
During log in, the system assembles a RuleSet list for a user from application rules referenced in:
- A requestor type instance (Data-Admin-Requestor)
- The user's organization (Data-Admin-Organization)
- The user's division (Data-Admin-OrgDivision)
- The user's access groups (Data-Admin-Operator-AccessGroup)
When effective
In a production setting, use care in updating application rules. After you save an Application form, active requestor sessions on the current node that are associated with that application are immediately updated, the equivalent of logging out and logging in again. This can affect not only the RuleSet list of these requestor sessions but other security and operational factors determined during log in, such as locale, organization, and operator availability. Requestor sessions at other nodes in a cluster are similarly updated when the next system pulse occurs on their node. GAJNJ 5/22/06 and KHATV 6/14/06
Security audits
Using the optional security audit feature, your application can present in the History Details display which values were added, updated, or removed from this rule when it was saved. C-2644 See How to enable security auditing for rule or data changes.
Version locking
Although application rules are associated with a RuleSet, they do not belong to any specific version of that RuleSet. Locking a RuleSet version (by checking the Lock this Version box) does not prevent later changes to application rules associated with the RuleSet.
Clipboard page
The reserved page Application on the clipboard holds most of the contents of a requestor's current application rule. PROJ-1008 GRP-368.
|
RuleSet list |
|
How the system assembles and uses your RuleSet list |
|
Atlas — Standard application rules |
About Application rules