Forum Discussion
Search functionality for unassigned trigger.
At present, we are required to manually inspect each page and layer for any unassigned triggers, which is a labor-intensive process and prone to oversight. This method is not only time-consuming but also increases the likelihood that some unassigned triggers may go unnoticed. There are instances when triggers remain unassigned due to various reasons, such as moving or reusing slides, or other operational factors. This can lead to significant functionality errors, which could impact the overall performance. To streamline this process and reduce the risk of errors, it would be highly advantageous to implement a search functionality specifically designed to identify and highlight unassigned triggers.
2 Replies
Hi SunilGupta-9bd2,
Thanks for sharing this idea!
A search function to quickly identify unassigned triggers would certainly help streamline quality checks and reduce errors, so I’ve added your request to our feature list for the team to review.
We’ll keep tracking interest in this and let you know if it becomes available in a future Storyline update.
This was first suggested literally 12 years ago. (You can find the thread in the Discuss forum, apparently the original Suggest thread has been deleted.)
It's weird it hasn't happened yet, honestly. It feels like such an obvious feature. In fact, in every development environment I've used (as a software dev) the compiler/intepreter would warn me and refuse to proceed if I had a variable named but not given a value, a function called that didn't exist, etc. Basic stuff.
As an interface designer, I have always said, "Nothing should ever fail silently."
