Skip to end of banner
Go to start of banner

Configuring Customer Events Definition

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Table of Contents

Navigating to Customer Events Definitions

CONFIGURATION > CRM APPLICATION > CUSTOMER EVENTS > SET UP DEFINITIONS 

 

What are Customer Events Definitions?

Customer Events  definitions is a set of business rules used to control the behavior of Customer Events  throughout their whole life cycle. Customer Events Definitions can be edited, deleted and have their life cycle state changed given that validations and restrictions are met.

Navigate to Customer Events Definitions and explore existing records via the Summary page. Click on the link (name or number) of the record of your interest to enter the Data Entry page and have a better look of the available information. Use the Actions Menu to create a new (NEW) Customer Events Definitions , modify (EDIT) or delete (DELETE) an existing one. Use the (BACK) link to go back to the summary page and (CANCEL) to cancel any unwanted changes made to the Customer Events Definitions . Check out the attributes table below for a thorough explanation of the information kept for Customer Events Definitions  and the Validations&Restrictions table to find out validations and restrictions applicable when working with Customer Events Definitions .

 

CUSTOMER EVENTS DEFINITION

Validations & Restrictions

ActionValidationsRestrictions
General
  • Multiple Customer Events definitions can exist in the system, but each one should have a unique name and alternative code
  • Only one active Customer Events definition can exist at any given time
  • If no active Customer Events Definition exists, then no Customer Events can be created
Create
  • Mandatory Fields must be defined
  • Name and Alternative code must be unique
  • Not Applicable
Edit
  • Mandatory Fields must be defined
  • Name and alternative code must be unique
  • Not Applicable
Delete
  • Not Applicable
  • Cannot be deleted if it is the active definition

Customer Events Definition attributes 

Name

Description

NumberAn auto generated number that uniquely identifies the customer event definition
Name*The name of the definition
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 specified
DescriptionA description for the definition
StateThe state of the definition which can be active or inactive. Only one active definition can exist at any point

Processing Automation 

It defines business processes that are automatically applied on customer events

Event Types Processed Immediately
Event Types Processed Immediately

It defines a list of all the supported customer event types, which can be enabled or disabled in order to automatically process customer events of that type immediately or not.

AVAILABLE FROM CRM.COM R10.0.0 As from CRM.COM R10 Achievement, Referral and Financial Achievement customer events will not be allowed to be set as "processed immediately"

Purchase Customer Events Automation
Purchase Customer Events AutomationIt defines a list of invoice types that will automatically be creating purchase customer events while they are posted.
Payment Medium Brand Automation AVAILABLE FROM CRM.COM R10.0.0  
It defines rules which are used in order to automatically set the payment medium brand on purchase customer events or financial achievement customer events based on the format of the specified payment medium identifier.
These rules apply only if the customer event is submitted having a payment medium identifier specified but no payment medium brand
Rule NameThe name of the rule. The rule name is generated automatically whenever a new rule is added.
ConditionsThe conditions that should be fulfilled in order to automatically set the specified payment medium brand 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 supported:

  • Simple Formatting: If this option is selected then a selection of condition criteria is presented, that can be used to specify the conditions
  • Advanced Formatting: If this option is selected then the conditions are specified by defining a regular expression
Payment Medium Identifier Length Range

The payment identifier length range (from and to, both values inclusive). If specified then the length of 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 applicable only if the formatting is set to "Simple Formatting"

Payment Medium Identifier Begins with

If specified then the 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 specified then the 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 identifier.

This is visible, applicable and mandatory only if the formatting is set to "Advanced Formatting"

Payment Medium Type Automation AVAILABLE FROM CRM.COM R10.0.0
It defines rules which are used in order to automatically set the payment medium type on purchase customer events or financial achievement customer events based on the format of the specified payment medium identifier. Those rules apply only if the customer event is submitted having a payment medium identifier specified but no payment medium type
Rule NameThe name of the rule. The rule name is generated automatically whenever a new rule is added.
Automatically set to Payment Medium TypeThe Payment Medium Type that will automatically be set on the customer event, if the conditions are fulfilled
Conditions The conditions that should be fulfilled in order to automatically set the specified 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 supported:

  • Simple Formatting: If this option is selected then a selection of condition criteria is presented, that can be used to specify the conditions
  • Advanced Formatting: If this option is selected then the conditions are specified by defining a regular expression
Payment Medium Identifier Length Range

The payment identifier length range (from and to, both values inclusive). If specified then the length of 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 applicable only if the formatting is set to "Simple Formatting"

Payment Medium Identifier Begins with

If specified then the 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 specified then the 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 identifier.

This is visible, applicable and mandatory only if the formatting is set to "Advanced Formatting"

Payment Medium Identifier Automation AVAILABLE FROM CRM.COM R10.0.0

It defines rules which are used in order to automatically adjust the payment medium identifier specified on purchase customer events or financial achievement customer events, before saving the customer events.
These rules apply only if the customer event is submitted having a payment medium identifier specified. Note that the adjustment is done just before saving the information and after any other processing is completed

Adjustment Method

The method that will be used in order to adjust the payment medium identifier. The supported options are the following:

  • No Adjustment (Default Option - Existing Definitions should be considered as No Adjustment)
  • Keep X Last Characters
  • Keep X First Characters
Number of CharactersThe number of characters (last or first) that should be kept after adjusting the payment medium identifier. This is visible, applicable and mandatory unless the no adjustment option is specified

Processing Rules

AVAILABLE FROM CRM.COM R9

It defines business rules that are automatically applied while creating and processing customer events
Spend Request Customer Events Rules
It defines business rules that are automatically applied while creating and processing spend request customer events
Allow creating spend requests for specific amountIt defines if a specific amount to be spend can be specified on spend request customer events. If it is enabled then the spend amount will become mandatory on the spend request.
Minimum Spend Request AmountIt defines the minimum amount that can be requested through a spend request customer event. This information is optional and is applicable only if the "Allow creating spend requests for specific amount" is checked. If not specified then the minimum spend request amount will not be validated
Maximum Spend Request AmountIt defines the maximum amount that can be requested through a spend request customer event. This information is optional and is applicable only if the "Allow creating spend requests for specific amount" is checked. If not specified then the maximum spend request amount will not be validated
Reject Spend Requests if the Requested Spend Amount is not CoveredIf enabled then spend requests will be rejected (and not created within CRM.COM) if the requested spend amount is not covered (i.e. the wallet balance for that combination of products, date / time, unit is less than the requested amount). The requested spend amount is either the amount of the related purchase customer event or the specific spend amount that is specified on the spend request customer event
Applicable Classifications

Defines a list of spend request customer event classifications which should be related with spend request customer events in order for the rule to be applicable. More than one classifications can be added in that list.

  • No labels