Limitation on Outbound schedule in NBA designer
Hello,
We are using Pega 8.7.1 and I wanted to know that is there any limitation for outbound schedule.
Our application is for telecommunication domain and we have account as top context and subscriber as primary context.
We want to add additional scheduler in NBA designer, so wanted to know if there any limitation on the count of scheduler and pros and cons of additional scheduler.
Thanks,
Taniya
TCS
AE
@Saleem_A Thanks for your response. I have gone through this document and I am not clear on below point:
"Note: Choosing context other than top level customer context will result in a warning, as it will impact engagement policies and might lead to action failures."
If this is the case then why Pega is allowing to run additional schedule. I really need support here to understand how can we achieve to send offers at different context via outbound schedule.
Pegasystems Inc.
US
Additional schedules is to allow multiple schedules that execute at different times, different base populations, different parts of the taxonomy, etc. It is best practice to always run schedules at top level and use multi-level features to assign actions to the the right context. I suggest you read up on multi-level decisioning capabilities if your main objective is to send offers at different contexts. The main thing you will find when reading about this feature is that you will always be sending your communications to primary (the human), but you will either send the communications that relate specifically to them individually or relate to their accounts. You get to choose who is the recipient of account actions by designating the owner of the account.
TCS
AE
@Saleem_A Thanks for your response.
It will be very helpful if you can let me know if there is any limitation on the count of scheduler can be scheduled in NBA designer.
Thanks,
Taniya
Pegasystems Inc.
US
@TaniyaD3 , please see the first 2 rows in the first table of Service and data health limits