• Multiple Notification Run Definitions can exist in the system, but each one should have a unique name and alternative code.

• The information that can be specified on notification run definitions depends on the classification of the selected notification type.
• Notifications Type selected should be related with a Communication Template with the following types of tags:
  • On communicating financial notifications
    • Notification, Contact Information and Accounts Receivable tags
  • On communicating customer care notifications
    • Notification,  Contact Information and the entity tags of the entity that is included in the related notification item

• If there is at least one scheduled or completed notification run using the notification run definition latest instance then a new notification run definition instance is created

• Notification run definitions cannot be deleted if there at least one scheduled or completed notification run for that definition.

• Mandatory Fields:
  • Name
  • Notification Type
  • Scheduling Settings

Determines when the process run definition should be applied. Process run definitions can be applied ad-hoc or on a recurring basis. Scheduling settings hold the following information:

• Method: It provides the following options. For each option different settings are provided:
  
  • Run now
  • Run on specific Date / Time
  • Specific Date / Time
  • Repeat
  • Start at
  • End by Date / Time
  Every X UOT
  • Advanced Repeat
    • Start at
    • End Date
    • Recurrent Mode Settings
• Start at: It determines the date and time that the process run definition should be applied. If the run now option is selected then the date / time is read only and set to 30 seconds after saving the record. Two options are available
  • Specific Date / Time
  • After X UOT: measured in seconds, minutes, hours, days, weeks or months
• End by Date / Time: It determines the latest date and time that the process run definition should be applied. This is available only if the repeat option is selected. Three options are available
  • No End Date
  • Specific Date / Time
  • After X UOT: measured in seconds, minutes, hours, days, weeks or months
• Every X UOT: It determines how often the process should be generated. The process run definitions can be scheduled to be applied per seconds, minutes, hours, days, weeks or months. This is available only if the repeat option is selected.
• Recurrent Mode Settings: It determines specific recurrence settings that can be applied per day, week, month or year. This is available only if the advanced repeat option is selected
  
• Throttling:  It determines the maximum number of processed records that should be affected per each run and the interval between each iteration. This is available only if the repeat and advanced repeat options are selected. Throttling settings include the following
  
  • Maximum batch size
  • Start again after X UOT (seconds, minutes,hours, days)

A list of segments which are used to filter in the contact information or the accounts receivable that will be notified, and optionally the notification information. The criteria consist of the following:

• Filtered entity: A select box displaying the main notification entity (i.e. contact information or Accounts receivable) and the entity which is selected in the notification information. The specified entity will be filtered while evaluating the results
• Segment: A select box with all the segments having the selected filtered entity as the segment entity

A list of segments which are used to excluded the contact information or the accounts receivable that will be notified, and optionally the notification information. Its criteria consist the same as in "Included in Segment"

Defines a list of notifications that should already be generated in the past. It consist of the following values:

• Notification Type: The type of the notification
• Life Cycle State: The life cycle state of the notification. The default value is the completed.
• Created less than X UOT ago: measured in minutes, days, weeks, months or years
• Created more than X UOT ago: measured in minutes, days, weeks, months or years

Defines a list of notifications that should not already exist. Its values are the same as in "Notified Previously"

It filters the accounts receivable based on their balance. Two options are available, which can be used combined:

• More than: checks for a value that is more than or equal to the one specified (≥)
• Less than: checks for a value that is less than to the one specified (<)

It filters the accounts receivable based on their outstanding amount and a specific due date. Two options are available, which can be used combined:

• More than: checks for a value that is more than or equal to the one specified (≥)
• Less than: checks for a value that is less than to the one specified (<)

The due date can be specified in one of the following ways:

• Due in X Days: Checks for accounts that are due in up to the date that equals to (current date + X). For example, if the current date is the 23rd and you specify X=5, then it checks for accounts due up to the 28th.
• Due X days ago: Checks for accounts that were due up to the date that equals to (current date - X). For example, if the current date is the 23rd and you specify X=5, then it retrieves accounts that were due up to the 18th.

It filters the notifications that will be created based on the total outstanding amount of each notification, as calculated based on the related invoices. Two options are available, which can be used combined:

• More than: checks for a value that is more than or equal to the one specified (≥)
• Less than: checks for a value that is less than to the one specified (<)

It filters the accounts receivable based on the wallet balance of wallets owned by that account.  Two options are available, which can be used combined:

• More than: checks for a value that is more than or equal to the one specified (≥)
• Less than: checks for a value that is less than to the one specified (<)

It filters the accounts receivable based on the wallet estimated consumption days of wallets owned by that account.  Two options are available, which can be used combined:

• More than: checks for a value that is more than or equal to the one specified (≥)
• Less than: checks for a value that is less than to the one specified (<)

It filters the accounts receivable based on the wallet product estimated consumption days of wallets owned by that account.  Two options are available, which can be used combined:

• More than: checks for a value that is more than or equal to the one specified (≥)
• Less than: checks for a value that is less than to the one specified (<)

It filters the accounts receivable based on the type of subscriptions owned by the accounts receivable. Multiple subscription types can be defined.