Access Deny rules
|
|
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 may copy data instances but they do not support specialization as they are not versioned.
Based on your use case, the Create, Save As, or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:
This information identifies the key parts and options that are applicable to the record type you are creating.
Create an Access Deny rule by selecting Access Deny from the Security category.
An Access Deny rule has two key parts. The key links an access role with a class:
Field |
Description |
| Role Name |
Enter an access role name (Rule-Access-Role-Name rule type). |
| Applies To |
Identify 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 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.