Question

2
Replies
19
Views
 Ben Passmore (BenP@QAC)
QA Consulting Services

QA Consulting Services
GB
BenP@QAC Member since 2015 4 posts
QA Consulting Services
Posted: February 12, 2021
Last activity: February 23, 2021
Posted: 12 Feb 2021 10:44 EST
Last activity: 23 Feb 2021 7:32 EST

Update case when retrieved by getnextwork

Report

We have a requirement to set certain flags on a case when its picked up by certain users through getnextwork.

Is there an extension point that we could use as most of the items that do the getting of the work seem to be Final internal rules (e.g. pzOpenAssignmentForGetNextWork / MoveToWorklist)

example 

user1 - flag1

user2 - flag2

user3 - no flag

 

user1 picks up case1 and sets flag1 on case1

user2 picks up case2 and sets flag2 on case2

user3 picks up case3, no flag set

Pega Platform 8.4.1 Case Management Government
Reply
Posted: 4 months ago
Posted: 14 Feb 2021 18:02 EST
Braam Smith (BraamCLSA)
PEGA
Partner Success Tech Lead - APAC
Pegasystems Inc.
AU
Report

@BenP@QAC

It's been years since I touched "Get Next", but Work-.GetNextWork itself is Available and its purpose appears to be predominantly to 'wrap' the inner Final activity getNextWorkObject that does all the 'work', then to orchestrate what Pega should do next based on whether work was found to do.

If you've done the digging already and can't find an extension point from within getNextWorkObject, you could consider:

  1. Determining how to check the result of getNextWorkObject to determine: a) whether work was found to do (hint: check the Jump configuration for the call to getNextWorkObject); and b) on what page it resides on the clipboard if found;  
  2. Specializing Work-.GetNextWork into your application where you need the extension point (it may have to remain on Work- ... depending on how GetNextWork is invoked);  
  3. Implementing an (empty) extension point in your application rulesets (again, on Work- depending on the findings from the previous step);  
  4. Adding a step to your specialized activity that calls your new extension point when work is found, using the work object page of the found work item as the step page (it looks like Step 4 onwards is the "happy path");  
  5. Class-specialize your extension point so that the flags for Case Type 1 can be configured (and tested) independently of the flags required for Case Type 2. Leave the extension point unspecialized for Case Types that need no special behaviour (Case Type 3).

As you are cloning a Platform rule, this introduces an upgrade risk should Pega decide to evolve the implementation of GetNextWork or the 'contract' of what getNextWorkObject does (where it puts its found work item, how it broadcasts that a match was found/not found). I recommend keeping a log of specialized platform rules like this so that scenarios for them are included in regression testing of upgrades. 

Reply