Question
TCS
IN
Last activity: 16 Oct 2018 12:03 EDT
Work Level SLA's
Hi,
when we configure work level SLA for a case, the values of GoalTime and DeadLineTime is available in WorkPage.pxFlow(pzInternalProcessFlow).pxAssignDeadTime and WorkPage.pxFlow(pzInternalProcessFlow).pxAssignGoalTime properties which is un-exposed.
The question is at what point of time the exposed properties like WorkPage.pySLADeadline, WorkPage.pySLAGoal will be populated.
I am having a scenario where I need to show the GoalTime and DeadLine time in user worklist (configured at case level) and I am having multiple workpools in my application.
so the best possible design is to create a report on my base work class (from which all my workpool classes are descending) with "report on descendant class instances" checked, and embed it in the assign-worklist RD as a sub-report.
But the problem here is if I am including un-exposed columns (WorkPage.pxFlow(pzInternalProcessFlow).pxAssignDeadTime and WorkPage.pxFlow(pzInternalProcessFlow).pxAssignGoalTime) in the RD configured on base work class, it is not doing union of workpools.
So I thought, I can create an expression and populate the exposed properties WorkPage.pySLADeadline and WorkPage.pySLAGoal and use them in the base work RD.
The above said properties are neither holding work level SLA or assignment level SLA values by default and I am not sure at what point of time Pega uses these properties. I would appreciate if somebody throws a light on these queries.
Thanks,
Siva.
Hi,
when we configure work level SLA for a case, the values of GoalTime and DeadLineTime is available in WorkPage.pxFlow(pzInternalProcessFlow).pxAssignDeadTime and WorkPage.pxFlow(pzInternalProcessFlow).pxAssignGoalTime properties which is un-exposed.
The question is at what point of time the exposed properties like WorkPage.pySLADeadline, WorkPage.pySLAGoal will be populated.
I am having a scenario where I need to show the GoalTime and DeadLine time in user worklist (configured at case level) and I am having multiple workpools in my application.
so the best possible design is to create a report on my base work class (from which all my workpool classes are descending) with "report on descendant class instances" checked, and embed it in the assign-worklist RD as a sub-report.
But the problem here is if I am including un-exposed columns (WorkPage.pxFlow(pzInternalProcessFlow).pxAssignDeadTime and WorkPage.pxFlow(pzInternalProcessFlow).pxAssignGoalTime) in the RD configured on base work class, it is not doing union of workpools.
So I thought, I can create an expression and populate the exposed properties WorkPage.pySLADeadline and WorkPage.pySLAGoal and use them in the base work RD.
The above said properties are neither holding work level SLA or assignment level SLA values by default and I am not sure at what point of time Pega uses these properties. I would appreciate if somebody throws a light on these queries.
Thanks,
Siva.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
IN
You should not include embedded properties (unexposed) in the report definition. All the data that you are looking for will be stored in pr_assign table. You need to join with that table and query the data accordingly. All the columns you are looking for are already exposed in that table.
TCS
IN
the goal and deadline will be in pr_assign table if we have configured an assignment level SLA. but the question here is i have configured SLA at work level (in process flow).
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.