| Excerpt | ||
|---|---|---|
| ||
Learn to configure Access Token Business Definition that will dictate the overall behaviour of Access Tokens |
Back to Access Tokens Main Page
| Panel | ||||
|---|---|---|---|---|
| ||||
Table of Contents
|
Navigating to Access Token Definitions
| Info |
|---|
CONFIGURATION > FOUNDATION APPLICATION > ACCESS TOKENS > SET UP ACCESS TOKEN DEFINITIONS |
What are Access Token Definitions?
Access Token Definitions are used to control the creation of Access Tokens, by defining the policies governing the format of the Access Token User Identifier, Pass Code and Authentication Code. You can define whether Access Tokens can be created without an Identifier and Pass Code or deactivated when their last entity association (Rewards Participant or Accounts Receivable) is removed.
Additional settings relating to Access Tokens may also be defined, concerning Accounts Receivable and Rewards Participants, as well as Communication (Access Tokens can be automatically communicated to customers once created).
Only Definitions with an 'Effective' Life Cycle State are applicable. The Life Cycle State can be changed between 'Effective' and 'Not Effective' using a dedicated action.
- Navigate to Access Token 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 to 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.
Check the Validations & Restrictions Table below for a list of available Actions when working with Access Token Definitions, including each Action's related validations and restrictions. View the Attributes Table for a comprehensive description of the Access Token Definitions fields.
Validations & Restrictions Table
| Action | Validations | Restrictions |
|---|---|---|
| General |
|
|
| Create |
|
|
| Save |
|
|
| Edit |
|
|
| Delete |
|
|
Attributes Table
An * indicates a field is mandatory
Name | Description | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Main Information | |||||||||||||||||||||
| Number | An auto-generated number that uniquely identifies the Access Token Definitions | ||||||||||||||||||||
| Name* | The name of the Definition | ||||||||||||||||||||
| Alternative Code* | An alternative code for the Definition. Unless otherwise specified, the codes for new Definitions default to the Definition's Name initials in capital letters. | ||||||||||||||||||||
| Description | A description of the Definition | ||||||||||||||||||||
| State | The state of the Definition which can be 'Active' or 'Inactive'. Only one 'Active' Definition can exist at a time. | ||||||||||||||||||||
SETTINGS: The settings related to the Access Tokens
| |||||||||||||||||||||
| Identifier Settings | |||||||||||||||||||||
| Automatic Creation Method | Determines whether Identifiers should be created automatically and the method used to create them. The following options can be selected:
| ||||||||||||||||||||
| Format | Determines how the identifiers are formatted. The options are:
| ||||||||||||||||||||
| Minimum Length | The minimum required number of characters Theminimumrequirednumberofcharacters(alphabetical, numerical, or special) of the Identifier.
| ||||||||||||||||||||
| Minimum Number Of Alphabetical Characters (a-z) | The minimum number of alphabetical characters from 'a' to 'z' that should be included in the Identifier.
| ||||||||||||||||||||
| Minimum Number Of Integers (0-9) | The minimum number of integers from '0' to '9' that should be included in the Identifier.
| ||||||||||||||||||||
| Minimum Number Of Other Special Characters | The minimum number of special characters that should be included in the Identifier.
| ||||||||||||||||||||
| Pass Code Settings | |||||||||||||||||||||
| Automatic Creation Method | Determines whether Pass Codes should be created automatically and the method used to create them. The following options can be selected:
| ||||||||||||||||||||
| Minimum Length | The minimum required number of characters Theminimumrequirednumberofcharacters(alphabetical, numerical, or special) of the Pass Code.
| ||||||||||||||||||||
| Minimum Number Of Alphabetical Characters (a-z) | The minimum number of alphabetical characters from 'a' to 'z' that should be included in the Pass Code.
| ||||||||||||||||||||
| Minimum Number Of Integers (0-9) | The minimum number of integers from '0' to '9' that should be included in the Pass Code.
| ||||||||||||||||||||
| Minimum Number Of Other Special Characters | The minimum number of special characters that should be included in the Pass Code.
| ||||||||||||||||||||
| Authentication Code Settings | |||||||||||||||||||||
| Automatic Creation Method | Determines whether Authentication Codes should be created automatically and the method used to create them. The following options can be selected:
| ||||||||||||||||||||
| Format | Determines how the Authentication Codes are formatted. The options are:
| ||||||||||||||||||||
| Minimum Length | The minimum required number of characters Theminimumrequirednumberofcharacters(alphabetical, numerical, or special) of the Authentication Code.
| ||||||||||||||||||||
| Minimum Number Of Alphabetical Characters (a-z) | The minimum number of alphabetical characters from 'a' to 'z' that should be included in the Authentication Code.
| ||||||||||||||||||||
| Minimum Number Of Integers (0-9) | The minimum number of integers from '0' to '9' that should be included in the Authentication Code.
| ||||||||||||||||||||
| Minimum Number Of Other Special Characters | The minimum number of special characters that should be included in the Authentication Code.
| ||||||||||||||||||||
| Automation Settings | |||||||||||||||||||||
| Allow Creating Access Tokens with No Identifier and Pass Code | If checked, one can create Access Tokens without specifying an Identifier and Pass Code. | ||||||||||||||||||||
| Set Access Tokens as 'Not Effective' on Removing the Last Entity Association | If checked, an Access Token will be set a 'Not Effective' if it is no longer associated with an entity. | ||||||||||||||||||||
| Accounts Receivable Settings | |||||||||||||||||||||
| Allow Creating Access Tokens on Creating Accounts Receivable | If checked, it will be possible to generate Access Tokens automatically when creating a new Accounts Receivable. | ||||||||||||||||||||
| Always Require at Least One Access Token | If checked, it will be mandatory to specify an Access Token for each Accounts Receivable. | ||||||||||||||||||||
| Maximum Number of Access Tokens | Defines the maximum number of Access Tokens that can be related to each Accounts Receivable. | ||||||||||||||||||||
| Require Verification | If checked, Access Tokens generated automatically when creating a new Accounts Receivable will require verification. They will have a 'Pending Verification' Life Cycle State. A verification code will also be generated automatically. | ||||||||||||||||||||
| Rewards Participants Settings | |||||||||||||||||||||
| Allow Creating Access Tokens on Creating Rewards Participants | If checked, it will be possible to generate Access Tokens automatically when creating a new Rewards Participant. | ||||||||||||||||||||
| Always Require at Least One Access Token | If checked, it will be mandatory to specify an Access Token for each Rewards Participant. | ||||||||||||||||||||
| Maximum Number of Access Tokens | Defines the maximum number of Access Tokens that can be related with each Rewards Participant. | ||||||||||||||||||||
| Require Verification | If checked, Access Tokens generated automatically when creating new Rewards Participants will require verification. They will have a 'Pending Verification' Life Cycle State. A verification code will also be generated automatically. | ||||||||||||||||||||
| Global Settings | |||||||||||||||||||||
Accounts Receivable Settings | |||||||||||||||||||||
| Allow Creating Access Tokens on Creating Accounts Receivable | If checked, it will be possible to generate Access Tokens automatically when creating a new Accounts Receivable. | ||||||||||||||||||||
| Always Require at Least One Access Token | If checked, it will be mandatory to specify an Access Token for each Accounts Receivable. | ||||||||||||||||||||
| Maximum Number of Access Tokens | Defines the maximum number of Access Tokens that can be related to each Accounts Receivable. | ||||||||||||||||||||
| Require Verification | If checked, Access Tokens generated automatically when creating a new Accounts Receivable will require verification. | ||||||||||||||||||||
| Required Number of Access Tokens per Access Token Classification | Determines the minimum and maximum number of Access minimumandmaximumnumberofAccess Tokens of a specific Classification that can be associated with an Accounts Receivable.
| ||||||||||||||||||||
Required Verification of Access Tokens per Access Token Classification
| Green
| R10
| |||||||||||||||||||
| Allow Creating Access Tokens on Creating Rewards Participant | If checked, it will be possible to generate Access Tokens automatically when creating a new Rewards Participant. | ||||||||||||||||||||
| Always Require at Least One Access Token | If checked, it will be mandatory to specify an Access Token for each Rewards Participant. | ||||||||||||||||||||
| Maximum Number of Access Tokens | Defines the maximum number of Access Tokens that can be related with each Rewards Participant. | ||||||||||||||||||||
| Require Verification | If checked, Access Tokens generated automatically when creating new Rewards Participants will require verification. They will have a 'Pending Verification' Life Cycle State. A verification code will also be generated automatically. | ||||||||||||||||||||
| Required Number of Access Tokens per Access Token Classification | Determines the minimum and maximum number of Access Tokens of a specific Classification that can be associated with an Accounts Receivable. Defines a list of Access Tokens Classifications that will require verification when these Access Tokens are created directly through the process of creating new Accounts Receivable. If no classifications are defined then Access Tokens generated automatically when creating a new Accounts Receivable will require verification, regardless of classification. | ||||||||||||||||||||
Rewards Participant Settings | |||||||||||||||||||||
| Allow Creating Access Tokens on Creating Rewards Participant | If checked, it will be possible to generate Access Tokens automatically when creating a new Rewards Participant. | ||||||||||||||||||||
| Always Require at Least One Access Token | If checked, it will be mandatory to specify an Access Token for each Rewards Participant. | ||||||||||||||||||||
| Maximum Number of Access Tokens | Defines the maximum number of Access Tokens that can be related with each Rewards Participant. | ||||||||||||||||||||
| Require Verification | If checked, Access Tokens generated automatically when creating new Rewards Participants will require verification. They will have a 'Pending Verification' Life Cycle State and a verification code will be generated automatically. | ||||||||||||||||||||
| Required Number of Access Tokens per Access Token Classification | Determines the minimumandmaximumnumberofAccess Tokens of a specific Classification that can be associated with an Accounts Receivable. | Communication Template | The template used to send the communication
| ||||||||||||||||||
| Communication Settings | |||||||||||||||||||||
| Accounts Receivable Settings Define if Access Tokens should be communicated when they are used on Accounts Receivable | |||||||||||||||||||||
| Enable on Assigning Access Tokens to Accounts Receivable | If checked, Access Tokens will automatically be communicated when added to an Accounts Receivable. | ||||||||||||||||||||
| Communication Template | The template used to send the communication. The Communication Template should have media set to email or SMS - and should be related with an Access Token entity. This information is mandatory if the Communication Setting is 'Enabled'. | ||||||||||||||||||||
| Communication Queue External System | The system that will be used to send the communication. If a Communication Queue External System is specified, the communication will be created automatically and added to the communication queue, but it will not be sent. | ||||||||||||||||||||
| Rewards Participant Settings Define if Access Tokens should be communicated when they are used on rewards participants | |||||||||||||||||||||
| Enable on Assigning Access Tokens to Rewards Participants | If checked, Access Tokens will automatically be communicated when added to a Rewards Participant. | ||||||||||||||||||||
| |||||||||||||||||||||
Required Verification of Access Tokens per Access Token Classification
| Defines a list of Access Tokens Classifications that will require verification when these Access Tokens are created directly through the process of creating new Rewards Participant. If no classifications are defined then Access Tokens generated automatically when creating a new Rewards Participant will require verification, regardless of classification. | ||||||||||||||||||||
| Communication Settings | |||||||||||||||||||||
| Accounts Receivable Settings Define if Access Tokens should be communicated when they are used on Accounts Receivable | |||||||||||||||||||||
| Enable on Assigning Access Tokens to Accounts Receivable | If checked, Access Tokens will automatically be communicated when added to an Accounts Receivable. If checked, the following options are mandatory to be provided:
| ||||||||||||||||||||
Enable on Resetting Access Token Pass Code
| If checked, Access Tokens will automatically be communicated when their Pass Code is Reset. If checked, the following options are mandatory to be provided:
| ||||||||||||||||||||
| Communication Queue External System | The system that will be used to send the communication. If a Communication Queue External System is specified, the communication will be created automatically and added to the communication queue, but it will not be sent. | ||||||||||||||||||||
| Rewards Participant Settings Define if Access Tokens should be communicated when they are used on rewards participants | |||||||||||||||||||||
| Enable on Assigning Access Tokens to Rewards Participants | If checked, Access Tokens will automatically be communicated when added to a Rewards Participant. If checked, the following options are mandatory to be provided:
| ||||||||||||||||||||
Enable on Resetting Access Token Pass Code
| If checked, Access Tokens will automatically be communicated when their Pass Code is Reset. If checked, the following options are mandatory to be provided:
| ||||||||||||||||||||
| Communication Queue External System | The system that will be used to send the communication. If a Communication Queue External System is specified, the communication will be created automatically and added to the communication queue, but it will not be sent. | ||||||||||||||||||||
| LOG INFORMATION | |||||||||||||||||||||
| Log Information | The standard set of Log Details information available in all entities | ||||||||||||||||||||
| Note |
|---|
View /wiki/spaces/WIP/pages/10010273 Applying Access Token Definition Settings on Access Tokens for a complete overview of how the system behaves on each setting. |
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Related Areas
|
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Helpful Links
|