Workflow Monitor
Workflows events are created by processes to initiate configured activities known as actions. Actions include:
- Changing an account
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. type - Applying a service (charge) to a subscription A billing entity that incurs a charge. Examples include a network attached device whose usage you want to measure and charge for, or a monthly software subscription
- Initiating generation of a network In the context of CMP, the infrastructure on which usage of registered customers will be measured – this could be a mobile phone network, broadband network or other non-telecommunications network. command
- Initiating generation of a customer 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. communication
Once a workflow has been created, it remains in a Pending state until it has been processed by this job on the requested date/time.
When a workflow is processed, account type changes and subscription service actions are applied in full immediately. Network commands and communication generation actions involve initiating further downstream processing. Once processed, the status of the workflow is updated to indicate success, error or pending network activity.
This job is automatically triggered when workflow records in a Pending state that are due for processing are detected. These workflows are processed in order of priority.
The Process Event job is responsible for identifying Workflow Events Manually or automatically created task items that drive and record activity within CMP. Sometimes referred to as Diary Events. eligible for processing based on:
- The date and time resolution of the Workflow Event is required.
- The Workflow Event having status of pending auto processing.
The following probes can be run against Workflow Monitor:
| Name | Type | Description | ||
|---|---|---|---|---|
| Workflow Monitor Verification Normal | Alert | Alert probe that returns the number of workflows that have ended up with a processing error today. If the value returned by this query is above the threshold, an alert will be sent to the recipients configured for this probe. | ||
| Workflow Monitor Verification Punctual | Alert | Alert probe that returns the number of workflows that are currently pending processing today. If the value returned by this query is above the threshold, an alert will be sent to the recipients configured for this probe. | ||
Relevant JSON schema A specification for JSON based format for defining the structure of JSON data.:
- Not applicable. This job does not consume any external feed from a third party Of software; a reusable component developed to be either freely distributed or sold by an entity other than the original vendor of the development platform. nor does it produce a feed for a third party; it operates on CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. tables.