Guidelines for extending Pega 1:1 Operations Manager
Some areas of Pega 1:1 Operations Manager are commonly extended during the implementation process, while others should be left as default for most implementations.
Recommended extension points
Review the following areas of Pega 1:1 Operations Manager and customize them to match your requirements:
- The mapping of properties and the UI of the Idea and Plan change request phases
- SLA details
- Routing
- Notifications
- Approval process
- Additional, non-default change request types
- Testing steps
Areas which should be left as default
In most cases, do not modify the following areas of Pega 1:1 Operations Manager:
- The built-in class definition and the class-to-table mapping
- The Build change request phase
- The integration between Pega 1:1 Operations Manager and the Revision Management functionality of Pega Platform
- Default change request types
Previous topic Implementing case types and attributes Next topic Testing and deploying application changes