Question
Last activity: 19 Aug 2016 20:52 EDT
RSV Description not available - new rule form
old version(before 7) in new rule form we used to see RSV description which help us to identify the purpose of ruleset version.
New version we do not see it any more.
Project team with big size/multiple teams require this to avoid rule creation in wrong rulesets/versions.
Find the attachment for more details. Is there any hot fix /workaround to see RSV description in new rule form?
Thanks
Chiranjeevi
Accepted Solution
Updated: 5 May 2016 11:28 EDT
Pegasystems Inc.
US
Hi,
Don't think there is a hotfix or workaround for this requirement, as the pzChangeRuleset section is final.
As per design, the ruleset version description wasn't just shown on new Pega 7 rule forms and I feel developers must be aware of which ruleset name & version to choose from drop-down while creating/save-as rules.
Maybe Dharma Initiative Maxwell DeAngelis can weigh in here!
Agree developers should be aware of which ruleset and version they need to use. But in parallel environment, big teams, its very tough to track so its always good to have extra information so that atleast some instances we can avoid.
Pegasystems Inc.
US
Hi Majeti,
I don't know of a workaround or hotfix which would enable this. Mudit Sharma might know if there are extension points which could be utilized. However, I think this would be a pretty good enhancement.
Bence Magyar Linoy Alex. What are your thoughts on this? I know you guys had some longer term changes in mind for the new / save as experience, perhaps this can be considered when we start making designs?
-Ryan
Pegasystems Inc.
US
Is it just a question of displaying the description of the ruleset version? That seems like a relatively minor enhancement and it does make sense, although I would like to make sure that it is considered in context of what other information developers need to correctly locate these rules.
It is worth it for the engineering teams to look into a solution for this, but it could be that on further review we might chose to only fix this in a future release depending on the design that we want to implement. Please initiate the next steps for SWAT to look into this and follow up with designer studio leadership?
Our future plans in this space is to reduce the number of steps required to create a rule, allowing for more intelligent defaults, but it doesn't change the need to provide the right context when the developer wants to be explicit about locating new rule.
Pegasystems Inc.
--
Thank you Chiranjeevi for this feedback!
To summarize: at this point no immediate action will be taken, but we'll consider this feedback as we think about and design the New and SaveAs experience going forward.