Question
Common Wealth Bank of Australia
AU
Last activity: 1 Feb 2016 4:08 EST
Pega 7.1.9 - Customizing status definition
Our users are insisting to use their own definition of statuses such as Draft, Publish, Closed instead of Pega default prefixes like New, Pending , Completed , Resolved-.
We have suggested to use pega default status definition as a prefix, so that it can be Open-Draft, Open-Publish, Resolved-Completed but users are particular on the status definition provided by them.
What is the best approach to be followed here?
- Can we customize and create our own property in our work class with user defined statuses? or
- Create a mapping between pyStatuswork and the Custom property? or
- Advise the users to strictly use the pega defined prefixes? or
- Do we have any other options?
Please advise.
Accepted Solution
Infosys
AU
I think localising field values for statuses (pyStatusWork) should be simplest and safest solution. By this, in the database statuses can always be having Pega defined prefixes like Open-, Resolved- etc. but for the user display values can be Draft, Closed etc.
I hope this helps.
Murali...
Pegasystems Inc.
IN
Hi Vidhya, Good morning!
creating field values (pyStatusWork) with pre-fixes (Open-Draft, Open-Publish, Resolved-Completed) may help in not hitting unknowns.
>>> Can we customize and create our own property in our work class with user defined statuses?
- we could customized on display & run the background process (reading from clipboard) using PRPC values
>>> Create a mapping between pyStatuswork and the Custom property? or
- a declarative rule should be applied as you said which need to be in sync
>>> Advise the users to strictly use the pega defined prefixes? or
- probably yes because of less maintenance and more control with application statuses
Please share your thoughts/comments, Thank you!
psahukaru
Accepted Solution
Infosys
AU
I think localising field values for statuses (pyStatusWork) should be simplest and safest solution. By this, in the database statuses can always be having Pega defined prefixes like Open-, Resolved- etc. but for the user display values can be Draft, Closed etc.
I hope this helps.
Murali...
Common Wealth Bank of Australia
AU
Thanks Pahni, Murali and Vinay for the replies.
I will go ahead with the field values, that seems to be the good option for my requirement.