Troubleshooting Pega 1:1 Operations Manager

Use the following troubleshooting tips to help solve issues with the  Pega 1:1 Operations Manager workflow.

Issue: Pega 1:1 Operations Manager does not show custom action attributes during the Build stage of the workflow

This functionality will be implemented in a future release of Pega 1:1 Operations Manager. To see custom action attributes in version 8.4 of Pega 1:1 Operations Manager, extend the Build stage of the workflow to include the custom attributes section.

Issue: Assignments listed under work queues on the Home screen of the Pega 1:1 Operations Manager portal are missing task labels

No workaround is currently available. A future release of Pega 1:1 Operations Manager will address this issue.

Issue: Cannot edit change requests with a launch date

No workaround is currently available. A future hotfix will resolve this issue.

Issue: The list of change requests automatically refreshes the displayed change requests back to the first page

When a team leader clicks Edit prioritization on any page in the list of change requests other than the first page, the display refreshes back to the first page. As a workaround, you can manually navigate back to the originally displayed page.

Issue: In the Build stage, the preview panel always displays the change request rank as 10, even if the actual rank is different

No workaround is currently available. Instead, this issue requires a local change in your implementation layer. Please contact the Pega Product Team for guidance.

Issue: If a team lead submits the Review revision assignment for a withdrawn revision, instead of creating a new child, the withdrawn child case reopens

No workaround is currently available. Instead, this issue requires a local change in your implementation layer. Please contact the Pega Product Team for guidance.

Issue: If multiple operators select the same action on Update action screen at the same time, multiple active change requests will include the same rule

No workaround is currently available. Instead, this issue requires a local change in your implementation layer. Please contact the Pega Product Team for guidance.