Incorrect value calculated for minimum age for processing
Hello!
I intend to use a standard agent for processing work items. However, the work items may be processed at a future date and hence I am using the 'MinimumAgeForProcessing' parameter when queuing the work objects.
The issue is that if the minimum age is very large, then the minimum age is being stored as an error value (<pyMinimumAgeForProcessing>3.2706526063E10</pyMinimumAgeForProcessing>) which results in incorrect value of pyMinimumDateTimeForProcessing.
I do not want to use the service level agent because the number of items to be processed is very large and I believe it will clog up service levels.
Anyone else has faced a similar issue? Any thoughts or resolutions?
***Updated by moderator: Lochan to update Categories***
Accepted Solution
Bank of Queensland Group
AU
Pegasystems Inc.
IN
pyMinimumAgeForProcessing is an integer which will not be able to store large value. I think you can try using pyMinimumDateTimeForProcessing property while you queue. You need to set the date time value in this property and keep the minimumage as blank.
Thanks
Saikat
Bank of Queensland Group
AU
Hello Sai,
Thank you for taking out time to answer the query. I would however not like to introduce any custom operations as this adds overhead to maintainence.
I will post my solution below.
Pegasystems Inc.
IN
The maximum allowable integer number is 2147483647
Are you storing this for seconds? If yes, try converting this to year. For example 2147483647 seconds is close to 68 years.
Do you think this helps?
Bank of Queensland Group
AU
Hi Santanu,
Thank you for taking out time to answer the query.
I did check the maximum value for the integer. That comes to about 24 days. Queue-For-Agent method only accepts milliseconds as the MinimumAgeForProcessing param (as per PEGA docuemntation). if you mean that I somehow override the method param to take input in seconds instead of ms then I am not sure how to implement that. Would like to know if such an option does exist.\
I will post my solution to the issue below.
Accepted Solution
Bank of Queensland Group
AU
Hi,
My solution to the issue is below:
1. Queue-For-Agent method only accepts the MinimumAgeForProcessing params value in milli seconds and is of type integer. As mentiond in the comments above, the maximum value of JAVA integer is 2,147,483,648. In milliseconds, that is about 24 days.
2. Since I did not want the business processing of my case to be done by SLA agent, my solution is to make the case "wait" till the time of the execution. SLA agent obviously handles any future date.
3. Once the SLA hits, the process is transferred to my orgs standard agent. The case in the meantime waits on an assignment. This standard agent which I have created will perform the business processing. Hence the load of performing the business process would be the headache of the customer standard agent and NOT then SLA agent.
4. Once the processing of my orgs agent is complete, it performs a resume flow of the case.
Do post if anyone else has a better way to approach the problem.
Hi,
My solution to the issue is below:
1. Queue-For-Agent method only accepts the MinimumAgeForProcessing params value in milli seconds and is of type integer. As mentiond in the comments above, the maximum value of JAVA integer is 2,147,483,648. In milliseconds, that is about 24 days.
2. Since I did not want the business processing of my case to be done by SLA agent, my solution is to make the case "wait" till the time of the execution. SLA agent obviously handles any future date.
3. Once the SLA hits, the process is transferred to my orgs standard agent. The case in the meantime waits on an assignment. This standard agent which I have created will perform the business processing. Hence the load of performing the business process would be the headache of the customer standard agent and NOT then SLA agent.
4. Once the processing of my orgs agent is complete, it performs a resume flow of the case.
Do post if anyone else has a better way to approach the problem.