Flow fails on setting MinimumAgeForProcessing property in ms
The flow fails on setting the MinimumAgeForProcessing property in milliseconds (ms) in the Queue-For-Agent method.
Steps to Reproduce
- Log in to the application
- Get the DateTime difference for a date >25 days in MinimumAgeForProcessing property in milliseconds which comes up to 2160000000
- Set it in the Queue-For-Agent method on a post activity of local action and save it to an activity
A defect or configuration issue in the operating environment. The MinimumAgeforProcessing property is mapped to an integer and does not support a value more than 2147483647 in milliseconds.
ResolutionPerform the following local-change:
Use the enqueue() method instead of using the Queue-For-Agent method to use pyMinimumDateTimeForProcessing for scheduling an agent as per a given date in future.
- Perform a Page-New > StepPage1
- Use Property-Set:
StepPage1.pyAgentName to [Agentruleset:AgentName] e.g. "Pega-ProCom:ServiceLevelEvents"
StepPage1.pyItemStatus to "Scheduled"
StepPage1.pyMaxAttempts to Value
StepPage1.pyMinimumDateTimeForProcessing to @DateTime.addToDate("20180418T013020.420 GMT","5","10","10","10") [Use datetime library here to compute curent date + 25 days]
catch (DatabaseException de)
- Commit the rule
0% found this useful