Question
Intact Financial Corporation
CA
Last activity: 26 Oct 2018 10:13 EDT
Pega Rule form As-of-Date circumstance conversion to Start Date 7.3.1
Im performing an upgrade from Pega 6.3 SP1 to Pega 7.3.1.
I ask again the question found in an other post, where the answer has been archived (https://collaborate.pega.com/question/pega-rule-form-date-circumstance-conversion-start-date) :
PRPC doesn't support As-of-Date circumstance on its rule-form. Instead we should be using Start Date[ End date as null] to apply the same circumstance logic. However, is there any OOTB tool/wizard/mechanism with which this conversion can be done on the rule forms of existing rules?
We have over 16000 rules with circ date in our system, 14 years of development, I can't imagine perform a 1 by 1 method as proposed by Pega.
In my opinion, when you perform a change like that, you should make your application support both method as one method (both date as one date). We should be able to have the same rule name with circDate using the startDate (new rule) and circDateValue (old rule).
I have validated in Pega 6.3, I can't use the Start Date, since it's using the current date instead of the property "pyCircumstanceDateProp". So, I can't perform the change before my upgrade, to facilitate the conversion.
Thank you for your answer
***Moderator Edit-Vidyaranjan: Updated SR details***
Accepted Solution
Intact Financial Corporation
CA
Pega ticket has finally bring something interesting, it exists an activity to perform a Big Bang from pyCircumstanceDate to pyStartRule :
old:pzUpgradeDateCircumstanceRules
Good luck to eveyone else who have problem with Pega Ugprade
Pegasystems Inc.
US
Hello,
Did you see this guidance documented somewhere?
"PRPC doesn't support As-of-Date circumstance on its rule-form. Instead we should be using Start Date[ End date as null] to apply the same circumstance logic"
I had not heard of As-Of-Date circumstancing not being supported in 7.3.1, although I do agree that Start and End date are more straightforward fields. It looks like there may be a long-standing bug where one of the two fields required to use that feature, Date Value, is not present on the UI. The field Date Property which is supposed to be used with Date Value is still present.
Can you tell us more about your situation? You mention having an application of 16000 rules. How many of those use As-Of-Date circumtancing?
Intact Financial Corporation
CA
As-Of-Date is supported while running, but you can't use it for new development, since like you said, the field is no more on the UI.
Start Date has change in Pega 7, now the Start Date uses the date property, instead of the current date. I have no problem with this change, I only have a problem with the way Pega brings it.
I have over 16000 rules with circumstance as-of-date, we have a lot more rule than 16000 rules (for fun, I ran a report 29836 distinct rules, total of 70822 rules).
We skim our rulesets every year, because we have too much development in progress.
Pegasystems Inc.
IN
As part of the post upgrade step, the old as of date circumstanced rules will be updated to use the new date range circumstancing. Only those rules which have both as of and date range defined on the same rule or same rule family will not be upgraded to new format.
Accepted Solution
Intact Financial Corporation
CA
Pega ticket has finally bring something interesting, it exists an activity to perform a Big Bang from pyCircumstanceDate to pyStartRule :
old:pzUpgradeDateCircumstanceRules
Good luck to eveyone else who have problem with Pega Ugprade