Versions Compared

Key

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

 

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

N. B. These hookpoints may not be available for all core version and in all customer 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)Context objectsInvocationNotes
SIGNUP 

SUBSCRIPTION

USERS
Sign flow for regular signup, started after registering the users information in self-care or customer care 
SIGNUP_NP NPFLOWSign 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 

SUBSCRIPTION

TELESERVICE

NPFLOW

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 

SUBSCRIPTION

TELESERVICE

NPFLOW
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

...

Hookpoint keyDynamic key(s)Context objectsInvocationNotes
SUB_CAN_TERMINATE SUBSCRIPTION

Hookpoint result values:

RESULT = "SUCCESS" - the the subscription can terminate

Invoked by customer care and other workflows to resolve if a subscription can be terminated. 
TERMINATE_SUBSCRIPTION 

SUBSCRIPTION

SUBSCRIPTION_TERMINATION

Handling the scheduled termination of subscriptions. Can be invoked by all areas of the system. 
SUB_REACTIVATE 

SUBSCRIPTION

Hookpoint result values:

RESULT = "SUCCESS" - the the subscription can be reactivated

Invoked by customer care and other workflows to resolve if a subscription can be re-activated. 
SUBSCRIPTION.TERMINATION.CHARGE_ITEM 

SUBSCRIPTION

RESULT = The charge item of the termination fee
Invoked when terminating the subscription 

...

Hookpoint keyDynamic key(s)Context objectsInvocationNotes
PRODUCT_OPTION_CAN_MODIFY<OPTION_KEY> = The key value of the product option

OPTION (the product option)

OPTION_LOGIC (the service belonging to the option)

Invoked 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 option

OPTION

SUBSCRIPTION

ACTION = "SUBSCRIBE"

Invoked 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 option

OPTION

SUBSCRIPTION

ACTION = "UNSUBSCRIBE"

Invoked when the specific product option with the OPTION_KEY is unsubscribed from any part of the system 
PRODUCT_OPTION_SUBSCRIBE 

OPTION

SUBSCRIPTION

ACTION = "SUBSCRIBE"

Invoked any product option is subscribed to from any part of the system 
PRODUCT_OPTION_UNSUBSCRIBE 

OPTION

SUBSCRIPTION

ACTION = "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 option

NEW_OPTION

OLD_OPTION

SUBSCRIPTION

Invoked 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 

...

Hookpoint keyDynamic key(s)Context objectsInvocationNotes
 <ALERT_HOOKPOINT>

<ALERT_HOOKPOINT>

e.g. "ALERT_HOOKPOINT = myAlertWorkflowHookpointKey"

"SUBSCRIPTION"
"SUBSCRIPTION_BUNDLE"
"BORDER" (which is the value of the percentage that triggered the workflow, in the form of java type Long)
"INVOKED_BEFORE_FOR_THIS_CDR" (the type is boolean)

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)

CAMPAIGN.ASSIGN.IS_ALLOWED<CAMPAIGN_KEY>INPUT (SubscriptionCampaignActivationInputBean)  
CAMPAIGN.ASSIGN.GENERATE_OBJECTS<CAMPAIGN_KEY>

INPUT (SubscriptionCampaignActivationInputBean)


Result:

Output

(SubscriptionCampaignActivationOutput)

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
CAMPAIGN.ASSIGN.PERSIST_OBJECTS<CAMPAIGN_KEY>

SUBSCRIPTION_CAMPAIGN

 

Invoked when an assigned campaign is assign and saved 
CAMPAIGN.ACTIVATE.GENERATE_OBJECTS<CAMPAIGN_KEY>

INPUT (SubscriptionCampaignActivationInputBean)


Result:

Output

(SubscriptionCampaignActivationOutput)

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
CAMPAIGN.ACTIVATE.PERSIST_OBJECTS<CAMPAIGN_KEY>

SUBSCRIPTION_CAMPAIGN

 

Invoked when an assigned campaign is activated and saved 

 

Fees

Hookpoint keyDynamic key(s)Context objectsInvocationNotes
     

...