trigger broadcast functionality via procedure launcer

Stefan Rappen

Our customer has the broadcast license and is currently sending content critical time-controlled status reports. We would liked to trigger this automatically at the end of the data preparation with the Procedure Launcher and not (necessarily) delayed (since the data preparation has to be finished) by the broadcast schedule. At the moment reports will be send as a "blank screen" if the data load is not finished or containing errors.

Stefan Rappen

will there be anything implemented in the future? The status open for voting is already 18 month old..

Product Management Team

Thank you for sharing your idea, Stefan. We appreciate the time and effort you put into crafting your suggestion. Great news, this feature is available with the Broadcast Procedure step.

Here is the link to the manual: https://www.boardmanual.com/2021/summer/data-modeling/2_Database_design_functions/8_Procedures/The_Procedure_Designer/procedure-actions/broadcasting-actions.htm?rhhlterm=broadcasting%20broadcast%20procedure%20steps%20step&rhsearch=broadcast%20procedure%20step

Apologies for the delay in our response here. Thank you for being patient and following up!

Product Management Team

Hello Stefan,

I would like to clarify our previous response.

At the moment the Broadcasting functionality cannot be scheduled via procedure as you mentioned. It can be added to a procedure as a step for interactive use, but it will not be executed if said procedure is then scheduled.

What is feasible is to use the Broadcasting section to schedule a Broadcast action after the procedure is completed. In the Broadcast layout you can enter a condition/filter block so that if the previous procedure is not completed or failed for some reason, the Broadcast sends a notification to the admin users instead of blank reports to end-users.

In the longer term we plan to improve this functionality to allow also synchronous notifications also in such use cases, this item is accepted and in our backlog of improvements.

Thanks again for your input.