Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Data pages - Understanding the access group field

Updated on May 4, 2020

This article describes behavior for Data Pages (PRPC 7.1 and newer) and Declare Pages (PRPC 5.1-6.3SP1).

The Access Group field (located on the Load Management tab of a data page in Pega 7 and on the Definition tab of a declare page in earlier versions of PRPC) identifies the access group that PRPC uses at runtime to locate the load activity that populates the page.

This access group must contain the appropriate RuleSets to provide access to the correct version of the Load Activity, which populates the clipboard with instances of the data page or declare page.

Suggested Approach

The Access Group field is visible only when the Page Scope field on the Definition tab is set to Node.

The field is available on the Load Management tab of a data page in Pega 7:

access group field

It is available on the Definition tab in PRPC 5.1-6.3 SP1:

This approach avoids the following design issues: many users may see one data page (declare pages) rule definition (for shared clipboard pages at the Node level). Due to rule resolution and different RuleSet Lists, these users would run different versions of the Load Activity to create that page, or have different rules called by that activity. Thus, the first user who called the data page (declare page) instance would set it up using their access group, with their Load Activity and their data.

The next user who accessed that instance might not have the same access group; if not, they would have to reload the page with their Load Activity and data.

To avoid continually reloading the page instance based on each user’s access group (which negates the concept of “shared”), the access group to use is set in the data (declare) page instance. When the first user calls this instance, the system switches to the specified access group and uses that RuleSet list to run the Load Activity and create the Declare pages. Once the page is created, the system switches the user back to their own access group.

Important: This means that whenever a user’s processing references a data (declare) page instance, that instance will contain data which has been loaded with the RuleSet list determined by the data (declare) page's access group – not necessarily what is available in the user’s RuleSet list. Changing your own access group to get different data on the page instance has no effect.

Select an access group that provides the RuleSets and versions which have all the appropriate rules to run the Load Activity.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us