Back to Wallets Main Page
| Excerpt |
|---|
|
Learn to configure Wallet Balance Expiration Run Definition Definitions that will dictate determine the overall behaviour of Wallet Balance Expiration RunRuns |
| Status |
|---|
| colour | Green |
|---|
| title | Available from CRM.COM R10.0.0 |
|---|
|
Navigating to Wallet Balance Expiration Run Definitions
| Info |
|---|
FINANCE > WALLETS > PERFORM WALLET BALANCE EXPIRATION RUNS |
What are Wallet Balance Expiration Run Definitions?
Wallet Balance Expiration Run Definitions are used to define the rules by which Runs will be performed, to identify the Wallet amount that should be expired , and debit the Wallet for the unspent amount of money (the identification process is performed based on the already specified Expiration Date and the amount that was already spent and debit the Wallet for the amount of money that was not spent). The resulted resulting debit that reflects the expired amount , is directly allocated against the credit the expired credit amount that expired.
The Expiration Date is specified either manually or automatically, as part of a Reward Offer Award that has a specific Expiration Date and it is available on Credit and Transfer Wallet Transactions.
| Tip |
|---|
It is recommended that Wallet Balance Expiration Runs , are configured to be executed on a daily basis. |
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 performed, a Process Run is logged, and once when the Run is completed, the log information will be is available in the respective SECTIONsection.
The user has the option to delete the specific run as long as it is not yet executed (still in 'Draft' state).
For a Definition to be submitted it needs to must have an 'Effective' Life Cycle State. The Life Cycle State can be changed between 'Effective' and 'Not Effective' using the dedicated action.
- Navigate to Wallet Balance Expiration Run Definitions and explore existing records entries via the Summary page.
Click on the link (name Name or numberNumber) of the record entry of your interest to access the Data Entry page and see more detail, or submit the Definition.
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 Wallet Balance Expiration RunRuns, including each Action's related validations, restrictions , and a description of its system process. and additional information. View the Attributes Table for a comprehensive description of the Wallet Balance Expiration Run fields.
Validations & Restrictions
| Action | Validations | Restrictions | Additional Information |
|---|
| Create | - Mandatory Fields must be defined.
- Name, and alternative code must beuniqueNotApplicableAlternative Code must be unique.
| | |
|---|
| Edit | - Mandatory Fields must be defined.
- Name and alternative code must beuniqueAlternative Code must be unique.
| | - If there is at least one scheduled Run using the same Definition, then a new Run Definition instance is created. The The new Definition will have the same values and Unified Code as the first one, an augmented version number and all the modified information.
|
|---|
| Delete | | - Run Definitions cannot be deleted if there exists at least one scheduled or completed run Run for that Definition.
| |
|---|
Attributes
An * indicates a field is mandatory mandatory.
| |
|---|
| Main Information |
|---|
| Name * | The name of the Wallet Balance Expiration Run Definition. |
|---|
| Alternative code Code* | The alternative code of the Wallet the Wallet Balance Expiration Run Definition. Unless otherwise specified, the Alternative Codes for new entries default to the Name initials in capital letters. |
|---|
| Description | A description of the Wallet the Wallet Balance Expiration Run Definition. |
|---|
| Life Cycle State * | The Life Cycle State of the Wallet Balance Expiration Run Definition which can be:- 'Effective'
- 'Not effective'
|
|---|
| Unified Code | An auto-generated code which is used to group the various instances of the Wallet Balance Expiration Run Definition. |
|---|
| Version | An auto-generated number which is used to specify the version of each Run Definition. If the version number is already in use used by a Run, a new Run Definition Version is created each time when the Definition is edited. "The VIEW PREVIOUS VERSIONS" link allows you the user to search and view any previous versions of the Definition. |
|---|
| Scheduled Date | A Read-only field which is available once a Run is scheduled and designates the latest date that the Run is scheduled to be executed or has been executed. |
|---|
Logging Method | Status |
|---|
| colour | Blue |
|---|
| title | Available from CRM.COM R12.0.0 |
|---|
|
| Defines the method to be used for logging process run's results. Two options are available: | Criteria
It defines - Log Processed Successfully and Processed with Errors: If selected, both entities successfully processed and failed ones will be logged in the Process Run Log.
- Log Only Processed with Errors: If selected then only entities which failed to be processed will be logged in the Process Run Log.
|
|---|
Criteria
Defines the criteria that will be used to identify the Wallet Allotments that will be expired. |
|---|
| Wallet Allotments expired Expired X days agoDays Ago * | Determines the Wallet Allotment Expiration Date in relation to the date of execution, measured in days. | Note |
|---|
The process will retrieve Wallet Allotments having an Expiration Date which is equal to or before the execution date minus the specified number of days. By default this is set to 0, meaning that so the process will retrieve Wallet Allotments having an Expiration Date which is equal to or before the date of execution. |
|
|---|
| Process Runs |
|---|
| Process Runs | Displays the Runs that were executed for this Definition. Each Run includes the Bills that were processed. In case of an error, the error code and description are displayed. |
|---|
Scheduling Settings
Determines when the Definition will be executed after being submitted. |
|---|
| Settings* | Method - The following options are available:
- Run Now
- Run on On Specific Date / Time
- Run Repeatedly
- Advanced Scheduling
Check out Refer to Scheduler Task - Global to find out how you can configure themSettings can be configured. |
|---|
| Log Information |
|---|
| Log Details | The standard set of Log Details information available in all entities . |
|---|