Question
EPAM Systems
CA
Last activity: 19 Jun 2017 15:43 EDT
After Rejection same case should not be picked by same operator from Workbasket
Hi Team,
I have a requirement where case is present in WB and if any user is getting that case and rejecting then same case is again going back to same WB.
now Rejected case should not be picked by same Operator again and rejected operator can be multiple for a same case.So what would be best design to accomplish this requirement ?
Thanks,
Lalit
Accepted Solution
PEG
IN
in otherway, Work history table will have details of the Rejection notes and the operator who has done rejection
pyMessageKey , Pyperformer columns will have the details.
when an user clicked on an Rejection Flow action, in pre-processing activity of flow action, get the records from history table and compare the performer value with current user details. if it matches then you can Show message like "You already rejected once"
Wipro
US
Hi Lalit,
You can extend work table with one more column for storing the operator list who rejected the case.
Whenever reject action is taken updated the property with a delimiter(like ',' '|'..etc) separated values of operators.
In report definition for displaying records you can use "OperatorList" does not contains "pyUserIdentifier" as filter condition.
Please let us know if you find any other approach to handle it.
Hope it helps.
Thanks,
Ananda Bhat
Wipro
US
Hi Lalit,
True, It will be little more expensive in terms of processing time.
But should not be an issue as long as you are
- creating report definition in Assign- class and joining with work- class
- using pagination to display limited number of records at a time
To reduce this you can try to add new column to Assign- class.
But to achieve the requirements need to extend few OOTB activities, which need to be handled carefully as it will be executed for all assignments.
Thanks,
Ananda Bhat
Accepted Solution
PEG
IN
in otherway, Work history table will have details of the Rejection notes and the operator who has done rejection
pyMessageKey , Pyperformer columns will have the details.
when an user clicked on an Rejection Flow action, in pre-processing activity of flow action, get the records from history table and compare the performer value with current user details. if it matches then you can Show message like "You already rejected once"