• Mandatory Fields must be defined
  • Notification Type
  • • Customer Care Notifications:
      At least one Segment MUST be defined (in 'Included' or 'Excluded')
    • Financial Notifications:
      At least one of the available criteria MUST be defined
• Name and Alternative Code must be unique

• Selected Notifications Type
  should be associated to a Communication Template including  Tags of the following Types exclusively:
  
  • For Financial Notifications
    • Notification Tags
    • Contact Information Tags
    • Accounts Receivable Tags
  • For Customer Care Notifications
    • Notification Tags
    • Contact Information Tags
    • Entity Tags of the Entity that is included in the related Notification Item

  • Status
    colour Blue title Available from CRM.COM R12.0.0

    For Reward Offers Notifications
    • Reward Offers Tags

• On creating a new Notification Run, there is the option to select between two separate Classifications of Notification Run Definitions, depending on which different criteria are made available.
  • Financial
    • Accounts Receivable
    • Wallet
    • Subscription
    • Notification
    • Segment
    • Notification History
  • Customer Care
    • Segments
    • Notification History

  • Status
    colour Blue title Available from CRM.COM R12.0.0

    Reward Offers
    • Reward Offers

• Mandatory Fields must be defined
• Name and Alternative Code must be unique

• Selected Notifications Type
  should be associated to a Communication Template including Tags of the following Types exclusively:
  
  • For Financial Notifications
    • Notification Tags
    • Contact Information Tags
    • Accounts Receivable Tags
  • For Customer Care Notifications
    • Notification Tags
    • Contact Information Tags
    • Entity Tags of the Entity that is included in the related Notification Item

  • Status
    colour Blue title Available from CRM.COM R12.0.0

    For Reward Offers Notifications
    • Reward Offers Tags

• If there is one or more scheduled Run using the same Definition, then a new Run Definition instance is created.  The new Definition will have the same values and Unified Code as the first one, an augmented version number and all the modified information.

• Not Applicable

• Run Definitions cannot be deleted if there exists at least one scheduled or completed Run for that Definition.

• Not Applicable

An auto-generated number which is used to specify the version of each Run Definition. If the version is already in use by a Run, a new Run Definition Version is created each time the Definition is edited.

The VIEW PREVIOUS VERSIONS link enables the user to search and view previous versions of the Definition.

The Type of Notification that will be created when the Notification Run Definitions are used to generate Notifications.
The list of available Notification Types will be filtered according to the Classification selected on creating a new Notification Definition.

• Customer Care Process
• Financial Process

Defines the methods that will be used to log the process run's results. Two options are available:

• Log Processed Successfully and Processed with Errors: This is the default option. If selected then entities successfully processed and failed to be processed will be logged in the Process Run Logs.
• Log Only Processed with Errors: If selected then only entities which failed to be processed will be logged in the Process Run Logs.

A list of Segments which are used to filter the Contact Information, Accounts Receivable or Notification Item that will be notified.

A list of Segments which are used to prevent Contact Information, Accounts Receivable or Notification Items from being notified.

Defines a list of Notifications that should have already been generated for the criterion to be considered as met. It includes the following options:

• Notification Typ
• Life Cycle State
• 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; i.e. the customers have not been sent these Notifications previously.

Available options are the same as those of "Notified Previously".

Filters the Accounts Receivable based on Balance. Two options are available, which can be used in tandem:

• 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 the one specified (<).

Filters the Accounts Receivable based on Outstanding Amount and a specific due date. Two options are available, which can be used in tandem:

• 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 the one specified (<).

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

• Due in X Days: The System checks for Accounts whose outstanding amount is due up to a date equal to the current date + X (a user-defined integer representing a number of days). For example, if the current date is the 23rd of the month and X is set as 5, the System retrieves accounts with outstanding amounts due up to the 28th.
• Due X days ago: The System checks for Accounts whose outstanding amount was due up to a date equal to the current date - X (a user-defined integer representing a number of days). For example, if the current date is the 23rd of the month and X is set as 5, the System retrieves accounts that were due up to the 18th.

Filters the Notifications to be created based on the total outstanding amount of each Notification, calculated using associated respective invoices. Two options are available, which can be used in tandem:

• 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 the one specified (<).

Filters the Accounts Receivable based on the Balance of Wallets owned by that account.  Two options are available, which can be used in tandem:

• 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 the one specified (<).

Filters the Accounts Receivable based on the estimated consumption days of Wallets owned by that account.  Two options are available, which can be used in tandem:

• 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 the one specified (<).

Filters the Accounts Receivable based on the Product estimated consumption days of Wallets owned by that account.  Two options are available, which can be used in tandem:

• 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 the one specified (<).

Filters the Wallets based on the amount that will expire by a defined date.

• Date

Optionally, an amount to be expired by the specified date which is greater than or equal to a specified minimum (amount) can be used to filter the Wallets.

• Minimum Expiration Amount

Filters the Accounts Receivable based on the Type of Subscriptions owned by the Accounts Receivable.

• Run Now
• Run on Specific Date / Time
• Run Repeatedly
• Advanced Scheduling

Refer to Scheduler Task for configuration guidelines.

Determines the maximum number of processed entries that should be affected per Run and the interval between each Run. This is available only if the Repeat and Advanced Repeat options are selected. Throttling settings include:

• Maximum Batch Size 
• Start Again After X UOT (seconds, minutes, hours, days)