Working with the Assignments in Error report

After a flow execution creates an assignment, many types of rules other than flow rules may operate on the assignment, including:

• Service level rules, which define intervals and escalation
• Harness rules for displaying the assignment and accepting user input
• Section, HTML, activity, and validation rules referenced in harness rules

When such rules, operating on an assignment, encounter problems, the system:

1. Changes the Instruction text on the assignment to begin with the word Error: followed by a problem description.
2. Includes the assignment on one of the two reports accessed from this panel, depending on whether the assignment resides on an operator worklist or in a workbasket.

You may need to update a flow rule, a router activity, add a missing workbasket, and so on.

In a production setting, review and diagnose every problem assignment to insure data integrity.

Assignments are grouped by the type of error encountered:

Error	Description and possible causes
Agent SLA Activity	The Pega-ProCom agent or another agent cannot find the flow rule, the Operator ID data instance, an activity referenced in the service level rule MARIK 3/17/06 or another object needed to process an assignment. Confirm that the agent(s) have access to all the needed RuleSets and versions, through an access group.
Agent SLA Open	The Pega-ProCom agent or another agent cannot find the service level rule referenced in a flow. Confirm that the agent(s) have access to all the RuleSets and versions, through an access group.
Agent Work Object	The Pega-ProCom agent or another agent cannot find the work object referenced in an assignment.
Assignment Mismatch	Assignment details in the work object do not match data in an instance in the Assign-Worklist or Assign-Workbasket. PRKB-21740 See Pega Developer Network article PRKB-21740 Troubleshooting: Error:Assign Mismatch " when a Before This Action activity transfers a work object.
Flow Not at Task	The assignment instance does not match any assignment shape in the flow rule. The flow rule may have be updated to rename or delete the assignment shape after the assignment was created.
Flow removed	The flow rule referenced in this assignment cannot be found.
Harness Fail	Problems were encountered in finding or processing a harness rule for this assignment.
Work Open	The work object referenced in the assignment cannot be opened, or the class (work type) cannot be found.

Click the plus sign to expand the group. Click any row to review the assignment.

After you have diagnosed and addressed a problem, select the Add box in one or more rows of this report. Then click a button to reflect your disposition of the issue.

Button	Result
Refresh	Update this report with the latest list of assignments with error.
Select All	Select the Add box for every row in the report.
Deselect All	Clear the Add box for every row in the report.
Clear Error   Status	Restore the previous value for the Instructions for this assignment. Remove this assignment from the report. The assignment remains on the worklist or workbasket as before.
Delete	Delete the assignment. Use this with caution; this does not restart flow execution or resolve the work object.

5.4 proj1218 As of Version 5.4, an operator can fix assignments that are missing from or have mismatching information on the pxFlow page.

Missing assignments

If an assignment is missing, the work object cannot be opened when a flow is initiated. Here is an example of the error message:

Unable to open an instance using the given inputs: ASSIGN-WORKLIST PEGASAMPLE W-12221!BASICPROCESS.

This error can occur after a work object is created and the flow rule is validated. This error is not displayed in your worklist or Assignments in Error report.

The error typically occurs when the property .pxAssignmentKey was deleted from table pc_assign_worklist or pc_assign_workbasket and therefore is not present on page pxFLow. To fix the null assignment, open the work object and start the flow by clicking the flow link. When the error message appears, click Restore This Assignment. When you run the flow again, a new assignment is created for the work object.

Assignment mismatches

An assignment mismatch error appears in the Assignments in Error report when assignment details in the work object do not match data in an instance in the Assign-Worklist or Assign-Workbasket. The error can be the result of the property .pxTaskName having been modified in table pc_assign_worklist or pc_assign_workbasket causing a mismatch on page pxFLow. Here is an example of the error message:

The work object references a different assignment than the current one.

To create the correct the mismatch, locate and open the item and click Repair This Assignment. When you run the flow again, the assignment is rebuilt matching .pxTaskName property with the property name on page pxFlow. (For examples, see Pega Developer Network article PRKB-25152 How to fix assignments that are deleted or do not match work objects.

Assignments can be repaired or recreated only when the page pxFlow is present and valid .

The Assignments with Errors In Workbaskets report lists assignments with errors routed to workbaskets that you can access.

This report operates similarly to the Assignments with Errors in Worklist report. See above instructions.