Question
IKOR
AU
Last activity: 17 Feb 2020 16:52 EST
AddTime() is not considering the calendar instance when it is getting executed through batch requestor context
Hi there,
We have a situation in our project where AddTime() is not considering the calendar instance when the logic is getting executed in the background (batch requestor).
Background
We have recently automated the business process and as a part of it application specific SLA needs to get computed as a part of background process (Using SLAs to proceed from the assignments)
Workflow is determining the Goal, deadline and Passed Deadline dynamically based on the business logic
Here is the logic used to determine the agreements
@(Pega-RULES:BusinessCalendar).addTime(.CaseSLAStartDateTime,0,Param.HoursToAdd,Param.MinutesToAdd,Param.WaitDateTime,true,Param.Calendar)
As a agreement calculation, application needs to consider the calendar for computation, but unfortunately that is not the case. (Computation is happening in the batch requestor context)
Nevertheless, if the functionality is being executed in the requestor context, function is returning the correct value
Would appreciate, if you any can assist me in addressing the issue
Cheers,
Naren
Pegasystems Inc.
AU
Hi Naren,
This response assumes you are using a Standard Agent (pre-Infinity) or Queue Processor (Infinity). Can you clarify the background processing technique you are using?
If your intent is that you set Param.Calendar before the background task is enqueued, and Param.Calendar be available when the background task is running, I doubt the parameter page is persisted and restored in the background processing task. I note though you have other Param's in your function call - are they getting through?
The preferred way to make state available to the background processing task is to ensure the values the task needs are on the step page of the Queue-For-Agent / Queue-For-Processing method. A Standard Agent will load the latest version of this instance from the database as the Primary Page for its execution; a Queue Processor has a few more options, but the premise is the same ... by setting the Calendar you want to a property on the item queued for background processing, you can reference it from 'Primary' in the background processing Activity.
I recommend using a Log-Message step in both:
Hi Naren,
This response assumes you are using a Standard Agent (pre-Infinity) or Queue Processor (Infinity). Can you clarify the background processing technique you are using?
If your intent is that you set Param.Calendar before the background task is enqueued, and Param.Calendar be available when the background task is running, I doubt the parameter page is persisted and restored in the background processing task. I note though you have other Param's in your function call - are they getting through?
The preferred way to make state available to the background processing task is to ensure the values the task needs are on the step page of the Queue-For-Agent / Queue-For-Processing method. A Standard Agent will load the latest version of this instance from the database as the Primary Page for its execution; a Queue Processor has a few more options, but the premise is the same ... by setting the Calendar you want to a property on the item queued for background processing, you can reference it from 'Primary' in the background processing Activity.
I recommend using a Log-Message step in both:
- The Activity that queues the task - to show that you've calculated the correct Calendar; and
- The background processing Activity - to show that you've retrieved the desired Calendar value.
Note that in a multi-node environment your background task may run on a different node, so check logs across all nodes. Use InfoForced level to ensure it is output now, but change this back to Debug before you go to Production.
Please report back your findings!