Posted: 17 Feb 2017 4:42 EST Last activity: 19 Feb 2017 22:03 EST
Default Access Group - PegaNBAM:Agents
We are building a brand new Marketing application and have created a custom app on top of PegaMarketingFS_FW. We ahve updated the PegaNBAM:Agents Access Group as advised in the implementation guide. Can someone please explain the significance of this Access Group?
If this Access Group is mandatory to be updated with the custom application, in that case, there can be only one custom Marketing application in one Pega instance.
The PegaNBAM:Agents access group is used to define the access and privilege for all Pega Marketing agent schedules and marketing integration services. This access group primarily specifies your decisioning application and your artifacts ruleset.
See for example:
PegaMKTContainer Service Package rule which is used real time containers.
PegaNBAM-Artifacts agent schedule which handles all batch processes.
Pega supports and recommend the concept of a Central Decision Hub (CDH) where you decisioning logic and artifacts are saved in one application. In essence, yes, you should only have 1 decisioning application.
If you have business requirements that require multiple decisioning applications, please reach out to a Lead Decisioning Architect/Pega.