Question
TCS
IN
Last activity: 31 Dec 2017 8:02 EST
Time Interval as non deployable component
Hey Guys,
I've a requirement to automatic retry a service on failure after 30 minutes. The catch it, this time interval should be reconfigurable without deployment (something similar to a Dynamic System Settings concept) . The wait shape's Time Interval falls out of scope (as in order to change the interval the latest version should be migrated to prod)
Is there anyway for the flow to wait for sometime with the time interval being a non deployable component?
Thanks
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
IN
Hi Aparna,
Can we re-trigger this based on local action with below config:-
Have a textbox for the desired time interval
Have a activity as post action on certain button that would use that interval and wait for that time before calling service method.
Thanks,
Ujjwal
TCS
IN
Hi Ujjwal,
This would have worked, had it not been automatic re-trigger of service.
Pegasystems Inc.
IN
Hi Aparna,
Even if you make things automatic, you have to have a manual intervention for wait duration.
The question is how would PRPC understand what interval it would need to consider.
Thanks,
Ujjwal
TCS
IN
Hi Ujjwal,
What I meant by automatic re-trigger of service was - once the service fails, the flow should loop back to the service call, with a wait duration.
Would the activity with Wait method work with property reference(instead of giving a time figure)?
<Have attached the flow for better understanding>
Pegasystems Inc.
IN
Hi Aparna,
You can use When condition in activity to have your scenario run based on property reference.
Thanks,
Ujjwal
TCS
IN
A When rule would be a deployable component, as in, if there is any future change in the reference value, When rule has to be modified and deployed to higher environments.
I tried with Wait shape using Future DateTime and using a DSS property to get +30 minutes. Strangely Wait shape doesnt work with DSS value even though giving the same value in the Wait configuration works.
@DateTime.addToDate(@CurrentDateTime(),"0","0","30","0").
Please find attached
StellarNexus Consulting UG
DE
Can you try to use the DSS in place of "30" inside the addToDate function? I hope it should work then.And, this DSS should specify only the timelimit( ex. 30) and not an expression in it.Hope you get where you are going wrong.