Any way we can achieve circumstance based on DSS value? i have to make some changes to flow rule which should take effective from certain date(which can be changed).
If you want to go with circumstancing, you can go with circumstance template. In the circumstance definition rule, I think we can write an expression to get the value from DSS and compare it with the property you want.
You can read the DSS and store in a property before the circumstance rules triggered. Please check this article (Approach 5)
Write an activity instead, in which you can get the dss value & then set it to a property in datapage and use it
But definition expression is not allowing to have DSS when i m comparing with pxCreateDateTime
Is this should be standalone activity or where we are going to invoke? Obj-Open with key of circumstanced rule?
With this approach we can only configure for only “=”, if i want my changes to be effective after specific date we don’t have possibility to define range for property in circumstance rule. Range is only available for date type (start and end).
You could try configuration set? there is more development experiences tied into these values - for me, it has the benefits of a dss whilst keeping the low code rule authoring in mind.
https://docs.pega.com/bundle/platform/page/platform/app-dev/creating-configuration-set.html
Before the circumstanced rule is resolved:
- Use a Data Transform or Activity to read the DSS value using @baseclass.GetDSSValue(“RuleSetName”, “SettingName”) and store it in a case property (e.g. .EffectiveDate).
- Circumstance your flow rule on .EffectiveDate using the date range qualifier (start date / end date) — this gives you the “effective after” behaviour.
- When you want to change the effective date, update the DSS value and your Data Transform / Activity picks it up dynamically at runtime, before the flow rule gets invoked. Make sure the property is already commited with the date value.
@KiruthikaA Your 2nd point, the actual requirement of mine is to have flexibility of date change using DSS. Why would i need to select date range again? it is like hardcoding date
My scenario is Start Date value should be from DSS. Bcs my start/effective date can be vary.
try puting the dss value to a datapage
Hi, you have to add the pxcreatedatetime of case in circumstance rule and on reaching to the flow please get the DSS value for comparision and set it, then flow will check the circumstance rule if don’t match it will pick base flow rule.
You can still DSS for date range, check but you have to make sure that the DSS is processed before it is been used in the flow. For instance, in Flow1 you need to take different path based on the date value, make sure the EffectiveDate property is populated from your DSS before it reaches the Flow1. This way the property will be populated ONLY from DSS.