Customfields in Automation.

We have started to move more and more of our processes to Wrike.

But we keep running into the same issue over and over.

We would really like to assign based on a customfield.

Like as an example:

We select various colleagues from various departments for a Approval process.

Now we have set up a customfield for each department. And for every department we can select a number of colleagues. Currently we have to do a extra rule for each colleague and status of the task.

It would reduce our  amount automations significantly if we were able to just say:
"[Assign -> Customfield(2)]" instead of :
Rule 1:
if custom field is [Assignee A]
then assign Assigne A

Rule 2:
if custom field is [Assignee B]
then assign Assigne B
....

The current work around is very intensive to set up and a lot of effort to maintain it...

Another big pain point for us is that we do not have the option for a "NOT" in the logic out of the box or an "else". We know that there are workarounds using the API but we would prefer to do it within the system itself.

Sometimes its easier to say "IF NOT [A]" then ...
instead of "IF [B,C,D or E] then....

 

Is there any plan to bring this functionallity into Wrike?

Best Regards,
Florian

Upvote 7
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
7 comments

I also have a need for this. Our use case is that we populate a custom field with a user name when a task is assigned so that if the task comes back to a department (as a rework or the like), it will automatically be assigned back to that same user. Right now we have a lot of individual rules inputting individual user names into the custom field.

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi folks, I've already sent your suggestion to the responsible team 👍 Thanks for posting! 

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

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Our org would also benefit from this. I will work to have additional up votes entered.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Thank you for supporting this suggestion, Milissa Epps 🙂 I'll be sure to circle back to you with any updates in the future 👍

Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Rohan V Wrike Team member Become a Wrike expert with Wrike Discover

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

We recently overhauled our Wrike setup, and managed to create Table views which include dedicated People type custom fields for those responsible for the steps in our print production workflow. We're really happy with the Table overview of who is responsible for e.g. layout design or prepress in which project at a glance, without having to dig into project subtasks. We have several hundred projects annually, and dozens of external designers and prepress operators who work on them.
Recently, we started to set up Wrike Automation notifications about handovers from e.g. our internal editorial process to external design to external prepress to internal production management and internal digital asset management. 
Turns out Wrike Automation doesn't support @-mentioning recipients, who happen to exist in People type custom fields.
Existing Wrike Automation "Add comment or mention" options are limited and not usable for our external designers and prepress users:

  • Followers - we don't add externals as followers.
  • Owners - each project is owned by one of our internal editors.
  • Author - all our projects are created by API integrations or request forms.
  • Approvers - we don't add externals as approvers.
  • Specific users - we have too many external designers and prepress users to even consider creating a dedicated automation rule for each one, plus the externals come and go anyway, so keeping the notification rules up to date would be an impossible chore.
  • Specific user groups - while external designers and prepress users do belong to specific user groups, there's no point in notifying e.g. all freelance designers about a handover concerning only one of them.

We would really appreciate an option for picking People type custom fields as comment and mention recipients. 

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

FYI there's another thread, started by Marco Eberl on May 23, 2023 Automation Rules: Notify/Mention users from custom field type "user", essentially the same request, with 10 upvotes at the moment.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Thank you so much, Tuomo Suominen, for taking the time to detail your use case with screenshots and for referencing a similar post. We understand that some users are looking for this functionality, and our team is aware of it. Rest assured, we will ensure that all your comments are forwarded to the relevant Product Team. If there is any progress on this suggestion in the future, I’ll make sure to keep you informed. Thank you for your understanding.

Rohan V Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Rohan V Wrike Team member Become a Wrike expert with Wrike Discover

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Customfields in Automation.
[this list is visible for admins and agents only]

Top
Didn’t find what you were looking for? Write new post