Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Business events create duplicate notifications

SA-260

Summary



There is a delay between the triggering and running a triggered-business event. Unexpected results occur if the work object changes state before the business event agent performs the logic. The user subscribed to buiness events may see duplicate events under certain conditions.

Error Messages



Not Applicable

Steps to Reproduce



1. Create a process that changes the work object state quickly.

   For example:
    Activity with following steps
       Obj-Open-By-Handle
       Property-Set .pyStatusWork = "Open-A"
       Obj-Save
       Property-Set .pyStatusWork = "Open-B"
       Obj-Save

2. Create a business event that observes the object state changes in Case Manager portal.
  Case Manager portal > Calendar Tab > Event Subscriptions > New
    Chose Evaluate when an instance of yourWorkClass is "is created or updated"
    specify the object state in the conditions
     .pyStatusWork is Equal to "Open-A"
    Action:
       Notify subscribers in RSS feed
       supply a title to the rss feed and RSS feed message
       optionally include the property with <<.pyStatusWork>>
         double bracket notation.

3. Create a second event but use as above with the modification given below.
    .pyStatusWork is Equal to "Open-B"

4. Subsribe to events by clicking on the Subscription Icon, and choose Subscribe to event definition and RSS feed.

5. Run the activity.

6. Wait for two minutes for agents to process the business events.

7. Navigate to Case Manager portal > Calendar Tab, and refresh the RSS feed.

Root Cause



The business events system stores only the previous state with queued agent event. When the business event agent runs, it uses the current state of the work object. If the current work object changes state prior to the agent running, the logic will use the updated state instead of the state at business event initiation.  The delay of the agent (default 90 seconds) allows change in state prior to evaluation of business event logic.

Submitted product enhancement request item FDBK-8560.

Resolution



An enhancement request has been created for consideration by Pega Product Management.

Published December 9, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us