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.

Completing the New or Save As form for Access Deny rules

Updated on July 1, 2021

Access Deny rules – Completing the Create or Save As form

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Create an Access Deny rule by selecting Access Deny from the Security category.

Key parts

An Access Deny rule has two key parts. The key links an access role with a class:

FieldDescription
Role Name Enter an access role name ( Rule-Access-Role-Name rule type).
Applies ToIdentify an abstract or concrete class to empower users who hold this access role to have some access to that class.

Specify a RuleSet Name. The RuleSet Name is used only by the Archive tools when creating or importing a ZIP file.

Rule resolution

Rule resolution does not apply to Access Deny rules. Your system can contain at most one Access Deny rule for each Applies To class and Role Name combination.

Class inheritance does not apply. Create a rule for each affected class.

About Access Deny rules

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.

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

Close Deprecation Notice
Contact us