Skip to main content

 –

Configuring assigned to assertions

Suggest edit Updated on April 13, 2020

For flows and case types, you can use the assigned to assertion to verify that an assignment is routed to the appropriate work queue or operator.

If you have multiple assignments on a flow or test case, you can route each assignment to an operator ID or work queue. Clipboard pages are created for each assignment under the pyWorkPage page and capture the assignment details, including the operator ID or work queue to which the assignment was routed. The assigned to assertion compares the operator ID or work queue to the last assignment that is configured on the flow or case type, which depends on where you stop recording the flow or case type.

For example, your flow has a Customer Details assignment, which is routed to the operator ID johnsmith. It also has a subprocess with an Account Information assignment, which is routed to the account_processing work queue.

If you record only the Customer Details assignment, the assigned to value is johnsmith. If you also record the Account Information assignment, the assigned to value is account_processing.

Before you begin: Open the unit test case. For more information, see Opening a unit test case.

  1. On the bottom of the Definition tab, click Add expected result.

  2. From the Assertion type list, select Assigned to.

  3. From the Assigned to list, select Operator or Work queue.

  4. Select a comparator from the Comparator list.

  5. In the Value field, press the Down Arrow key and select the operator ID or work queue.

  6. Optional:

    To add a comment, click the Add comment icon, enter a comment, and click OK.

  7. Click Save.

Related Content

Article

Converting unit tests to test cases
Did you find this content helpful? YesNo

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