CONTEXT
A company using ERP-class software wants to create an automated employee notification system. This system should operate fully automatically, independent of the user, detect alarm conditions, and notify the appropriate recipients.
TASK
Creating a feature that helps the user immediately react to a decline in sales.
EXAMPLE USE OF GRAVITY
For our example, we assume that we must notify users about a drop in sales over the last 7 days, provided that the 7-day sales value is lower than the median for the last 12 months. If the defined condition is met, GRAVITY sends an email notification to the configured recipient.
Processing trigger: scheduled time-based scanning.
TASK
Creating a functionality that enables immediate notification when a customer exceeds their credit limit.
GRAVITY USE CASE – TIME-BASED TRIGGERING
When the condition of exceeding the credit limit is detected, GRAVITY sends an email notification to the configured recipient (or recipients). Processing is triggered by cyclic time-based scanning.
GRAVITY USE CASE – DATABASE NOTIFICATION TRIGGER
The behavior is identical to the above example, but processing is triggered by a database notification instead. The notification is fired when an invoice record is added for the customer.
GRAVITY USE CASE – SMS NOTIFICATION
As in the previous example, but the event information is sent as an SMS to a designated person. This scenario uses the CALL WEB SERVICE operator to invoke an external SMS gateway service.
TASK
Creating a functionality that enables continuous retrieval of information about overdue customer order fulfillment.
GRAVITY USE CASE – EMAIL NOTIFICATION
When the condition (presence of overdue orders) is detected, GRAVITY sends an email message to the configured recipient or recipient group.
Processing trigger: scheduled time-based scanning.
GRAVITY USE CASE – PROVIDING AGGREGATED DATA
When the condition (existence of overdue, not-yet-closed customer orders) is detected, GRAVITY places information about all such cases onto the main data bus and then saves it to a temporary database (session memory cache).
A WEB SERVICE function is additionally configured to expose this temporary database to external systems.
As a result, any external software can retrieve the prepared in-memory data.
Processing trigger: scheduled time-based scanning.
