Metadata triggers without folder specification
--I want Box Relay to be able to kick workstreams off in sub-folders that don't exist yet. We have a general "Accounts" folder, and I want my metadata tag triggers to affect sub folders in that parent folder. However, the metadata trigger requires me to specify which specific folder to trigger the Relay within. I suggest one of two things:
1. Remove the need for folder specification. If I have a metadata trigger, do I really need to specify the folder in which the content lives? Relay should scan for that metadata tag, wherever it occurs.
2. Allow for Relay to scan in parent and sub-folders. While the specific account folders do not exist yet, I still do have the "Accounts" parent folder--I should be able to use this folder location in the metadata trigger so that Relay will scan that folder AND any sub-folder within.
Either of these enhancements would greatly improve our account certification process. We regularly add new accounts, and I don't want to have to create new Relays every time we add one.
Anonymous
shared this idea
Thanks for your feedback. We’re exploring introducing new cascading triggers or system-wide workflows which would address this issue.