Setting notification schedule based on a Workflow trigger

Note: To use a workflow trigger for a space, you must first configure the workflow trigger in Orchestration. See Workflow Triggers and Configuring workflow triggers in Orchestration for more information.

You can set a notification schedule based on a workflow trigger created in Orchestration. If the conditions of the configured workflow trigger are met, the notification you set the notification schedule to is triggered and sent.

When a notification is run, it uses the trigger's workflow's status of the last time the workflow was run. If the condition of the trigger's workflow was not met in the last run, no notification is sent.

Note: Notifications can set their schedule based on a workflow trigger for only the triggers configured for that subscribed space. For example, if you subscribe space A to a workflow trigger, that workflow trigger is available for notifications in space A. If you attempt to set a schedule for a notification in space B based on that same workflow trigger, it will not be available.

Select Notifications from Space Management or click the Notifications icon in Dashboards to navigate to the Notification Center.
Click + Create New Notification to create a new notification.
Complete the New Notification form by specifying and setting the details of the notification.
Enable the Set schedule based on Workflow trigger property.
When you enable this setting, the Repeats fields are automatically used for scheduling based on the trigger.

Repeats

Select the frequency to check for the condition. You can select When data loads, Hourly, Daily, Weekly, or Monthly.

Additional frequency details are displayed based on what you select for Repeats.

If you select Hourly:

Every

The hourly frequency.

If you select Weekly:

Every

The number of week frequency. For example, if you specify 3, the schedule will run every three weeks.

On

Set the weekly cadence to schedule the notification. You select a day of the week or multiple days of the week for your weekly cadence.

If you select Monthly:

On The

The day of the month to use.

At

Specify the time and time zone for when to schedule the check and then send the report.

Starts On/Ends On

A start and/or end date. These fields are empty by default. You can specify both a start and end date or just one date. If you select a weekly cadence, you must specify a start date. If there is a start date specified but no end date, Birst checks for the trigger from the start date until the user manually changes the schedule or disables the notification. If there is an end date by no start date, Birst runs on the cadence you specified until the end date is met.
Note: You are restricted from setting the start date as today's date. It must be tomorrow's date or later.
Click Select trigger label in the Report driven trigger field to select the trigger for the notification. Only workflow triggers that have been configured for this space are listed.
Complete the rest of the Notifications form.
Click Save.
The workflow trigger is activated when the last step of the workflow is completed and only the workflow’s most recent status is used. If the condition of the trigger's workflow was not met in the last run, no notification is sent. If partial steps are successful, the status updates to success, and the notification is executed.
When executing a workflow with an associated trigger, more than one email is sent if the last step of the workflow is completed:
- An email confirming the workflow's successful completion
- A report notification email
Note: If multiple notifications are linked to the same trigger, all will be executed.
If the final step of the workflow fails, a failure email is sent with a note saying: "The workflow encountered an issue and failed. Any notifications linked to its trigger will not be sent."

Caution:
There is a known issue that occurs when you set a schedule based on a workflow trigger, run the workflow to trigger a notification, and then remove the workflow trigger schedule from the notification. If you disable the schedule based on the workflow after the workflow was already run, future notifications are not get triggered by the new schedule. This will be fixed in a future release.