Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Get Next Work customization

Customizing Get Next Work

You can customize Get Next Work processing to meet the needs of your application and your business operations. The most common customization requirement is adjusting the prioritization of work returned by Get Next Work. You change the prioritization of work by adjusting the assignment urgency.

Adjusting assignment urgency may not be a good long term solution however, since urgency can also be affected by other case or assignment urgency adjustments. A better long term solution is to adjust the filter criteria in the Assign-WorkBasket.GetNextWork and Assign-Worklist.GetNextWork list views. For example, you can sort by the assignment's create date or join the assignment with the case or another object to leverage other data for prioritization.

Sometimes different work groups have different Get Next Work requirements. When different business requirements exist, you customize each Get Next Work functionality to satisfy both sets of requirements. So a change implemented to satisfy a certain requirement should not affect the solution to a different requirement. For example, if assignments for gold-status customers should be prioritized for customer service representatives (CSRs), but not for the accounting team, then the change implemented to prioritize gold customers for CSRs must not affect the prioritization for the accounting team.

You can create several circumstanced list views if the requirements cannot be implemented in a single list view, or if a single list view is hard to understand and maintain.

Use the Assign-.GetNextWorkCriteria decision tree to filter the results returned by the GetNextWork list view. You can define and use your own when rules in the GetNextWorkCriteria decision tree. Create circumstanced versions of the GetNextWorkCriteria decision tree if needed.

Note: Using the GetNextWorkCriteria decision tree for filtering has performance impacts since items are iterated and opened one-by-one. Always ensure the GetNextWork list view performs the main filtering.

Circumstance Example:

GetNextWork ListView: Assign-WorkBasket

Circumstanced: OperatorID.pyWorkGroup = FacilityCoordinator@Booking

Criteria: .pxWorkGroup = FacilityCoordinator@Booking

Get These Fields: .pxUrgencyAssign Descending (1), pxCreateDateTime Ascending (2)

Show These Fields: .pxUrgencyAssign, pxCreateDateTime

Besides circumstancing the GetNextWork ListView, it is also possible to circumstance the GetNextWorkCriteria Decision Tree for a particular WorkGroup. Other alternatives exist such as specializing the getContentForGetNextWork Activity to call a different Decision rule to produce the desired results. When specializing any of these rules, it is important to implement changes efficiently to ensure results will be performant.

 


If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice