Hiiiii!
Wondering if anyone can help me find a workaround for the following rule? I’ve created a multi-select field with to be added promotional subtasks for events. The idea is that the team member uses the field as a ‘button’ to add all (different sets of) subtasks related to a promotional task. See screenshot for how I’ve built the rule. The way it is now, only implements the action/subtasks of the first selection in the field due to the ‘otherwise if’ statement. It stops reading after it’s succeeded to fill one of the ‘if’s.
The current workaround is to make a selection, wait for the rule to load, clear selection and then select the following action. It works, but it’s not the best solution I’d say.
Does anyone know of a smarter build to have the rule read through the full selection in the field and add different sets of subtasks related to each selection seperately?
I’ve thought of either:
- building separate rules for each selection - much more workload heavy and messy in the rule builder so ideally not.
- Seperate fields for each promotional activity - will probably also require separate rules so adding double double the workload
Some more context:
This rule lives in a project where we track all events this team works on as tasks (we have hundreds of them each year). Within the task the activity per event is listed in subtasks that are also multihomed in projects such as our social media calendar, website planning, creative requests board, misc. tasks etc.
