Question
Declare Trigger Activity not committing Property value.
In my application one declare trigger triggers every time when any work object saves and committed. This declare trigger is running two times when i resolve any work object. In declare trigger we are setting one property "CaseResolveDate as pyresolvedtimestamp".
Now question is - (1) Why declare trigger is triggering two times? how can I find root cause? In tracer its triggering twice continuously.
(2) When the declare trigger runs first time, in pyWorkPage, CaseResolvedDate is not present, in this activity we are setting the CaseResolveDate and in clipboard page and pyWorkpage it is setting that value.
But second time when Trigger activity runs, the pyWorkPage should have that value. But It is not present in pyWorkPage. The pyWorkPage of second trigger is same as first trigger. Please help.
***Edited by Moderator Marissa to move from Pega Academy to Pega Support Community; updated platform capability tags***
Which version of PRPC/Pega are you using? - PRPC 7.1.8 version I am using.
Does this same behavior occur in all environments? - yes all environment.
When using Tracer which Event Types were selected? There is OOTB logging available which you can turn on in a non-Production environment to debug in more detail. - I will try that
Actually in flow two times end shapes are present, that's why declare trigger is triggering two times. In trigger activity we are doing obj-save one property value. After first trigger activity in pyWorkpage the value is present, but when second time the trigger activity is triggered, that property is not present in pyWorkPage. How is that possible?
Hello, Susmita! Do you have an answer on your question? We have the same problem too.
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.
Hello,
Which version of PRPC/Pega are you using?
Does this same behavior occur in all environments?
Did you test after clearing the declarative network?
When using Tracer which Event Types were selected? There is OOTB logging available which you can turn on in a non-Production environment to debug in more detail.