Access Role NamesCompleting the Create, Save As, or Specialization form

You are here: Reference > Rule types > Access Role Names > Access Role Names - Completing the New or Save As form

Access Role Names Completing the Create, Save As, or Specialization form
About New Role History More...

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 role name rule by selecting Access Role Name from the Security category.

Key parts:

Field

Description

Role Name

Enter an access role name. Choose a name that is unique system-wide, both in the current system and in other Pega 7 Platform systems that may later host this application, and that contains one colon character.

Use the format ApplicationName:RoleName when specifying an access role name; for example, Thorr:Administrator or Purchasing:Buyer. This allows you and others to ensure the name is unique across multiple applications.

Begin the name with a letter, and use only letters, numbers, the ampersand character, hyphens, and a single colon.

Enter a RuleSet Name and version. This information is used only by the Archive tools, not for rule resolution.

Access of Role to Object rules

For standard access roles such as PegaRULES:SysArch4 or PegaRULES:User4, the Pega 7 Platform includes corresponding standard Access of Role to Object rules, including a rule for @baseclass. If you create access roles, be sure to create a last-resort Access of Role to Object rule at @baseclass for that access role, so that the class inheritance search always ends successfully.

Rule resolution

Rule resolution does not apply to Access Role Name rules. Your system can contain at most one Access Role Name with a specific name.

Circumstanced versions are not supported by Access Role Name rules.

Open topic with navigation