Define / change the value of a property based on a task completion status

The main objective would be to be able to define or change the value of a property of a specific transaction based on a task completion status.

There are multiple ways of doing this but after trying many options, I found that the easiest one would be to have “Activities: properties” as a trigger for transaction-based workflows (as we currently have for Contact-based workflows). It’s currently possible to do this for contacts but not for specific transactions.

An example of what is possible today and what I would like to do:

Context:

1 contact

2 associated transactions (“Transaction 1” and “Transaction 2”)

Today:

Transaction 1 reaches phase 3 of its pipeline. A task (“ToDo A”) is automatically created. This task is linked to Transaction 1 and the contact.

Another transaction-based workflow does: if “Todo A” is completed, then define “Property X” to “Yes”. That will modify Property X on both Transaction 1 and Transaction 2, even if Todo A is only linked to Transaction 1 because there is no way to identify the transaction.

Tomorrow:

Transaction 1 reaches phase 3 of its pipeline and a task (“ToDo A”) is automatically created. This task is thus linked to Transaction 1 and the contact.

Another transaction-based workflow does: if Todo A is completed, then define Property X to “Yes” only for transactions associated with this Todo or only for transactions in phase 3 or only for transactions with property Y value = “Yes”.

I hope it’s clear, and that we’ll soon have a solution to this major problem that requires minimal improvement in the way workflow works (I guess)

A very interesting idea !

@RValverde great idea. Nice work! :+1:

Hey, I like this idea a lot. Is there any way how to set it, please? :woman:

Hi everyone,

Thanks for taking the time to explain the use cases for this request and upvote the idea. While I recognize there are ways we could use triggers to drive a process like this, I also want to call attention to new functionality we released in early 2021 that some customers are successfully using for processes like this.

The “Delay until event happens” action can be used to delay until a task created earlier in the workflow gets update, for example it can delay until the task status is changed to “complete.” For this to work, the task therefore must also be being created by the workflow. Our KB documentation has more information about this action, and there is even a gif in there with the Delay until task is completed use case. Then, the workflow moves on once that task is complete, and can do something related, like set a property at that time. Here is an example:


delay a workflow until a task has been completed

I would love your feedback on if this feature is helpful to your goals, and / or how we could improve it. Also, I wonder if it is too hard to find, and how we might make that easier too : )

Best,

Megan