Question
Tech Mahindra
IN
Last activity: 23 Mar 2016 12:46 EDT
Save As a rule
When developer save a rule into another another, user should get an option to override the rule content if target version already have it!!!
Message was edited by: Lochan to add Category
Pegasystems Inc.
IN
Hi Satya,
I believe that overriding a rule is probably not a good idea and that is the reason we have the concept of ruleset version so that at anytime developers can refer back and check what was the design or content of a rule in earlier versions.
Also you may want to explore the option of rule set branching.
Tech Mahindra
IN
When I try to do 'Save As' a rule from vSource to vTarget:
Current behavior:
If rule already exists in vTarget, an error displayed "Rule already exist"
Expected behavior:
If rule already exists in vTarget, a confirmation message to be displayed
asking confirmation to override rule in vTarget.
Pegasystems Inc.
IN
Hi
"
Expected behavior:
If rule already exists in vTarget, a confirmation message to be displayed
asking confirmation to override rule in vTarget"
I am not convinced with this idea of overriding an existing rule from Target version. I feel branching should do good for this.
Anyway, I will keep this query open for others to provide their inputs.
Crestone Technology
MX
The behavior you suggest would be convenient. I'll acknowledge that.
However, I think this is a case in which convenient != good
RuleSet versioning and other programming constraints are often inconvenient by design. As Santanu Bhattacherjee notes, the suggested behavior contradicts a fundamental principle of RuleSet versioning and Check Out/Check In.
In a similar fashion, suppose my app is for scheduling jobs for house painters. Please forgive the sloppy SQL syntax below - this is meant to be a quick, fictional example.
- I have the table: PAINTING_JOBS (ID, DUE_DATE, PAINTER, COLOR)
- COLOR has the constraint IN ('White','Grey','Brown','Blue')
- I attempt
INSERT into PAINTING_JOBS(id.nextval, '30-Mar-2016','Bob the Painter','PINK');
It would be convenient if the DB would alter the constraint to add PINK to the color choices, but it would not be desirable behavior.
Disclaimer: my argument here will be undone if you ask my 4-year-old daughter her opinion, which would surely be that all houses would be painted pink, preferably with spots.
Pegasystems
US
I'm not convinced it would be a good idea to allow save-as to optionally replace the target rule. There are so many situations in which this could be a problem.
1) If an assignment on a flow is still using the old rule and will break if the new rule isn't compatible.
2) If you have the target checked out,.
3) If someone else has it checked out
4) If the target is in a locked ruleset
. . .
/Eric