Discussion
Capgemini
IN
Last activity: 15 Apr 2015 5:40 EDT
PyResolvedTime is not captured
Hi,
pyResolvedTime:
Sum, in seconds, of the time a work object held a status value starting with New, Pending, or Open. Computed and updated when a work item becomes resolved. Older values are retained within a page of the pyResolveSummary property.
After upgrading application from v5.4 to V6.1SP2 PyResolvedTime is not captured in prod environment. can you suggest what might be the reason for this?
Pegasystems Inc.
US
pyResolvedTime is set by the StatusElapsedCalculation Rule-Declare-Trigger. I suggest you run tracer and see if it fires. If it doesn't, perhaps you've blocked it?
Capgemini
IN
Thanks for reply Marik...
Yeah, it is set by the Declare trigger rule and it is not captured in production environment, all the rules are exist like development, SIT and pre-prod environments and there it is working as expected. Tracing in production is difficult and it is restricted for us. So, is there any alternative approach to trace this.
Pegasystems Inc.
US
Do you know if other Declare Trigger rules are working properly in Production? If so, I suggest manually looking to see if you blocked this particular trigger in a production-only ruleset. If not, you'd better enter a Support Request.
If you have an environment identical to production and it is working there, there must be a difference and we need to find it.
Capgemini
IN
Yes, other declare trigger rules are working fine. That rule is not blocked it was there in pega ruleset. (class work- ; Ruleset Pega-ProCom : 06-01-01)
Capgemini
IN
Hi,
We did revalidate and save for pyResolvedTime ( property), Declare trigger rule and correspondig activity in production now it's working as expected.