Difference between pyMinimumAgeForProcessing and pyMinimumDateTimeForProcessing
HI,
I am creating a queue page & settting a particular future date as the pyMinimumDateTimeForProcessing. I wish to increase the number of attempts to more than one. But the difference between first attempt & subsequent attempts should be 60 seconds. Also, of what I know, it checks the pyMinimumAgeForProcessing before processing each time. So if I set both these properties which one will decide the Minimum time after which the Agent processes it for first time? Best way to implement the requirement?
Hi Henry,
Thanks for comment.
I am not using an SLA for the requriement. The enqueueing for the agent is being done in an activity. My question is if we set a pyMinimumDateTimeForProcessing as say '20-04-2015' & attempts as 2 & pyMinimumAgeForProcessing as 300 ms. Will the Agent pick the task on 20-04-2015 & if not successful retry it after 300 ms?
Also,if we do not mention pyMinimumAgeForProcessing - what will be the time difference between first and second attempt by Agent?
(Agent is in Advanced mode with time as 7:am everyday)
Hi Tanul did uou find the solution for the above proble.
I am facing the same issue.
Please help me.
Hi Tanul,
When it comes to items with "Scheduled" status the important field is pyMinimumDateTimeForProcessing. The pyMinimumDateTimeForProcessing property is also an effective means of ordering the list without using the actual primary key. On the other hand both pyMinimumDateTimeForProcessing and pyMinimumAgeForProcessing are configurable.
There is an interesting article on the PDN that discusses how to set the Service Level Agreement (SLA) Late event from a property reference (https://pdn.pega.com/process/how-to-set-the-service-level-agreement-sla-late-event-from-a-property-reference). Try both approaches and use the one that works best based on your requirements.
Hope this helps,
Henry
Pega Academy