Versions Compared

Old Version 1

changes.mady.by.user p_demou (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Back to Customer Events Main Page

Excerpt
hiddentrue

Learn how you can to configure Customer Events Business Definition Definitions that will dictate the overall behavior behaviour of Customer Events

What does this section cover?

Panel
nameblue

Table of Contents

Table of Contents
minLevel2

Navigating to Customer Events Definitions

Info

CONFIGURATION > CRM APPLICATION > CUSTOMER EVENTS > SET UP DEFINITIONS 

 

What are Customer Events Definitions?

Customer Events definitions Events Definitions is a set of business rules used to control the behavior of Customer Events throughout their whole life cycle.

Creating, Editing & Deleting

the behaviour of Customer Events throughout their Life Cycle. 

Customer Event Definitions can be edited, deleted and have their Life Cycle State changed given that Validations & 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.

 

Configuring Customer Events DefinitionImage Added

Anchor
validations
validations
Validations & Restrictions

ActionValidationsRestrictions
General
  • Multiple Customer Events definitions Definitions can exist in the system, but each one should have a unique name Name and alternative codeAlternative Code
  • Only one active Customer Events definition 'Active' Customer Events Definition can exist at any given time
  • If there is no active 'Active' Customer Events Definition exists, then no Customer Events can cannot be created
Create
  • Mandatory Fields must be defined
  • Name and Alternative code must be unique
N/A
  • Not Applicable
Edit
  • Mandatory Fields must be defined
  • Name and alternative code Alternative Code must be unique
N/A
  • Not Applicable
DeleteN/A
  • Not Applicable
  • Cannot be deleted if its the active definition
Customer Events Definition attributes 
  • it is the 'Active' Definition

Anchor
attributes
attributes
Customer Events Definitions Attributes 

Automation It defines on customer events

Name

Description

NumberAn 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.
DescriptionA description for of the definitionDefinition
StateThe 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 

Defines business processes that are automatically applied

to Customer Events

Event Types Processed Immediately
Event Types Processed Immediately

It defines 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.Customer Event Types which can be automatically selected for immediate processing.

Status
colourGreen
titleAvailable from CRM.COM R10.0.0
As from CRM.COM R10, Achievement, Referral and Financial Achievement Customer Events cannot be automatically selected for immediate processing.

Purchase Customer Events Automation
Purchase Customer Events AutomationIt defines Defines a list of invoice Invoice types that will automatically be creating purchase customer events while they are posted.

Defining your own Customer Events Definition tailored to your company's needs

  • Navigate to CONFIGURATION > CRM APPLICATION > CUSTOMER EVENTS > SET UP DEFINITIONS 
  • Either search for an existing one or from the Top Menu click on NEW
     

  • MAIN INFORMATION

    1. Provide the required information

      1. Name

      2. Alternative Code

      3. Description

        Configuring Customer Events DefinitionImage Removed

  • PROCESSING AUTOMATION

    1. PURCHASE CUSTOMER EVENTS AUTOMATION

      1. Click on ADD to select the invoice types that will automatically trigger the creation of purchase customer events, on posting.

        PURCHASE CUSTOMER EVENTS AUTOMATIONImage Removed

    2. EVENT TYPES PROCESSED IMMEDIATELY

      1. Select the customer event types that should be processes immediately automatically by checking their check box.
        EVENT TYPES PROCESSED IMMEDIATELYImage Removed

    • LOG INFORMATION

    Include PageLog Information - GlobalLog Information - Global
  • From the Top Menu click on SAVE

    • Deleting Customer Events Definitions

    Include PageDeleting a record - GlobalDeleting a record - Global

    Changing the Life Cycle State of Customer Events Definition

    Include PageChanging the Life Cycle State of a Definition - GlobalChanging the Life Cycle State of a Definition - Global
    create Purchase Customer Event when posted.
    Payment Medium Brand Automation
    Status
    colourGreen
    titleAvailable from CRM.COM R10.0.0
      
    Defines the rules used to automatically set the Payment Medium Brand on Purchase 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 with a specified Payment Medium identifier but without a Payment Medium Brand.
    Rule NameThe name of the rule, which is generated automatically whenever a new rule is added.
    ConditionsThe criteria that must be met 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 available:

    • Simple Formatting: A selection of condition criteria is presented that can be used to specify the conditions.
    • Advanced Formatting: The conditions are specified by defining a regular expression.
    Payment Medium Identifier Length Range

    The range of inclusive values for the length of the Payment Medium identifier.  If the 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 identifier should begin with the specified value.

    This is applicable only if the formatting is set to 'Simple Formatting'.

    Payment Medium Identifier Ends withIf specified, then the Payment Medium identifier should end with the specified value.

    This is 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 applicable and mandatory only if the formatting is set to 'Advanced Formatting'.

    Payment Medium Type Automation

    Status
    colourGreen
    titleAvailable from CRM.COM R10.0.0

    Defines the rules used to automatically set the Payment Medium Type on Purchase 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 with a specified Payment Medium identifier but without a 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
    ConditionsThe criteria that must be met 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 available:

    • Simple Formatting: A selection of condition criteria is presented that can be used to specify the conditions.
    • Advanced Formatting: The conditions are specified by defining a regular expression.
    Payment Medium Identifier Length Range

    The range of inclusive values for the length of the Payment Medium identifier.  If the 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 identifier should begin with the specified value.

    This is applicable only if the formatting is set to 'Simple Formatting'.

    Payment Medium Identifier Ends withIf specified, then the Payment Medium identifier should end with the specified value.

    This is 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 applicable and mandatory only if the formatting is set to 'Advanced Formatting'.

    Payment Medium Identifier Automation
    Status
    colourGreen
    titleAvailable from CRM.COM R10.0.0

    Defines the rules used to automatically adjust the Payment Medium identifier specified on Purchase or Financial Achievement Customer Events, before saving the Events.
    These rules apply only if the Customer Event is submitted with a specified Payment Medium identifier. The adjustment is performed just before saving the information and once other processing is completed.

    Adjustment Method

    The method that will be used to adjust the Payment Medium identifier. The available options are:

    • No Adjustment (the default Option, which applies to existing Definitions)
    • 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 applicable and mandatory unless the 'No Adjustment' option is selected.

    Processing Rules

    Defines business rules that are automatically applied while creating and processing Customer Events
    Spend Request Customer Events Rules
    Defines business rules that are automatically applied when creating and processing Spend Request Customer Events
    Allow Creating Spend Requests for Specific AmountDetermines whether a specific amount to be spent can be specified on a Spend Request Customer Event. If enabled, then the amount will become mandatory on the Spend Request.
    Minimum Spend Request AmountDefines the minimum amount that can be requested through a Spend Request Customer Event. This information is optional and 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 AmountDefines 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 in CRM.COM) if the requested amount for that combination of products, date / time, unit is more than the Wallet Balance. The Requested Spend Amount is either the amount of the related Purchase Customer Event or the amount specified on the Spend Request Customer Event Type.
    Applicable Classifications

    Defines a list of Spend Request Customer Event Classifications which should be associated with Spend Request Customer Event Types for the rule to be applicable. More than one Classification can be added to the list.

    Log Information
    Log DeatilsThe standard set of Log Details information available in all entities 

     

     

    Panel
    namegrey

    Related Areas

    Filter by label (Content by label)
    showLabelsfalse
    spacesV4Manual
    showSpacefalseexcerpttrue
    labelscustomer-events-basics-r7,customer-events-advanced-r7,customer-events-admin-r7

    heatmap

    Helpful Links

    Panel
    namegrey

    Popular Labels

    Popular Labels
    spaceKeyV4Manual
    style
    Filter by label (Content by label)
    showLabelsfalse
    spacesV4Manual
    showSpacefalse
    labelsglobal