The Event-Based Trigger component creates in the decision tree a main branch that is activated each time an allowance event is sent to allowances through an Allowance Event Sender Operator. The Event-Based Trigger component creates in the decision tree a main branch that is activated each time an allowance event is sent to allowances through an Allowance Event Sender Operator.
The configuration of an Event-Based Trigger component requires the selection of an Allowance Event Class that specifies the type of the allowance event (for more information on the Allowance Event Class, refer to the primary help of Core Tool).
The rules are the following:
The Allowance Logic can contain several Event-Based Triggers but only one per Allowance Event Class.
You must at least assign an Allowance Event Class to an Event-Based Trigger.
If an allowance event class is assigned to an Event-Based Trigger, the user properties of this Allowance Event Class are available only in the branch that uses this Event-Based Trigger.
When you insert an Event-Based Trigger in the Allowance Logic, some properties (*) are available in the Event-Based Trigger branch.
(*) These properties are the following:
Event Date: The date of the allowance event
Validity Start Date: The start date of the validity period of the allowance
Validity End Date: The end date of the validity period of the allowance
Allowance Unique Identifier: The unique identifier of the allowance
Currency Code: The currency code of the allowance
ISO Currency Code: The currency code of the allowance in the ISO format
You use the Event-Based Trigger component to interact with allowances created in several decision trees: Price plan, refill logic, and allowance logic.
As an operator, you create an offer for your customers so that they can add recharges to a base plan. Each time the customer buys a recharge, the new recharge (or the new allowance) is created, and the current allowance is extended to the expiration date of the new one. Furthermore, you want to declare the revenues related to allowances by reporting the exact revenue at the creation, the usage, and the expiration of the allowances. You can then create in the allowance logic of your allowance plan:
An Event-Based Trigger branch to report the revenues related to the usage of allowances
A One-Shot Trigger branch to report the revenues related to the creation of allowances
A One-Shot Trigger branch to report the revenues related to the expiration of allowances
Each time the allowance is used with an Allowance Event Sender Operator component in the price plan of a charge, the Event-Based Trigger component computes the properties to report or updates the allowance event. The Event-Based Trigger branch needs a Property Introducer Operator to define the reason of revenue recognition. This Event-Based Trigger branch enables the generation of a charged item.
|
Note: The Event-Based Trigger component needs an Allowance Event Class with related properties describing the event. In this example, the Allowance Event Class can be named “Carryover” and contains the validity period (start date and end date) of the new allowance. The name of the Allowance Event Class determines the type of the event. |
As an operator, you create an offer for your customers so that they can add recharges to a base plan. Each time the customer buys a recharge, the new recharge (or the new allowance) is created, and the current allowance is extended to the expiration date of the new one. This offer contains an allowance plan, and its allowance logic includes an Event-Based Trigger component whose branch checks whether the validity period of the allowance can be extended or not. This branch contains a Numbers Comparator component and an Allowance Validity Period Updater Operator component. The Numbers Comparator checks that:
The allowance start date is before the start date of the new allowance
The allowance end date is after the start date of the new allowance
The allowance end date is before the end date of the new allowance
If the previous rules are true, the Allowance Validity Period Updater Operator can extend the validity period of the allowance.
Name: Type the name of the component (mandatory). Choose an appropriate name because it is reused as the label of pricing transactions.
Description: Allows you to type the description of the component (optional).
Allowance Event Class: Provides the list of allowance event classes. Select an allowance event class. If necessary, click 
to open the selected allowance event class.