Back to Notifications Main Page
Excerpt | ||
---|---|---|
| ||
Learn how you can configure and execute Notification Runs |
to configure Notification Run Definitions that will determine the overall behaviour of Notification Runs |
Panel | ||||
---|---|---|---|---|
| ||||
Table of Contents
|
Navigating to Notification Run Definitions
Info |
---|
CRM > NOTIFICATIONS > PERFORM NOTIFICATION RUNS |
What are Notification Run Definitions?
Notification Runs Run Definitions are used to log the execution of notification run definitions, that were performed in order to generate notifications and all the information that the notification is referring to.
Notification Runs can be performed only within an effective notification run definition.
A new Notification Run is created each time a recurring Notification Run Definitions is submitted. Whenever a run has been submitted, the notification run added to the scheduler to be executed based on the specified run definition scheduling.
In order to modify the scheduling information of a submitted Notification Run you can Edit the definition.
Creating, Editing & Deletingdefine the rules by which Notification Runs, responsible for creating Notifications will be executed. The two Classifications of Notification Run Definitions are 'Financial' and 'Customer Care'. Each Classification supports separate Entities which result in the generation of different types of information. The Classification also determines the conditions available to be set on/by? each Run Definition.
- Financial Classification
This is related to Financial information of the supported entities, such as balances and outstanding debts.- Subscription
- Bills
- Wallets
- Wallet Product Consumption
- Customer Care Classification
This is related to Customer Care information of the supported entities, such as confirmation of payments, award points earned, redeemed or expired and Goods and Services added to a Subscription.- Subscriptions
- Jobs
- Activities
- Leads
- Service Requests
- Rewards Participants
- Award Transactions
- Spend Transactions
- Award Expiration Transaction
- Payment Gateway Cards
- Payment Gateway Requests
- Payments
- Buy in Advance Request
Run Definitions must be submitted once created and will be executed once or on a recurring basis, based on the defined scheduling settings. Once a Definition is executed, a Process Run is logged, and once the Run is completed, the log information is available in the respective section.
The user has the option to delete the specific Run as long as it is not yet executed (still in 'Draft' state).
A Definition must be in an 'Effective' Life Cycle State to be submitted. The state can be changed between 'Effective' and 'Not Effective' using a dedicated action.
- Navigate to Notification Run Definitions and explore existing entries via the Summary page.
Click on the link (Name or Number) of the entry of your interest to access the Data Entry page and see more detail, or submit the Definition.
Select a Classification ('Financial' or 'Customer Care') and use the Actions Menu to create a NEW Definition.
Use the Actions Menu to modify (EDIT), or DELETE an existing one.
Use BACK to return to the Summary page and CANCEL to revert any unwanted changes made to the Definition.
- Click on the Audit Log button to view a log of changes performed on the displayed Notification Run Definition.
Check the Validations & Restrictions Table below for a list of available Actions when working with Notification Run, including each Action's related validations, restrictions and additional information. View the Attributes Table for a comprehensive description of the Notification Run Definition fields.
Anchor | ||||
---|---|---|---|---|
|
Action | Validations | Restrictions | Additional Information | ||
---|---|---|---|---|---|
General |
| N/A | |||
Create | N/A|||||
Create |
|
|
For more information on criteria check out the Notification Run Attributes table below
| ||
Edit |
|
| Edit | N/A
|
|
Delete | Notification run definitions
|
| N/A | Save
Mandatory Fields:
Anchor |
---|
Notification Run attributes
|
- Customer Care Notifications :
At least one segment MUST be specified (Either in Included or Excluded)
At least one criterion MUST be specified (from any of the available criteria)
|
An * indicates a field is mandatory
Name | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Main Information | |||||||||
Name* | The name of the notification run definitionNotification Run Definition. | ||||||||
Alternative Code | The alternative code of the notification run definitionNotification Run Definition. Unless otherwise specified, the Alternative Codes for new entries default to the Name initials in capital letters. | ||||||||
Description | A description of the notification run definitionNotification Run Definition. | ||||||||
Life Cycle State | The life cycle state Life Cycle State of the notification run definitionNotification Run Definition. The supported values are effective and not effective. Only effective notification run definitions 'Effective' and 'Not Effective'. Only 'Effective' Notification Run Definitions can be used to generate notificationsNotifications. | ||||||||
Unified Code | An auto-generated code which is used to group the various instances of the notification run definitionsNotification Run Definitions | ||||||||
Version | An auto-generated number which is used to specify the version of each notification run definition. New notification run definition versions are created each time they are edited, if they are already been used to generate notificationsRun 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. | ||||||||
Scheduled Date | This is a read Read-only field which is available once you schedule a Run is scheduled. The date provided shows the latest date that the run Run is scheduled to be executed on. | ||||||||
Notification Type* | The type Type of notification Notification that will be created whenever the notification run definitions when the Notification Run Definitions are used to generate notificationsNotifications.
| 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:
| Criteria | ||||||||
Criteria - Segment Criteria | |||||||||
Included in Segment | Criteria -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 .
| ||||||||
Not Included in Segment | 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" | ||||||||
| |||||||||
Excluded from Segments | A list of Segments which are used to prevent Contact Information, Accounts Receivable or Notification Items from being notified.
| ||||||||
Notification History Criteria | |||||||||
Notified Previously | 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:
| ||||||||
Not Notified Previously | 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". | ||||||||
Criteria - Accounts Receivable Criteria
| |||||||||
Accounts Receivable Balance | It filters the accounts receivable Filters the Accounts Receivable based on their balanceBalance. Two options are available, which can be used combinedin tandem:
| ||||||||
Accounts Receivable Outstanding Amount | 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:
The due date can be specified in one of the following ways:
| ||||||||
Accounts Receivable Classification | It filters the accounts receivable Filters the Accounts Receivable based on a list of accounts receivable classificationsAccounts Receivable Classifications. | ||||||||
Accounts Receivable Credit Rating | It filters the accounts receivable Filters the Accounts Receivable based on a list of accounts receivable credit ratings | Criteria - Notification CriteriaAccounts Receivable Credit Ratings. | |||||||
Notification Criteria
| |||||||||
Total Outstanding Amount per Notification | 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:
| ||||||||
Criteria - Wallet Criteria
| |||||||||
Wallet Balance | 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:
| ||||||||
Wallet Estimated Consumption Days | 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:
| ||||||||
Wallet Product Estimated Consumption Days | 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:
| Criteria - Subscription Criteria
| |||||||
Wallet Amount Expiration Up To Date
| Filters the Wallets based on the amount that will expire by a defined 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.
| ||||||||
Subscription Criteria
| |||||||||
Subscription Types | 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. | ||||||||
Billing Term Schemes | It filters the accounts receivable Filters the Accounts Receivable based on the billing term schemes of subscriptions Billing Term Schemes of Subscriptions owned by the accounts receivable. Multiple billing term schemes can be defined.Accounts Receivable. | ||||||||
Price Plans | It filters the accounts receivable Filters the Accounts Receivable based on the price plans Price Plans of subscriptions Subscriptions owned by the accounts receivable. Multiple price plans can be definedAccounts Receivable. | ||||||||
Billing Frequencies | It filters the accounts receivable Filters the Accounts Receivable based on the billing frequencies Billing Frequencies of subscriptions Subscriptions owned by the accounts receivable. Multiple billing frequencies can be defined.Accounts Receivable. | ||||||||
Binding Periods | It filters the accounts receivable Filters the Accounts Receivable based on the binding periods Binding Periods of subscriptions Subscriptions owned by the accounts receivable. Multiple binding periods can be defined.Accounts Receivable. | ||||||||
Binding State | It filters the accounts receivable Filters the Accounts Receivable based on the binding state Binding State of subscriptions owned by the accounts receivable. | ||||||||
Notification Runs | |||||||||
Notification Run information | It displays all the notification runs which were performed based on the specific notification run definition and displays all the notification run information as described in Reading Notification Run Logs |
Configuring a Notification Run tailored to your company's needs
MAIN INFORMATION
Provide the required information
Name
Alternative Code
Notification Type
Life Cycle State: Is automatically set
- Version: Is automatically set to 1 (for new notification runs)
Description
CRITERIA
Accounts Receivable
Outstanding Amount
Wallet
Subscription
Notification
Outstanding Amount Per NotificationSegment
Notification History
SCHEDULING SETTINGS
THROTTLING SETTINGS
Provide the required informationLOG INFORMATION
Executing a Notification Run
Modifying a Notification Run
Deleting a Notification Run
Deleting a scheduled job of the specific Run
Changing the Life Cycle State of a Notification Run definition
Reading Notification Run Logs
Process Runs
The following information is available regarding the Notification RunProcessed With Errors: Drill down including the entities that were not successfully processed thus no notifications were created for the specified entities
Info |
---|
Visit Creating Notifications to find out more information regarding created Notifications. |
Subscriptions owned by the Accounts Receivable. | |
Scheduling Setting | |
---|---|
Scheduling Settings | Method - The following options are available:
Refer to Scheduler Task for configuration guidelines. |
Throttling Settings | |
Throttling Settings | 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:
|
Process Runs | |
Process Runs | Displays the Runs that were executed for the specific Definition. Each Run includes the Subscriptions that were processed. In case of an error, the error code and description is displayed. |
Log Information | |
Log Details | The standard set of Log Details information available in all entities. |
Note |
---|
View Understanding Notifications for business examples related to Notification Runs. |
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Related Areas
|
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Popular Labels Popular Labels | | |||||||
spaceKey | V4Manual | style | heatmap
Filter by label (Content by label) | ||||||||
---|---|---|---|---|---|---|---|---|
|