LogiSense's eventing system is an event-driven framework for creating and managing business processes and system integrations. The eventing system and queues use a publish and subscribe model. Many times an action in the billing system is the trigger for a sequence of business processes. The eventing system publishes registered events (create, update, and delete events for platform objects) to a queue (or queues) configured for the event. Those queues are in turn subscribed to and when an event is added, the subscriber will process the event. This processing could be notifying a person or external system of the changes, performing a custom calculation, or sending to another queue for further processing.
There are many different events that can be subscribed to that deal with different billing lifecyle events such as account creating, bill run execution and many more. Click here for the full list of events.
Parameters are name value pairs that provide additional information about the event. Parameters are contextual and dependent on the underlying event object. For example, on a service state transition notification it is possible to provide the corresponding service name as a token. However on a bill run it is not possible to provide a service name as there are multiple accounts and services that can be associated with a bill run.
Parameters can be extended to include data sources and their values to the callout. Data source extensions to parameters are dependent on a contextual relationship between the event object and the data source.