Declare triggers are detecting changes in unchanged properties
Declare trigger rules, that are configured with the option to trigger when an instance is "Saved and ... One of these properties was modified," will at runtime fire off even if none of the listed properties were modified.
Steps to Reproduce
- Login to the Out-of-the-box (OOTB) PegaRULES 07.10 Application.
- Navigate to the class explorer, expand PegaSample-Task, and go the Process category.
- Run PegaSample-Task .BasicProcess Flow.
- Run the tracer and click on “Settings.”
- Check “Declare Trigger” checkbox under “EVENT TYPES TO TRACE.”
- Click “Select All” button under “RULESETS TO TRACE.”
- Add “pyDeclarativeContext” under “PAGES TO TRACE.”
- Click “OK” button.
- Go back to the tab that opened when you ran the BasicProcess flow, fill in the field for Summary text area, and click the “Create” button.
- Engage the tracer window and pause the tracer.
- Search for “pxTriggerOnCaseChange” activity.
- Open the TraceEvent page by clicking on the row where the “Activity Begin.”
- Click on pyDeclarativeContext link.
- Notice “.pyEffortEstimate” listed as a changed property.
- Open the primary page “pyWorkPage” of the same tracer event and search for the “pyEffortEstimate” property. The value does not exist on the page.
- Check the primary page “pyWorkPage” on any of the previous tracer events and notice how “pyEffortEstimate” property never existed on the clipboard.
This issue was determined to be a product enhancement request.
An enhancement request, FDBK-17828, has been created for consideration by Pega Product Management.
100% found this useful