Notification Template Group Processing Sequence

Overview

1. Dunning Template Override
   Aria first performs a check for a Dunning Behavioral Option Override assigned to the group. If a Dunning Behavioral Option Override exists, Aria follows the behavior as defined in the Dunning template.
2. Account Level Overrides
   If a Dunning Behavioral Option Override is not assigned to the group, then Aria performs a check for templates defined at the Account Level that are overriding the Template Group.  If an Account Level Override exists, Aria follows the behavior as defined at the Account Level.
3. Account Level Template Groups
   If no overrides exist, Aria checks for an Account Level Template Group associated with the account.
4. Functional Account Groups
   If no Template Groups are assigned at the Account Level, Aria checks for a Template Group associated at the Functional Account Group level of the account. If more than one Functional Account Group is attached to the account and each has an assigned Notification Template Group, it is unclear to Aria which Functional Account Group to use. In this case, Aria ignores this step and proceeds to check for a Master Plan.
5. Master Plan
   If there are no Template Groups assigned to the Functional Account Group, or if more than one Functional Account Group is assigned to an account, then Aria checks for a Template Group associated with the Master Plan of the account.
6. Client Default
   If there are no Templates Groups assigned to the Master Plan, Aria uses the default Template Group assigned at the Client Default level.