Skip to main content

 –

Guidelines for extending Pega 1:1 Operations Manager

Suggest edit Updated on September 21, 2021

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 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
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us