Subscription forms

Subscriptions allow users to be notified about events even if they were not initially targeted by the notification message sent by a workflow. For example, a restaurant manager could subscribe to all equipment failure alerts, even though these alerts may only be sent to the on-duty repair personnel assigned to handle them.

To allow people to subscribe to events, you must create a subscription form for each workflow that you want to have subscriptions. Subscription forms define who can subscribe to events, which properties they can subscribe to, and whether they can respond to notifications. You can also use these forms to set message content for the notifications sent to subscribers, and how to handle any responses.

You can create a subscription form that will trigger a subscription for all events related to a workflow, or just for events related to a single messaging form within a plan.

You can only create subscriptions based off messaging forms, not flow trigger forms.

Once you have designed and configured a subscription form, you can create event feeds based on the form that define which properties and values should trigger a notification, and which devices should receive the message. Users can then subscribe to the events that most relate to them, or their supervisors can assign subscriptions on their behalf.