Your system contains several standard access role name rules recommended
for use, including the ones described here. These are referenced in standard Access of Role to Object rules to
control the classes that users with these access role names can see, update,
and so on.
Name
|
Purpose
|
More
|
| PegaRules:AutoTest
|
Access to use Automated Unit Testing |
|
| PegaRULES:Batch
|
For background requestors, including agents. |
agent
|
| PegaRULES:Guest
|
Unauthenticated access with minimal access. |
guest
|
| PegaRULES:Guest-Maximum
|
Unauthenticated access with more capabilities,
including the ability to open and update work objects assigned to
self. |
|
| PegaRULES:SysAdm4
|
Developer with full capabilities. |
|
| PegaRULES:User1
|
Application user with limited capabilities. May
not perform assignments on worklists other than own worklist.
Typically uses the Get Most Urgent button to obtain the assignments to work
on next. MARIK 2/21/06 |
|
| PegaRULES:User4
|
User with broader capabilities. Can open any work
object in the application. Can perform assignments only on own worklists. MARIK 4/15/10 |
|
| PegaRULES:WorkMgr4
|
R-9965 C-494Work manager with full
capabilities. Able to update basic the leftmost tab of delegated
rules. |
How
to build for change. |
| PegaRULES:SysArch4
|
For a business analyst or a system architect who defines processes, classes and properties (Data Model category) and may develop activities. MARIK 4/15/10 Updated for 6.1 SP2 GRP-18342 |
|
| PegaRULES:ProArch4
|
For a process architect who focuses on flows and other rules in the Process and User Interface categories. MARIK 4/15/10 |
|
Deprecated and reserved access roles
These standard access roles are reserved, or retained for Version 4
compatibility. They are deprecated for new development.
Name
|
Purpose
|
| PegaRULES:SysAdm5
|
Reserved. Do not use. KHATV 4/8/10 |
| PegaRULES:Basics
|
Not used. ??? |
About Access Role Names
Atlas
home
Atlas
— Standard Access Roles