SmartIQ Workflow allows configuring Escalation actions to be triggered based on configurable conditions.

Adding an Escalation

1. Open the Workflow canvas.
2. Drag and drop the Escalation button from the left panel into the appropriate state or go to the Escalations tab of the state and click Add.

Escalation Properties

These are common properties for all available escalations:

Escalation Name

Allows customizing the name of this escalation action.

Initiate

• Interval – Allows to define when this Escalation should be triggered, these are the options available:
  • In Minutes
    • Min(s) after transition
  • In Hours
    • Hour(s) after transition
  • In Days
    • Day(s) after transition
    • Weekdays Only
  • Day/Time
    • Question (question reference to resolve date and time.)
    • Date: The recommended format should be standard date format, yyyy-MM-dd hh:mm:ss.s
    • Time: Should be in local time because time will get converted in the system to UTC
• Retry On Failure – Allows the user to specify the number of retries and wait between retries. The escalation will be attempted again on failure the next time the scheduler runs. This may mean that it may not run at the exact delay specified, however it will never be shorter than that time period.

It is also possible to define recurring Escalations, selecting Recurring option. Here a brief description of available options:

Recurrence

Recurrence Pattern

• Hourly
• Daily
• Weekly
• Monthly

Range of Recurrence

• Occurrences
• After Days
• On Date
• No End

Post to Webhook

A Webhook is a simple HTTP publish and subscription model for passing information between services. With the Webhook action, you can call your own HTTP endpoint when a form is submitted and optionally include form answers. This means all your connector logic can remain in an external service that can be updated and load-balanced separately.

The service call is made as a POST and the body of the request contains the JSON payload. Service response codes determine if the action is considered to have failed or completed. This action does not deal with the generated documents.

Push Notification

Ability to send Push Notifications to the Offline App which has been registered to a user.

📘

Note

If there is no user or group guid specified, the notification will look at the current workflow state (if it is within a workflow) and send a push notification to the current user or group.

Reassignment

Allows reassigning current State to another User or Group.

Send Email

Sends an Email similarly to the Email Action with the difference that can be configured to be recurring using Escalation parameters.

Send to REST Service

Makes a request to a REST API every time the Escalation is triggered. For more information, refer to the Send to REST Service Action.

Submit Task

❗️

Required configuration in Manage > Connector Settings

This escalation has a required setting in Manage which sets the designated user to progress the workflow. If this is not set, the escalation will fail. See Connector Settings below for details.

A submit step escalation will progress a workflow from it's current state to a destination state. The escalation has the following input types:

🚧

Notes

• Any conditions required to trigger the Submit Task action must be complete before Workflow Assignment occurs during the creation of the Escalation. This means that an actions that need to input into those conditions must be run no later than "Run After Document Generation". "Run After Finish" will be too late.
• Avoid using Current User transitions when also using the Submit Task escalation. The Submit Task escalation submits the task as the configured user (from Connector Settings), so a "Current User" workflow transition will result in a task assigned to the Connector Settings service user.

Connector Settings

Terminate Workflow

Terminates workflow when escalation Initiate condition is met. Note that this escalation can't be recurring as it will cancel the workflow once is initiated.