1. Message Scenario Configuration Guide
  2. Message Scenario Notification Workflow

Message Scenario Notification Workflow

Messages are generated and sent based on pre-defined conditions.

This image shows the notification workflow, which is described below.

  1. The system provides a set of APIs to receive data from different sources, agents and external systems like customer relationship management, inventory management, and human capital management systems.

  2. If a certain condition is met when data is received, the relevant launch condition is activated.

  3. The launch condition invokes the start of one or more steps in the message engine.

  4. A message is generated and saved in the message queue at the end of every message scenario step.

  5. Each message is processed until it reaches its final status.

    Note: The following message statuses are possible:

    • New: Set by the message engine for successfully created messages that have not yet been sent to the message agent, which is the application that processes messages.

    • Falsemethod: Set by the message engine for messages that cannot be created due to an invalid configuration or missing data.

    • Obsolete: Set by the message engine for messages that are invalidated by an operation within the application, such as delete, move, or suspend, or by the creation of another message.

    • Sending: Set by the message engine for messages that are sent to and initially processed by the message agent.

    • Sent: Returned by the message agent when receipt of the message cannot be confirmed, for example, when a message was received by a voice mail system.

    • Delivered: Returned by the message agent if the message was delivered successfully and the final recipient has received the message. This status is not typically used for e-mail since verifying that the message was read is not possible.

    • Failed: Returned by the message agent for messages that cannot be delivered.

  6. If a blocking condition is met, the message is either not generated or generated but not sent. The message is then set to its final status.

  7. There may be inner steps included in the message scenario. An inner step is invoked in accordance with a final status of the message received as the result of the previous step processing.

  8. When all pre-defined conditions have been met, the message is sent to the corresponding message agent via the Outbound API.

  9. The scenario is complete when there are no more steps to be executed.

The following figure shows a possible scenario flow.

The image shows three possible message scenarios: A, B and C.