Linked Events

You can link a series of workflow events to create a sequence of linked workflow events. Linked workflow events can be used to automatically create another workflow event once a workflow event has been resolved.

For example:

  1. Workflow A: Sends moves an accountClosed In the Cloud Monetisation Platform, a billing entity that can be used to manage payments on one or more subscriptions or payments for services. An account can hold details such as payments or invoices. from a nursery account to a business account.
  2. Workflow B: Removes the data capClosed A limit on a subscriber's service. from the account.

An error with Workflow A will prevent Workflow B being created.

Any number of workflow events can be linked as long as every workflow event in the sequence is configured to be raised at the same level of the CMPClosed Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. customerClosed In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement. hierarchy. For example, all workflow events are to be raised at account level.

The first workflow event in a sequence is referred to as the initiating event. All linked workflow events are linked to the initiating event only. You cannot link another initiating event to the first initiating event. For example:

  • Allowed: Workflow A is the initiating event. Workflow B and C are linked to A.
  • Not allowed: Workflow A is the initiating event. Workflow B is linked to A. Workflow C is linked to B.

When you define linked events, you give each workflow event a sequence number, which determines the order in which the linked workflow events will be created. When the first workflow event is resolved, the second will be created. When the second is resolved, the third will be created, and so on. Typically the sequence numbers 10, 20, 30 are used so that changes can be made in the future by using the numbers in between. For example:

  1. Workflow A is the initiating event. Workflow B has sequence number 10 and will be created when Workflow A is resolved.
  2. Workflow C has sequence number 20 and will be created when Workflow B is resolved.

Linked workflow event functionality is independent of other workflow event functionality, making it entirely optional. Linked event functionality runs as a background process. It identifies any workflow events that have linked workflow events predefined where one or more of predefined linked workflow events have not been created. It then checks if the preceding workflow event in the sequence has been set to Resolved. If it has, the next workflow event in the sequence is created. Linked workflow events are created in exactly the same way as workflow events created manually. Standard workflow functionality is then responsible for processing the workflow event.