There are times when under Dispatch'r or Observer, the limit on only one rule firing per change limits the power of FreshDesk's automation potential.
We have a number of scenarios where we need to automate a set of actions against a ticket and where some may even have a dependency on the execution of a prior rule. With the current "once and out" approach, we are pretty limited to what we can do.
I know that we can build rules that handle more tasks, but there are times when we could have the need to automate conditions that can exist in the same rule.
Therefore, I submit the following suggestions for improvements to the automation rules in FreshDesk:
- Allow a rule to execute another rule, and/or
- Allow rule execution to pass through all active rules that are under Dispatch'r or Observer, based on the order provided and execute any rule that matches the conditions.
