Question
COFORGE DPA UK LTD
GB
Last activity: 7 Dec 2017 12:17 EST
Is it mandatory to set final status of work object starting from Resolved%?
Is it best practice or is it mandatory to set the resolved work object status set from ‘Resolved%’ ?
What will be impact on case management if this status is not starting from 'Resolved'?
***Moderator Edit: Vidyaranjan | Updated Categories***
TATA Consultancy Services
IN
Once the all case management process completed, the case must be moved to resolved status. Otherwise the case is open status. Its will impacting the reports and other tracking.
EPAM Systems, Inc.
ES
Adding to Nadimuthu, it will also impact the audit much of the OOTB activities depends on resolution status.
COFORGE DPA UK LTD
GB
I understand that there are OOB reports running on status. Keeping in mind that we are not using them.
Whenever any child case is resolved, does it search other child in the process and check the status starting from Resolved?
Is it best practice to set final status starting from 'Resolved%' or Is this mandatory to set status starting from 'Resolved% in case design?
Pegasystems Inc.
US
Hi Gaurav,
It is mandatory for child cases as pega maintains pxcoveredopencount property which is directly related to child case having Resolved% status. pxcoveredopencount is used at a lot of places and many customers tend to use it as well for their business usecases.
This is just a single example, there can be many examples for top case as well. So it is best you set it to Resolved%
Hope this clarifies.
-Ravi.