Customize Agile Studio Status Lists and Values
My client has asked me to report on construction progress more granularly than the out-of-the-box Agile Studio (v 7.3.1) statuses allow. I'm sure I can leverage tags to do this, but would rather customize the values in the various status lists. Is there a way to do this?
Accepted Solution
Pegasystems Inc.
US
Pegasystems Inc.
IN
It is not possible to add new items to dropdowns, but existing items can be renamed by overriding the respective field values. For this customization they should have a ruleset
Accepted Solution
Pegasystems Inc.
US
I was able to add new values to status dropdowns using the existing case lifecycle stages. I didn't want to mess with the stages. It certainly isn't easy, intuitive, or end user friendly like other COTS solutions, but it is possible. You do need an unlocked ruleset, and some technical knowledge to do this, as it involves creating field-values, and editing when-rules.
Pegasystems Inc.
IN
Hello, thank you for your response and glad that you could meet your requirements.
Accenture
IT
Hi FORKC,
I have found the solution to your problem as it was also mine.
You have to follow these steps.
1) Create your own statuses
Create new field values for pyStatusWork and StatusName with status values you need and put them in the specific class you need them (e.g. PegaProjMgmt-Work-UserStory, PegaProjMgmt-Work-UserStory-Epic and so on...)
2) Modified a when condition
Within the DTs used to populate the status dropdown, Pega uses the following when rules
- IdeaStatuses
- SizingStatuses
- ReadyStatuses
- IsNotInProgressStatus
You have to modify them adding a condition as you need. For example, my need was to add Pending-Prototyping status in the sizing stage for User Stories, so I have modified the SizingStatuses when rule, adding a new condition (see the condition D in the attached when rule screenshot example)
3) Flush data pages
You have to flush the following Data Pages in order to "update" the dropdowns, in the following order.
- D_WorkStatusList
- D_WorkStatusListForNonSprintUserStories
- D_WorkStatusListForInSprintUserStories
- D_WorkStatusListEpic
That's almost all and, for me, it works. Just try and then let me know if this solution works also for you.
Hi FORKC,
I have found the solution to your problem as it was also mine.
You have to follow these steps.
1) Create your own statuses
Create new field values for pyStatusWork and StatusName with status values you need and put them in the specific class you need them (e.g. PegaProjMgmt-Work-UserStory, PegaProjMgmt-Work-UserStory-Epic and so on...)
2) Modified a when condition
Within the DTs used to populate the status dropdown, Pega uses the following when rules
- IdeaStatuses
- SizingStatuses
- ReadyStatuses
- IsNotInProgressStatus
You have to modify them adding a condition as you need. For example, my need was to add Pending-Prototyping status in the sizing stage for User Stories, so I have modified the SizingStatuses when rule, adding a new condition (see the condition D in the attached when rule screenshot example)
3) Flush data pages
You have to flush the following Data Pages in order to "update" the dropdowns, in the following order.
- D_WorkStatusList
- D_WorkStatusListForNonSprintUserStories
- D_WorkStatusListForInSprintUserStories
- D_WorkStatusListEpic
That's almost all and, for me, it works. Just try and then let me know if this solution works also for you.
Vicio
I was able to add new values to status dropdowns using the existing case lifecycle stages. I didn't want to mess with the stages. It certainly isn't easy, intuitive, or end user friendly like other COTS solutions, but it is possible. You do need an unlocked ruleset, and some technical knowledge to do this, as it involves creating field-values, and editing when-rules.