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 14 Next »

 

Some of the hookpoint used most commonly are listed here, along with the the context provided to the workflow.

N. B. These hook points may not be available in all installation. 

 

For a details regarding the available context objects and return values please refer to the Workflow Admin tool under the Hookpoint Explorer.

Sign-Up

Hookpoint keyDynamic key(s)InvocationNotes
SIGNUP Sign flow for regular signup, started after registering the users information in self-care or customer care 
SIGNUP_NP Sign flow for Number Porting sign up, started after registering the users information in self-care or customer careOnly available for specific countries
TELESERVICE_MOBILE_SIGNUP Sign flow for regular sign up, started after registering the users information in self-care or customer care.Only available for services of type TELE
TELESERVICE_MOBILE_SIGNUP_NP Sign flow for Number Porting sign up, started after registering the users information in self-care or customer care. Only available for services of type TELE.Only available for services of type TELE

Termination

Hookpoint keyDynamic key(s)InvocationNotes
SUB_CAN_TERMINATE Invoked by customer care and other workflows to resolve if a subscription can be terminated. 
TERMINATE_SUBSCRIPTION Handling the scheduled termination of subscriptions. Can be invoked by all areas of the system. 
SUB_REACTIVATE Invoked by customer care and other workflows to resolve if a subscription can be re-activated. 
SUBSCRIPTION.TERMINATION.CHARGE_ITEM Invoked when terminating the subscription 
GET_DEFAULT_TERMINATION_DATE Invoked when the termination date need to be calculated in Customer Care 

 

Product Options

Hookpoint keyDynamic key(s)InvocationNotes
PRODUCT_OPTION_CAN_MODIFY<OPTION_KEY> = The key value of the product optionInvoked from customer care when determining if a product option and be subscribed or unsubscribed. 
PRODUCT_OPTION_SUBSCRIBE<OPTION_KEY> = The key value of the product optionInvoked when the specific product option with the OPTION_KEY is subscribed from any part of the system 
PRODUCT_OPTION_UNSUBSCRIBE<OPTION_KEY> = The key value of the product optionInvoked when the specific product option with the OPTION_KEY is unsubscribed from any part of the system 
PRODUCT_OPTION_SUBSCRIBE Invoked any product option is subscribed to from any part of the system 
PRODUCT_OPTION_UNSUBSCRIBE Invoked any product option is unsubscribed to from any part of the system 
PRODUCT_OPTION_SWITCH<OPTION_KEY> = The key value of the new product optionInvoked when changing between product options that are exclusive. I.e. the parent option marked the sub options as exclusice or the option is part of an exclusive group 

Campaigns

Hookpoint keyDynamic key(s)InvocationNotes
<ALERT_HOOKPOINT>

<ALERT_HOOKPOINT>

e.g. "ALERT_HOOKPOINT = myAlertWorkflowHookpointKey"

Invoked when specific configurable alert levels have been crossed. The levels are defined on the PARAMETERS of the bundle configuration and is a comma separated list of numbers (percentages), e.g. "ALERT_LEVEL=25, 50, 75, 100"

The alert hookpoint for bundles is fully configured in the bundle configuration and has no static part.

(see documentation for Campaign and bundle configuration: The RestrictActive Framework)

Not supported by all campaigns types

CAMPAIGN.ASSIGN.IS_ALLOWED<CAMPAIGN_KEY>Invoked when attempting to assign a campaign. The result of the workflow will tell if assigning is allowed or not.Not supported by all campaigns types
CAMPAIGN.ASSIGN.GENERATE_OBJECTS<CAMPAIGN_KEY>Invoked when an campaign is assigned and the activation is not activated yet.

A workflow linked to this hookpoint is intended to generate the objects used by the hookpoint: CAMPAIGN.ASSIGN.PERSIST_OBJECTS

Not supported by all campaigns types

CAMPAIGN.ASSIGN.PERSIST_OBJECTS<CAMPAIGN_KEY>Invoked when an assigned campaign is assign and savedNot supported by all campaigns types
CAMPAIGN.ACTIVATE.IS_ALLOWED<CAMPAIGN_KEY>Invoked when attempting to assign a campaign. The result of the workflow will tell if activation is allowed or not.Not supported by all campaigns types
CAMPAIGN.ACTIVATE.GENERATE_OBJECTS<CAMPAIGN_KEY>Invoked when an assigned campaign is activated and the activation is not saved yet.

A workflow linked to this hookpoint is intended to generate the objects used by the hookpoint: CAMPAIGN.ACTIVATE.PERSIST_OBJECTS

Not supported by all campaigns types

CAMPAIGN.ACTIVATE.PERSIST_OBJECTS<CAMPAIGN_KEY>Invoked when an assigned campaign is activated and savedNot supported by all campaigns types
CAMPAIGNONASSIGN / ONACTIVATE / ONEXPIRE / ONTERMINATEInvoked when a campaign is assigned, activated, expires or terminatedNot supported by all campaigns types

 

Fees

Hookpoint keyDynamic key(s)InvocationNotes
FEE_CALC_NEXT_CHARGE_DATE<SUBSCRIPTION_FEE_CODE>Invoked when the next charge date of a fee is calculated. Usually on the charge date.Not supported by all fee types
FEE.PRIOR<PLAN_ELEMENT_NAME> with the first part ('PRE-', 'POST-', 'ONCE-' or 'SINGLE-') strippedThis hookpoint is invoked when you bill or refund a fee, before it is doneNot supported by all fee types
FEE.AFTER.BILL<PLAN_ELEMENT_NAME> with the first part ('PRE-', 'POST-', 'ONCE-' or 'SINGLE-') strippedInvoked after the fee is billedNot supported by all fee types
FEE.CHARGE_ITEM This hookpoint is invoked when you bill a fee. The hookpoint returns the charge item to be used in the billing process.Not supported by all fee types
FEE.CALCULATE.PRICE<PLAN_ELEMENT_NAME> with the first part ('PRE-', 'POST-', 'ONCE-' or 'SINGLE-') strippedinvoked when you bill a fee. The hookpoint returns the price for billing the given fee with the given context. Not supported by all fee types

Invoices

Hookpoint keyDynamic key(s)InvocationNotes
INVOICE.BEFORE.CLOSE Invoked before the invoice is closed 
    

Dunning

Hookpoint keyDynamic key(s)InvocationNotes
<INVOICE.FLOW.STEP>

The hookpoint is defined on the database table field: INVOICE_FLOW_STEP_DEF_METHOD.META_DATA:

E.g. {"values":{"HOOKPOINT_KEY":"INVOICE.FLOW.REMINDER"}}

Invoked for every defined step on the invoice flow.Part of the Invoice Flow Engine
INVOICE.FLOW.CANCEL<INVOICE_FLOW_CANCEL_STEP_NUMBER>Invoked when an invoice or a billing group is no longer in an invoice flowPart of the Invoice Flow Engine

Simcards

Hookpoint keyDynamic key(s)InvocationNotes
SIMCARD_STOLENBLOCK<PRODUCT_HOOKPOINT_KEY>Invoked when the sim card is blocked in customer care or a via workflow, with the reason stolen 
SIMCARD_HARDBLOCK<PRODUCT_HOOKPOINT_KEY>Invoked when the sim card is blocked in customer care or a via workflow, with the type hard block 
SIMCARD_SOFTBLOCK<PRODUCT_HOOKPOINT_KEY>Invoked when the sim card is blocked in customer care or a via workflow, with the type soft block 
SIMCARD_FRAUDBLOCK<PRODUCT_HOOKPOINT_KEY>Invoked when the sim card is blocked in customer care or a via workflow, with the reason fraud 
SIMCARD_UNBLOCK<PRODUCT_HOOKPOINT_KEY>Invoked when the sim card is unblocked in customer care or a via workflow, after it has been soft blocked 
SIMCARD_REACTIVATE<PRODUCT_HOOKPOINT_KEY>Invoked when the sim card is reactivated in customer care or a via workflow, after it has been hard blocked 

A-Numbers

Hookpoint keyDynamic key(s)InvocationNotes
CHANGE_ANUMBER Invoked when a change a-number request has been issued from any part of the system 

Recharge Tickets

Hookpoint keyDynamic key(s)InvocationNotes
RECHARGE_TICKET.CALCULATE_RECHARGE_AMOUNTDynamic hookpoint key provided by the RechargeTicketType's meta dataInvoked when the recharge ticked is used to perform a top-upNot available in all recharge ticket implementations
RECHARGETICKET.BEFORE.DELETE   

Other

Hookpoint keyDynamic key(s)InvocationNotes
GET_PHONE_NUMBER_FOR_SMS   
GET_LONG_DESCRIPTION_SERVICE_XXXX   
CHANGE_RATEPLAN   
CAN_DELETE_LOCKIN   
CANCEL_NP_FLOW   
CAN_CANCEL_NP_FLOW   
  • No labels