Question
Bank of Singapore
SG
Last activity: 19 Mar 2018 19:30 EDT
Declare Trigger's execution method as Background copy, missing few commits 20 out of 10k workobject commits
hi team,
we have declare trigger activity run as background copy activity pushes data into reporting database.
there are some workobject whose updated data is missing in reporting db, i'm thinking because of declare trigger background copy commit issue. i didn't see any exceptions in the logs.
in production env we are getting this issue i.e. multi node environment, unable to replicate in lower environments.
how to fix this issue or any alternative suggestions appreciated.
Regards,
Madhu
Accepted Solution
Bank of Singapore
SG
Hi this issue is resolved by using queue for agent method in declare trigger calling activity.
1. in declare trigger rule execute immediately is set
2. created customized queue class, on queue class step page set the agent details and below details
try {
myStepPage.putString("pyPageNames(1)", "workpage");
myStepPage.putString("pyInsHandles(1)", tools.getPrimaryPage().getString(".pzInsKey"));
tools.getThread().getQueueManager().enqueueDeferred(myStepPage);
} catch (DatabaseException ex) {
throw new PRRuntimeException(ex.getMessage(), ex); }
3. in EstablishContext activity saved into our queue class and removed lock on it
tools.getDatabase().open(insHandle, true, false, false, null);
4. In agent activity kept the remaining storing logic, enabled AQM in standard agent
Pegasystems Inc.
US
How is the declare trigger configured?
- What is the 'Trigger when an instance is' value set to?
- Are there any conditions?
Does the declare trigger fire for different types of work objects or just one class? If it is used for multiple work types, does the issue only occur for certain ones?
Bank of Singapore
SG
trigger when instance is "committed save"
declare trigger fire for different types of work objects, issue is occuring for all work types but when the work object is resolved that particular status is missing.
attached WO history, that part is executed by SLA activity, within that we have ResumeFlow activity.
Pegasystems Inc.
US
Can you confirm the batch requestor has access to the Declare Trigger rule and activity? I would have expected an error message as shown in the article below if it didn't but since it works in the lower environment maybe that could be a difference.
Accepted Solution
Bank of Singapore
SG
Hi this issue is resolved by using queue for agent method in declare trigger calling activity.
1. in declare trigger rule execute immediately is set
2. created customized queue class, on queue class step page set the agent details and below details
try {
myStepPage.putString("pyPageNames(1)", "workpage");
myStepPage.putString("pyInsHandles(1)", tools.getPrimaryPage().getString(".pzInsKey"));
tools.getThread().getQueueManager().enqueueDeferred(myStepPage);
} catch (DatabaseException ex) {
throw new PRRuntimeException(ex.getMessage(), ex); }
3. in EstablishContext activity saved into our queue class and removed lock on it
tools.getDatabase().open(insHandle, true, false, false, null);
4. In agent activity kept the remaining storing logic, enabled AQM in standard agent