Question
B.Braun group
BR
Last activity: 19 May 2016 14:01 EDT
I have to avoid a persistence of a work object on interaction history. How can I do that?
I have a particular case id that I dont want to be saved on DEMHandler.CustomerInteractionHistory(1...n) how can I do that? I will apreciate your help.
Thank you all that answer this question, but it was more simple than I thought, I just add a pre condition to not call this activity NBAACaptureInteractionResponse .
Regards,
Mario Mesquita
Pegasystems Inc.
IN
Hi
Perhaps the suggestion given how to not save CustomerJourney page into CustomerInteractionHistory? be able can give you some idea for this as well .
B.Braun group
BR
That is the poblem it is a OOTB functionality, and only using a page remove will not help, because it will be saved on PRPC database tables, this is what we want to avoid, to not save this CustomerJourney(Embed-OMFON-CustomerJourney) into CustomerInteractionHistory(n) (Embed-OMFON-CustomerJourney). Somewhere is the code that save the content of CustomerJourney(Embed-OMFON-CustomerJourney) into the database, this is what we need to avoid. Any help?
Pegasystems Inc.
US
Mario,
Would setting pyTemporaryObject to true address your needs? It won't stop you from doing an obj-save of the object, which will persist it to the database, but it will tell the process engine not to persist it or to create assignments. Based on your initial comment, it looks like you're trying to avoid persisting an embedded page. If you save the object it's embedded on, it's going to be saved as part of the data structure. The only way to avoid that would be to move it to a top level page and completely out of the work object that's going to be saved. If that's being added by OOTB code, you'd need to customize the code (assuming it's possible) or intercept the update and remove the page before the save.
Thanks,
Mike