Back to Customer Events Main Page
Excerpt | ||
---|---|---|
| ||
Learn how you can to configure Customer Events Business Definition Definitions that will dictate the overall behavior behaviour of Customer Events |
Panel | ||||
---|---|---|---|---|
| ||||
Table of Contents
|
Navigating to Customer Events Definitions
Info |
---|
CONFIGURATION > CRM APPLICATION > CUSTOMER EVENTS > SET UP DEFINITIONS |
What are Customer Events Definitions?
Customer Events definitions Definitions is a set of business rules used to control the behavior behaviour of Customer Events throughout their whole life cycle. Customer Events Definitions can throughout their Life Cycle.
Customer Event Definitions can be edited, deleted and have their life cycle state Life Cycle State changed given that validations and restrictionsValidations & Restrictions are met.
- Navigate to Customer
- Event Definitions and explore existing records via the Summary page.
Click on the link (name or number) of the record of your interest to
access the Data Entry page and
see more detail.
Use the Actions Menu to create a
NEW Definition, 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 Trail button to view a log of changes effected on the Customer Event under examination.
Check the Validations & Restrictions Table below for a list of available Actions when working with Customer Event, including each Action's related validations and restrictions. View the Attributes Table for a comprehensive description of the Customer Event Definition fields.
Anchor | ||||
---|---|---|---|---|
|
Action | Validations | Restrictions |
---|---|---|
General |
|
|
Create |
|
|
Edit |
|
|
Delete |
|
|
Anchor | ||||
---|---|---|---|---|
|
Events Definitions Attributes
Name | Description | ||||||
---|---|---|---|---|---|---|---|
Number | An auto-generated number that uniquely identifies the customer event definitionCustomer Event Definition. | ||||||
Name* | The name of the definitionDefinition. | ||||||
Alternative Code* | An alternative code for the definition. On creating a new definition it should default to the first letter of each word included in the name (in capitals), if nothing else is specifiedDefinition. Unless otherwise specified, the codes for new Definitions default to the Definition's Name initials in capital letters. | ||||||
Description | A description for of the definitionDefinition | ||||||
State | The state of the definition Definition which can be active or inactive'Active' or 'Inactive'. Only one active definition 'Active' Definition can exist at any pointa time. | ||||||
Processing Automation It defines Defines business processes that are automatically applied on customer eventsto Customer Events | |||||||
Event Types Processed Immediately | |||||||
Event Types Processed Immediately | It defines Defines a list of all the supported customer event types, Customer Event Types which can be enabled or disabled in order to automatically process customer events of that type immediately or notautomatically selected for immediate processing.
| ||||||
Purchase Customer Events Automation | |||||||
Purchase Customer Events Automation | It defines Defines a list of invoice Invoice types that will automatically be creating purchase customer events while they are create Purchase Customer Event when posted. | ||||||
Payment Medium Brand Automation
It defines Defines the rules which are used in order to automatically set the payment medium brand on purchase customer events or financial achievement customer events Payment Medium Brand on Purchase or Financial Achievement Customer Events, based on the format of the specified payment medium Payment Medium identifier. These rules apply only if the customer event Customer Event is submitted having a payment medium identifier specified but no payment medium brandwith a specified Payment Medium identifier but without a Payment Medium Brand. | |||||||
Rule Name | The name of the rule. The rule name , which is generated automatically whenever a new rule is added. | ||||||
Conditions | The conditions criteria that should must be fulfilled in order met to automatically set the specified payment medium brand Payment Medium Brand on the customer event Customer Event that triggered the rule. It is mandatory to specify at least one of the condition criteria. | ||||||
Formatting | The formatting that will be used to set up the conditions. The following options are supportedavailable:
| ||||||
Payment Medium Identifier Length Range | The payment identifier length range (from and to, both values inclusive). If specified then range of inclusive values for the length of the Payment Medium identifier. If the specified payment medium identifier should be within that range in order for the rule to be applied (it should be greater or equal the from value and less or equal the to value)This is visible and range is specified and the values are within the range, the rule is applied. This is applicable only if the formatting is set to "'Simple Formatting"'. | ||||||
Payment Medium Identifier Begins with | If specified, then the payment medium Payment Medium identifier should begin with the specified value. This is visible and applicable only if the formatting is set to "'Simple Formatting"'. | ||||||
Payment Medium Identifier Ends with | If If specified, then the payment medium Payment Medium identifier should end with the specified value. This is visible and applicable only if the formatting is set to "'Simple Formatting"'. | ||||||
Regular Expression | The regular expression that will be used to evaluate the rule against the specified payment medium Payment Medium identifier. This is visible, applicable and mandatory only if the formatting is set to "'Advanced Formatting"'. | ||||||
Payment Medium Type Automation
used in orderto automatically set the payment medium type on purchase customer events or financial achievement customer eventsPayment Medium Type on Purchase or Financial Achievement Customer Events, based on the format of the specified payment mediumPayment Medium identifier. ThoseThese rules apply only if the customer eventCustomer Event is submitted having a payment medium identifier specified but no payment medium typewith a specified Payment Medium identifier but without a Payment Medium Type. | |||||||
Rule Name | The name of the rule. The rule name is generated automatically whenever a new rule is added. | ||||||
Automatically set to Payment Medium Type | The Payment Medium Type that will automatically be set on the customer event, Customer Event if the conditions are fulfilled | ||||||
Conditions | The conditions The criteria that should must be fulfilled in order met to automatically set the specified payment medium type on the customer event Payment Medium Type on the Customer Event that triggered the rule. It is mandatory to specify at least one of the condition criteria. | ||||||
Formatting | The formatting that will be used to set up the conditions. The following options are supportedavailable:
| ||||||
Payment Medium Identifier Length Range | The payment identifier length range (from and to, both values inclusive). If specified then range of inclusive values for the length of the Payment Medium identifier. If the specified payment medium identifier should be within that range in order for the rule to be applied (it should be greater or equal the from value and less or equal the to value)This is visible and range is specified and the values are within the range, the rule is applied. This is applicable only if the formatting is set to "'Simple Formatting"'. | ||||||
Payment Medium Identifier Begins with | If specified, then the payment medium Payment Medium identifier should begin with the specified value. This is visible and applicable only if the formatting is set to "'Simple Formatting"'. | ||||||
Payment Medium Identifier Ends with | If If specified, then the payment medium Payment Medium identifier should end with the specified value. This is visible and applicable only if the formatting is set to "'Simple Formatting"'. | ||||||
Regular Expression | The regular expression that will be used to evaluate the rule against the specified payment medium Payment Medium identifier. This is visible, applicable and mandatory only if the formatting is set to "'Advanced Formatting"'. | ||||||
Payment Medium Identifier Automation
It defines Defines the rules which are used in order to automatically adjust the payment medium Payment Medium identifier specified on purchase customer events or financial achievement customer eventsPurchase or Financial Achievement Customer Events, before saving the customer eventsEvents. | |||||||
Adjustment Method | The method that will be used in order to adjust the payment medium Payment Medium identifier. The supported available options are the following:
| ||||||
Number of Characters | The number of characters (last Last or firstFirst) that should be kept after adjusting the payment medium Payment Medium identifier. This is visible, applicable and mandatory unless the no adjustment 'No Adjustment' option is specifiedselected. | ||||||
Processing Rules
| |||||||
Spend Request Customer Events Rules It defines Defines business rules that are automatically applied while when creating and processing spend request customer events | Allow creating spend requests for specific amount | It defines ifSpend Request Customer Events | |||||
Allow Creating Spend Requests for Specific Amount | Determines whether a specific amount to be spend spent can be specified on spend request customer eventsa Spend Request Customer Event. If it is enabled, then the spend amount will become mandatory on the spend requestSpend Request. | ||||||
Minimum Spend Request Amount | It defines Defines the minimum amount that can be requested through a spend request customer eventSpend Request Customer Event. This information is optional and is applicable only if the "Allow creating spend requests for specific amountCreating Spend Requests for Specific Amount" is checked. If not specified, then the minimum spend request amount Spend Request Amount will not be validated. | ||||||
Maximum Spend Request Amount | It defines Defines the maximum amount that can be requested through a spend request customer eventSpend Request Customer Event. This information is optional and is applicable only if the "Allow creating spend requests Spend Requests for specific amount" is checked. If not specified then the maximum spend request Spend Request amount will not be validated. | ||||||
Reject Spend Requests if If the Requested Spend Amount is not Not Covered | If enabled, then spend requests Spend Requests will be rejected (and not created within in CRM.COM) if the requested spend amount is not covered (i.e. the wallet balance for amount for that combination of products, date / time, unit is less more than the requested amount)Wallet Balance. The requested spend amount Requested Spend Amount is either the amount of the related purchase customer event Purchase Customer Event or the specific spend amount that is specified on the spend request customer eventSpend Request Customer Event Type. | ||||||
Applicable Classifications | Defines a list of spend request customer event classifications Spend Request Customer Event Classifications which should be related with spend request customer events in order associated with Spend Request Customer Event Types for the rule to be applicable. More than one classifications Classification can be added in that list.to the list. | ||||||
Log Information | |||||||
Log Deatils | The standard set of Log Details information available in all entities |
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Related Areas
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Helpful Links
|