Issue: New Pega 1:1 Operations Manager landing pages are not visible

If you use App Studio to create a new landing page for the Pega 1:1 Operations Manager portal, but the page is not visible when you log in to the portal, verify that your Pega 1:1 Operations Manager overlay application uses the same UI class as the Pega 1:1 Operations Manager implementation application.

To check the UI class of your application, do the following steps:

1. In Dev Studio, click the name of your application, and then click Definition.
2. Switch to the Cases & Data tab.
3. In the Associated Classes section, check the value in the UI class field.

Issue: The Items I follow widget remains empty even after creating a change request

To display your change requests in the Items I follow widget on the Home page, you must click the Follow icon after you create the change request. If you selected the Follow option, but the request still does not show in the widget, make sure that the work pool for your access group is set to PegaMKT-Work-Ops.

1. In Dev Studio, find and open the access group for your operator. For more information, see Viewing access groups and operators.
2. On the Advanced tab, verify that the work pool for the access group is set to PegaMKT-Work-Ops.

Issue: The NewChange request option is not available

If the NewChange request option does not show in the main navigation panel, ensure that the overlay application is correctly configured.

1. In Dev Studio, click on the name of your Pega 1:1 Operations Manager overlay application, and then click Definition.
2. In the Presentation section, verify that the selected skin is CosmosSkin.
3. On the Case & data tab, verify that the following case types are available and enabled:

   Name	Work ID prefix	Implementation class
   ChangeRequest	OpsCR-	PegaMKT-Work-Ops-ChangeRequest
   CreateAction	OpsCA-	PegaMKT-Work-Ops-CreateOffer
   UpdateAction	OpsUA-	PegaMKT-Work-Ops-UpdateOffer

Issue: Engagement policy details were not saved

If you enter engagement policy conditions, and then click Next without confirming the selection, the details that you enter may be lost. To confirm the selection, do the following steps:

1. In the engagement policy details, enter the required condition.
2. Click Use to confirm the selection after each required condition, as in the following figure:

Issue: Issues and groups do not load when you create a new change request

If you do not see any issues or groups when trying to create a new change request, check the following settings:

• Verify that the Pega 1:1 Operations Manager overlay application exists. For more information, see Creating and configuring the overlay application for Pega 1:1 Operations Manager.
• Verify that your access group can access the Pega 1:1 Operations Manager overlay application. For more information, see Creating operator accounts in Pega 1:1 Operations Manager.
• Check the Next-Best-Action Designer configuration for your Pega Customer Decision Hub implementation application to make sure that issues and groups have been configured on the Taxonomy tab. For more information, see Next-Best-Action Designer taxonomy.
• Verify that the built-on Pega Customer Decision Hub application has at least one issue and one group in the Proposition Management hierarchy. For more information, see Verifying Pega 1:1 Operations Manager implementation.
• Verify that the pxDecisioningClass SR Class is configured in the same ruleset in both the overlay application and the Pega Customer Decision Hub application. For more information, see Verifying Pega 1:1 Operations Manager implementation.

Issue: Users cannot see their tasks in My Worklist and other work queues

If a case or assignment was created by an operator who had an incorrectly defined work group or team, or who is part of a team that does not have correctly defined work queues, the case or assignment may not be visible in the My Worklist queue and in other work queues. If you are unable to see assignments in your worklist, do the following steps:

1. In Dev Studio, click ConfigureOrg & SecurityOrganizationOperators.
2. Find and open the operator whose assignments do not show in the My Worklist queue.
3. On the Work tab, check the team that is selected in the Team field.
4. Log in to Pega 1:1 Operations Manager as a user with the your overlay application:TeamLead access group.
5. In the left navigation pane, click My Teams.
6. Ensure that the appropriate work queues have been added to each team. For more information, see Configuring a team in Pega 1:1 Operations Manager.
7. For existing cases that were created under the wrong work group, either withdraw and recreate them, or manage them without using the My worklist widget, by opening the cases directly from the Change Request landing page.

Issue: An NBA Specialist cannot see any tasks associated with a change request

The tasks might have already been completed by another user in the user with the your overlay application:NBASpecialist access group. To refresh the page, click ActionsRefresh.

Issue: After all build stage tasks are completed, the change request status changes to Pending-Merge instead of Resolved-Completed

An operator in the <your overlay application>:RevisionManager access group has opened the revision associated with the change request or the revision is in inactive state (due date has been passed). This locks the revision and causes the change request status to remain as Pending-Merge while the revision is locked. Once the lock of the revision is released by the revision manager by closing the opened revision, or the revision is updated to an active state by updating the due date, change request will proceed to the next stage.

Issue: After all change request tasks are completed, the change request status changes to Pending-Failed

One or more of the tasks associated with the change request has an error that caused the build to fail. To resolve it, send the change request back to an NBA Specialist.

1. Log in to Pega 1:1 Operations Manager as a user with the your overlay application:TeamLead access group.
2. Open the change request that is in Pending-Failed status.
3. Open the Resolve build failure task.
4. To see the reason for the build failure, click Show more.
5. Return the change request to an NBA Specialist for a fix by clicking Return to build and fix.
6. (Optional) Team lead can also move the change request to Plan stage by using Actions from left navigation or the option to reject changes and move to plan.

Issue: Cannot save criteria to a When condition in the library during the Create Engagement Policy task in the Build stage

This issue may happen if a When condition with the same name already exists in the application. Verify that you use a unique name for the When condition before you save the condition to the library.

Issue: Bundle details are not visible in a change request after enabling the Bundle setting on the Settings page

This issue may happen for change requests that were created before the Bundle setting was first enabled. Bundle details are only visible for change requests that were created after you enabled the setting.

Issue: No option to add Peer reviewer on the screen in the Plan stage

Click on the stakeholder’s widget and select Peer reviewer option from the drop-down menu and add the peer reviewer.

Issue: Error while submitting the Edit Rank task in plan stage

Go to Operations ManagerSettings page and select any user as the revision manager from the list. Click Save and proceed with the change request submission.

Issue: Not able to select the persona for running the validation

This can happen when data transform for the persona is missing details for the context. To resolve this update data transform to include properties adhering to context dictionary, refer to data transform <Primary Context>Persona for reference.

Issue: Some properties are not shown for the persona

By default, there are 5 properties shown for every persona based on the properties selected in the engagement policy task.

Issue: Multiple account details are not visible for the persona

Click on the preview of the persona, move to accounts tab, then click on any account which needs to be previewed.

Issue: Change request is moved to build stage when a peer review task is rejected

This is an expected behavior. When the peer review task is rejected, all the tasks which are not completed will remain open and the configure engagement policy task will be reopened to allow work on the review comments added during the rejection of peer review task.

Issue: Team manager cannot see the work queue in the My worklist list in the Home portal

This issue might occur if the operator account of the team manager is not associated with any team. To solve this issue:

1. Edit the operator account of the team manager.
2. On the Work tab, specify the team that this operator manages.

Issue: Unable to withdraw or update a revision

This can happen if you had no user with default Revision manager access group when you created the revision. You can confirm this by checking Created by and Assigned to field values being empty on the details section of the revision. To resolve this issue:

1. Do a private check out of WHEN rule pyIsInitiator (class: RevisionManagement-Work).
2. Update the condition to return True.
3. Perform a private check out of Validate rule (class: Data-Party) by selecting Edit on the condition and deselecting the Required and Continue validation checkboxes.
4. Reopen the revision and Withdraw the action.

Issue: While updating an existing treatment, system does not show internal email treatments for selection

• A standard change request supports creating an action with an internal email treatment. You need to create a standard change request by using the Revision management landing page.
  Note: Pega 1:1 Operations Manager change request does not cover the internal email treatment so you cannot create an action with internal email treatment using the Pega 1:1 Operations Manager. This issue will be fixed in an upcoming release.
• A standard change request supports updating the internal email treatment. You need to create a standard change request by using the Revision management landing page.
  Note: Pega 1:1 Operations Manager change request does not cover internal email treatment so you cannot edit an internal email treatment using the Pega 1:1 Operations Manager and the option will not present an internal email treatment for selection.

Issue: Action preview shows all available treatments but there is no content visible when the internal email treatment is clicked

The preview of an internal email treatment type is not supported in Pega 1:1 Operations Manager.

Issue: On clicking Save to Library, the When rule is not saved and the pop-up window does not close

This issue can occur if you try to save a When rule that has the same name as a deleted When rule, because deleting the When rule does not remove the Relevant Record entry for that rule. To resolve this issue:

1. In Dev Studio, search for and Data-Tag-RelevantRecord.
2. Search for the When rule name.
3. Delete the Relevant Record for the When rule.

Issue: The Build stage fails when engagement policy conditions include a Strategy/When rule, and the tracer shows the error message "Unable to open an instance using the given inputs: pxObjClass = "Rule-Decision-Strategy/Rule-Obj-When"

This issue can occur if you try to save a Strategy/When rule that has the same name as a deleted Strategy/When rule, because deleting the Strategy/When rule does not remove the Relevant Record entry for that rule.

To resolve this issue:

1. In Dev Studio, search for and Data-Tag-RelevantRecord.
2. Search for the Strategy/When rule name.
3. Delete the Relevant Record for the Strategy/When rule.

Issue: Next-Best-Action Designer rules are not available for creating a standard change request

This issue occurs if you had not included the Next-Best-Action Designer rules in the Overlay application during the initial deployment.

To resolve this issue:

1. Log into your Development instance as a CDH Admin.
2. Go to your Application overlay landing page.
3. Edit the overlay application and include all the Next-Best-Action Designer rules.
4. Package the updated ruleset and promote it on all of the higher instances.

Various issues with actions having a Customer Journey associated

Scenario 1

You create an operations change request (OPSCR-1) to update an action and add a Customer Journey. You move the change request to Resolved-Completed status.

You create an operations change request (OPSCR-2) to update the same action and add a Customer Journey.You move the change request to Resolved-Completed status. But when you withdraw the OPSCR-2, it will withdraw the OPSCR-1 changes related to the Customer Journey.

To solve this issue, create a follow up change request to update the same action. Make the necessary changes to Customer Journey, that needs to be packaged for deployment.

Scenario 2

You create a standard change request (CR-1) to update an action and add a Customer Journey. You move the change request to Resolved-Completed status.

When you withdraw the CR-1 it will not revert changes related to Customer Journey.

To solve this issue, create a follow up standard change request to update the same action. Make the necessary changes to Customer Journey, that needs to be packaged for deployment.

Scenario 3

You create a standard change request (CR-1) to update Next-Best-Action configuration rule, and add or remove the Customer Journey stages. You move the change request to Resolved-Completed status.

When you withdraw the CR-1 it will not revert changes related to Customer Journey stages.

To solve this issue, create a follow up standard change request to update the same Next-Best-Action configuration rule. Make the necessary changes to Customer Journey, that needs to be packaged for deployment.

Issue: Unable to use new group created by using OpsMT or CR

You cannot update the Engagement policy configuration rule for a newly created group of an existing issue by using the Other (OpsMT) change request type, or Standard change request (CR), because the artifact-specific rules (for example, Strategy) are not created and not defined.

To resolve this issue:

1. Log in as a Revision Manager and update Next-Best-Action rule by using Standard change request (CR). Create a new group to an existing issue.

   Note: You can also create new group by using the Other type change request.
2. Complete and submit the change request.
3. Navigate to the Next-Best-Action Designer landing page and click the Engagement policy tab.
4. Select the newly created group and click Edit.
5. Click Save.
6. Add the newly created group (Next-Best-Action configuration rule) and complete the revision.

   Result: Engagement Policy configuration rule will be defined for the newly created group.

Issue: Unable to use All Issue/All groups for the first time

You cannot update the Engagement policy configuration rule for All Issue/All group for the first time, because the artifact-specific rules (for example, Strategy) are not created and not defined.

To resolve this issue:

1. Log in as an NBA Designer.
2. Navigate to the Next-Best-Action Designer landing page and click the Engagement policy tab.
3. Select All Issue/All group and click Edit.
4. Click Save.
5. Log in as Revision Manager and add the All Issue/All Group (Next-Best-Action configuration rule) and complete the revision.

   Result: Engagement Policy configuration rule will be defined for All Issue/All group.