You can define settings for an access group that are related to run-time rulesets and accessibility for users and other requestors who belong to an access group.
To provide users with more accessible versions of several standard harness, section,
and flow actions , select
Enable accessibility add-on.
To provide maximum accessibility support, include the PegaWAI ruleset in the Production Rulesets list for such users. For more information, see Understanding accessibility.
For users who belong to the access group and who have design-time permission in a
production setting, provide the names of one or more
that contain the updated rules.
For example, in a production setting, you can identify one ruleset and version that remains unlocked and holds only rules that are expected to change often. Such rules can be delegated to management. A ruleset with this purpose is sometimes called a local-only or production ruleset.
As a best practice for good security, and to avoid a warning when you save the Access Group form, select from the ruleset versions that appear in the Production Rulesets (customization) array on the Definition tab of the Application rule.
The system uses this information at log-on time to assemble the ruleset list for this user. The order of your entries in this array affects rule resolution. At login, the system appends these entries to the top of your ruleset list, but starting at the bottom of this array. The order of rows in this array becomes the order in which they appear in the ruleset list.
Except for access groups that have the PegaRULES:WorkUser4 role, include at least one ruleset version that is not locked. If all ruleset versions that a user can access are locked, the user cannot create new rules. Typically, managers have access to a local customized ruleset for storing only those rules that are personal, customized versions of reports.