Support Article

Only one pulse note of two pulse notes is considered

SA-79197

Summary

User adds a pulse note from a flow shape and another pulse note from an activity. However, only the pulse note which is added from the flow displays. The user creates a wrapper activity which triggers the pzCreateCase activity to create a case. However, the Post to Pulse flow shape is added to the case creation flow. The pzPostSocial activity is added to the wrapper activity to post the pulse note to the case created in step 1. However, only one pulse note added to the flow shape displays in the case. The exact context is unavailable for the pzPostSocial activity to link the message to the case. The pzCreateCase activity uses the IsCalledFromPegaUnitPlayback property to create a work page. In this case, the value is false and the step page is created similar to pyTopCasePage_1. Hence, the wrapper activity is not rendered the correct context to update the case. However, pyIndirectObject renders the case ID on the Clipboard.

Error Messages

Not Applicable

Steps to Reproduce

Create an activity to create work objects
Add a post to Pulse in the flow
Use the pxPostSocial activity after the case creation

Root Cause

A defect in Pegasystems’ code or rules. A case is created through the pzCreateCase activity. A pulse note is added to the case stage 1 flow using the Post to Pulse flow shape. A second pulse note is added after the creation of case is completed through the pzCreateCase activity. A pulse note is added to the stage 1 flow of the case using the Post to Pulse flow shape. The second pulse note is added after the pzcreateCase. While using the pxPostSocial activity, both the pulse notes are not added after the case creation. The issue is with the pzRetrieveFeed activity. The objects are stored based on the post posted time stamp. The pulse notes are created simultaneously with a fraction of seconds difference. Hence, only one pulse note is considered and rendered in the pulse gadget. Therefore, the changes made in the pzRetrieveFeed activity to save the pulse messages are based on pzInsKey and not through pulsepostedOn. The pzRetrieveFeed activity uses pyFeed.pyPostedOn and pyFeed.pyContext to identify unique posts. The gadget considers both the posts as same as pyFeed.pyPostedOn does not have the milliseconds information.