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. |
|
| PegaRULES:Guest-Maximum
|
Unauthenticated access with more capabilities, including the ability to open and update work items 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. |
|
| PegaRULES:User4
|
User with broader capabilities. Can open any work object in the application. Can perform assignments only on own worklists. |
|
| PegaRULES:WorkMgr4
|
Work manager with full capabilities. Able to update basic the leftmost tab of delegated rules. |
How to delegate a rule
|
| PegaRULES:SysArch4
|
For a business analyst or a system architect who defines processes, classes and properties (Data Model category) and may develop activities. |
|
| PegaRULES:ProArch4
|
For a process architect who focuses on flows and other rules in the Process and User Interface categories. |
|
| PegaRULES:EditorCollaborator
|
For collaborators that participate in development of the application as editors. Can view and change application assets. |
Inviting collaborators
|
| PegaRULES:ViewerCollaborator
|
For collaborators that participate in development of the application as reviewers. Can view application assets, but cannot change them. |
Inviting collaborators
|