More about Access Group data instances
When effective
After you save an Access Group form, active requestor sessions on the current node that are associated with that access group are immediately updated. Requestors at other nodes in a cluster are updated when the next system pulse occurs on their node.
Security audits
Using the optional security audit feature, your application can present in the History display which values were added, updated, or removed from the data object, for selected data classes.
Facilities provided to unauthenticated (guest) requestors
Guest users—also known as unauthenticated requestors—typically have access to only the rules in the rulesets in the PRPC:Unauthenticated access group, as referenced in the Requestor type instance named pega.BROWSER.
The clipboard for a guest requestor does not include pages for the Operator ID, organization, division, or organization unit.
The default time-out period for an idle guest requestor is one minute.
- As you develop applications and operate your system, the SmartPrompt feature displays those rules that you have access to. When completing an access group form, choose rules (for the default Portal and Roles fields) that the operators associated with this access group at runtime can access. Rule visibility for these operators is deterapplication rule listed on the Definition tab of their access group or groups. Their RuleSet list may contain fewer RuleSets and Versions — or different RuleSets and Versions — than your own RuleSet list.
- To change access groups programmatically, a requestor can call an activity that uses the PublicAPI function getAuthorizationHandle(), and then applies the Java method setCurrentAccessGroup().