We are looking for a placeholder PostExecuteContainer extension Activity to HandleRealTimeContainerExecution_V2 Activity rule. The ask is similar to the PreExecuteContainer Activity available at PegaMKT-Engine:08-08-01 ruleset, step 5.8.
The rationale behind the Ask is, for some of the clients, there is a need to persist in the request and response to their own tables for their analysis, especially when Customer service OR NBAA application is used in the customer-assisted channel. Since the Container V3 service Activity HandleContainerRequest_V3_Post is already marked to handle, an additional extension point to HandleRealTimeContainerExecution_V2 would apply any customization requirements for the client.
Another potential option is to introduce a place-holder Extension Activity in the next version of the Container service Activity rule itself.
@Nanjundan Chinnasamy , this is not an extension point that product would be comfortable adding as it adds a big exposure risk point for SLA. Stashing away data as part of the real time call is not a good practice and can add a lot of latency. You should be using the decision and interaction history data to that is produced for any offline analysis or subsequent propagation to other systems.