Consolidating Pega Pulse from Child and Parent Cases
We have a use case where the customer has a parent child case relationships and need to roll-up pulse comments entered on a child case to their parent case. Does any one have any similar use cases? If so, how did you solve it.
***Edited by Moderator: Lochan to update platform capability tags***
You can check which property is being used to store the pulse message and then you can add that in the data propagation of parent case. This will pass this property value from parent case to the child case.
I'm not sure this would work considering Pega Pulse has it own clipboard page. I have to either do a batch copy from the child Pulse page to the parents Pulse page or I have to modify the activity to add the child message to the parents message real-time. I'm still investigating.
Pulse comments are stored are part of pc_work_social table, each pulse comment will have their pxInsName and pzInsKey,pyID similar to a work object. Also there is one column pyIndirectObjectId which will have value of Work object to which this comment belongs.
I believe you can do Obj-Open of pulse comment using pyID, update pyIndirectObjectId(to cover case iD) and insert a new row into the pc_work_social table.
I see the table, and I see the items, but they aren't the items I expected. They are stored in the PegaSocial_Message class. I don't see all the Pulse entries in that class. I have to figure out what causes an entry to be in PegaSocial_Message as opposed to PegaSocial_Posts.
Either way, I created a report def and optimized some properties. If I can figure it out, it will solve my issue.