[From Wrike] Exciting Updates to Wrike's Automation Engine: Conditions ๐ฅ
Hi Community!
ย
We know that many of you have been waiting for this, so today we are very excited to share the latest update to Wrike's Automation Engine: Conditions ๐ฅ
ย
Thank you to everyone who has been providing us with your feedback on Wrike's Automation, it was crucial for developing this new release.ย
ย
What Are Conditions?
ย
Conditions are a new capability of Wrike's Automation Engine that specifies criteria that the triggered item needs to meet in order for your rule to be executed. The available automation conditioning logic is the same as the task and project filters that you see in your workspace, with options like Status, Assignee, Importance, custom fields, and others.
ย
When a trigger occurs, the condition checks if additional criteria are true before executing the rule. If all criteria are met your automation rule will be applied ๐ค
ย
How to Introduce Conditions to Your Automation Rules?
ย
An Account Admin can set up and edit automation rules from the Automation tab in the Settings section. Now, after selecting a trigger, you will be able to add one or more conditions. Multiple different selected conditions will be connected by an "AND" relationship: if you select more than one condition, all of them need to be true for the rule to apply. There is no limit on the number of conditions you can add to a rule.
ย
ย
Please check out our Help Center for additional information on conditions.
ย
We hope you are excited about this release (we certainly are ๐)! Send us your feedback or questions in the comments below ๐
ย
Very excited about this - have some teams in our company where this will be extremely useful. Doing testing today to make sure it works with our conditions to hopefully be able to implement it within the week!!
Looking forward to test this outย ๐
Fantastic. That extends the usage of automation very much. Just started testing and first experience is very good.
Great news! Automation will be even better! I passed on to the other admins!
How exciting! ๐
Hi everyone, thank you so much for the positive feedback here!ย
Cannot wait to test this out!!
This is great! I implemented one this morning. Next, I would love to see the ability to add an exception to a rule.ย
Since custom field value sets from request forms cannot be applied to subtasks, It would be useful to have the ability to look into parent task values to trigger subtasks automation.ย
For example, if 'Parent task CF = X' AND 'subtask = assign to Y' > 'reassign subtask to Z'
YESSS!!!
Thank you all for the feedback, I'm passing it on to the team๐๐ปโโ๏ธ
Excited to test out this new capability!ย
ย
Amazing. THANK YOU! This has been such a weird thing to work around.ย
Next up - conditions within approvals so just one person can move along a process... please.ย
Hi, Robyn Jackson and Elizabeth Bayer thank you both for the feedback!ย
Thanks for the update.
This is so good - thank you :)
Thank you folks ๐ค
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Is it anywhere on the roadmap to add an OR functionality here?ย It seems like adding the basic logical operators (AND/OR/XOR) to different wrike areas would be an easy add that would SIGNIFICANTLY improve the usability of these functions.
Hey Connor Redalen, thanks for reaching out!ย
I'd recommend supporting this Product Feedback thread with a similar suggestion ๐
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover