Hi, we are with the implementation of real time event in CDH, but we are wondering how to handle the prioritization in the queue of the sending of the action resulting from an event and the queue generated by the normal sending of the nba run.
We have made some tests of it, for example in email, and the action generated by the rt event joins the mailing queue, which causes that it does not go out until its time in the queue. Preventing the notification to reach the final customer on time. Same case with Push, for example.
The optimum with this would be that the action generated by RT Events is prioritized within the queue or manages a separate queue for its prompt delivery.
***Edited by Moderator Rupashree to add Capability tags***
@AnthonyR4693, the way to accomplish this is to have different email accounts in Pega (they can point to the same provider with the same credentials, but they need to be considered virtually different to Pega), one for regular batch emails and one that is used when the action is initiated for higher priority. You would split the action flow based on the an attribute that would indicate if it is meant for the normal batch account vs an event account. In addition to this you would need to have dataflow nodes that can be available to take up work for both accounts independently:
1. You need to have multiple background processing nodes (where the email child agent is running).
2. The Email data flows run on the MKTEmail tier in Pega Cloud. As long as you don't get into a situation where you have exceeded the max number of Data Flows processing, your 2 accounts will be processed independently and the real-time queue should be emptied faster than the long queue of a batch email account.