• 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

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)

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 method to be used for logging process run's results. Two options are available:

• Log Processed Successfully and Processed with Errors: If selected, both entities successfully processed and failed ones will be logged in the Process Run Log.
• Log Only Processed with Errors: If selected then only entities which failed to be processed will be logged in the Process Run Log.

A list of segments Segments which are used to filter in the contact information or the accounts receivable the Contact Information, Accounts Receivable or Notification Item that will be notified, and optionally the notification information. The criteria consist .

• 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"

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

Defines a list of notifications Notifications that should have already be been generated in the pastfor the criterion to be considered as met. It consist of includes the following valuesoptions:

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

Defines a list of notifications Notifications that should not already exist. Its values ; i.e. the customers have not been sent these Notifications previously.

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

It filters the accounts receivable Filters the Accounts Receivable based on their balanceBalance. Two options are available, which can be used combinedin 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 (<).

It filters the accounts receivable based on their outstanding amount Filters the Accounts Receivable based on Outstanding Amount and a specific due date. Two options are available, which can be used combinedin 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.

It filters the notifications that will Filters the Notifications to be created based on the total outstanding amount of each notificationNotification, as calculated based on the related calculated using associated respective invoices. Two options are available, which can be used combinedin 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 (<).

It filters the accounts receivable Filters the Accounts Receivable based on the wallet balance Balance of wallets Wallets owned by that account.  Two options are available, which can be used combinedin 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 (<).

It filters the accounts receivable Filters the Accounts Receivable based on the wallet estimated consumption days of wallets Wallets owned by that account.  Two options are available, which can be used combinedin 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 (<).

It filters the accounts receivable Filters the Accounts Receivable based on the wallet product Product estimated consumption days of wallets Wallets owned by that account.  Two options are available, which can be used combinedin 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

It filters the accounts receivable Filters the Accounts Receivable based on the type Type of subscriptions Subscriptions owned by the accounts receivable. Multiple subscription types can be defined. 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)