Events and Actions
Apps -> <App> -> Events & actions
Last updated
Apps -> <App> -> Events & actions
Last updated
In Appverse, the Events and Actions framework enables automated workflows by defining specific actions triggered by events under predefined conditions. This feature helps to execute processes automatically when certain criteria are met.
In Appverse, events and actions are made up of the following components
Action: Specifies what needs to be done when the event occurs. This could be updating a record, creating a record in another form, sending a notification, or executing a custom script.
Event: Defines what triggers the action. An event could be a form submission, record update, or a user-initiated action. User-initiated events are displayed to the users and has to be manually triggered by the user.
Conditions: Determines when the event should trigger the action. Conditions help filter events so that actions are only executed when specific criteria are met, preventing unnecessary operations. Read more about "Conditions" in Appverse.
Notification (SMS/Email/InApp): Allows sending alerts via SMS or email or InApp to notify relevant users when an event is successfully executed or if it fails. Read more about "Notifications" in Appverse.
Event - An order is submitted.
Action - Put the order on Hold.
Condition - Trigger only if the customer has the "Put Order on Hold" flag set to "Yes."
Notify - Notify the salesperson assigned to the customer or the customer via email.
In Appverse, configured actions can be executed in either synchronous or asynchronous mode, depending on the nature of the task and system requirements. Currently for optimal performance, the execution mode is controlled by a parameter called "Strategy". Strategy can either be "Wait" or "Emit". In future, we may provide more control over the sequence of execution of various configured events and actions.
If the strategy is set to "Wait", all the actions configured with strategy as "Emit" will wait for the "Wait" actions to get completed first. This means that actions with "Wait" and "Emit" strategy will execute sequentially or synchronously i.e. one after another.
However, all actions of "Wait" type will execute asynchronously. Similarly, all events of "Emit" type will execute asynchronously.
"Wait" Strategy
If a form needs to wait for the output of a configured Event and Action before proceeding, the strategy must be set to "Wait." This ensures that the form does not move forward until the action is fully executed and its output is received.
By enabling the "Wait" setting, the system holds control within the form, preventing further user actions or submissions until the necessary processing is completed. This is useful for scenarios where immediate validation, calculations, or external system responses are required before proceeding.
Note: This works only for online forms.
Scenario: A form submits a loan application that requires an immediate credit score check before approval.
Configuration: The Event and Action for fetching the credit score is set to "Wait."
Outcome: The form will remain in a processing state until the credit score is retrieved, ensuring accurate decision-making before proceeding.
Using the Wait setting in Appverse ensures that dependent processes are completed before users can continue.
