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.

Specifying a client-based access control rule on an abstract class

Updated on July 1, 2021

You can define client-based access control (CBAC) rules on concrete classes and on abstract classes. At run time, Pega Platform combines multiple CBAC rules, starting from the concrete class. If the CBAC rule is on an abstract class and not on any of its concrete classes, you must do extra configuration to ensure that the abstract class is included.

  1. Create a data transform and append the abstract class name to .pxResults.
    For example: You have defined a CBAC rule on the abstract class MyApp-Work-AbsClass but not on any of its concrete classes. Create a data transform named MyCBACTransform with the values shown below.
    Data transform stepActionTargetRelationSource
    1Append and Map to.pxResultsa new page
    1.1Set.pyClassNameequal toMyApp-Work-AbsClass
  2. Customize the data page D_pyCBACPolicyClassList by adding the data transform that you created in step 1 as a data source.
    For example: For the data transform example in step 1 above, update the data page with the following values.
    1. In the Source list, click Data Transform.
    2. In the Data transform name field, enter MyCBACTransform.

    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?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us