Workflows: sequence multiple Objects

Marketing & Content Hub Lists, Lead Scoring & Workflows
,
1

When creating a Workflow, sometimes the goal is recieving information from multiple associated objects.

Example: I want to enhance the readability of Deals.
Every non-completed Task should write a Summary into multiline text.
This multiline text may be added to the Deal Preview to see open tasks more easily.

As is now, The Workflow structure would require you to sequence which Deal writes in which order. If you used a Deal-Workflow, you would not be able to single out Tasks in any way, shape or form.

If a Deal-Workflow were to trigger all Tasks, they would clash trying to overwrite the value at the same time - the result is a value missing Task-Input that was overwritten.

The solution to this should be either:

  • Lock other Objects out of editing a value that is already being edited.
    Make them wait, until they are save to edit.
  • Give the Workflow creator more control over which Object (in this case Task) writes first, then play them out in sequence with enough spacing to not overwrite input - essentially a for each.

In case of Testing: it does become a consistent issue, once about 5 or more Objects are involved. I find it likely it is a probability based on Threading or alikes.

I prefer the second option, because it gives more granular control of what you want to work with first and produces more predictable results.

2

Hi @MBohnke,

Have you considered using task-based workflows for this particular workflow? Using “Edit record”, you can append whatever you want to append to a multi-line text property by setting the target property to its current value, followed by whatever you want to append.

You don’t have any control over the order, but all task workflow executions will append their value just fine.

Best regards

3

yes and no - if all Tasks are triggered at the same time, they try overwriting the same property in my e.g. Deal at the same time resulting in the same issue.

It does only work when a Task adds itsself the moment it is e.g. created.
Retroactively initiating all at once results in that very issue.

I chose this example, since closing a task would also require you to re-write the text input to delete the finished task so you cannot avoid the issue of having to trigger multiple tasks at once.