When setting up workflow, you will see an option to enable chaining to other workflows as shown:
This feature allows you to connect two or more workflows without them being part of the same chain/node. Therefore, you can set up multiple workflows separate to each other that still function as a unit. This is to allow app builders to control is a workflow outcome should trigger another workflow or act as separate and unconnected processes, even with integrated child and parent apps.
For example, you could have a workflow to link to the parent which should then send an email containing the information from the parent to the user.
For this, you would need to separate these two so that you have separate starting nodes as shown:
For this, you will need to enable chaining from the first workflow so that it can link to the second workflow as shown:
The first workflow will link the child to the parent - like this:
The second workflow will be triggered when the fields linked to the parent are updated and will send an email with the parent's info.
For example, when using workflow to copy and link a record from within a parent app to a child app, you can then set up a workflow in the child app that is triggered on record creation.
This would mean that the workflow would enact as such:
So the original workflow in the parent would create the record in the child and then this would trigger the workflow in the child to send the email notifying the person of a record being created.
To do this, you would need to enable chaining workflow in the parent workflow as this is the one that triggers the second workflow in the child.
So this would look like this:
Similarly, this can work in the opposite direction, where workflow in the child record can trigger one within the parent record.
A child expression within the parent record will need to be in place to detect the change in the child record – for more information on child expressions click here
The child record could have a workflow to trigger a change in the field value, which is then pulled into the parent record through the isnull([Parent.ParentFieldName], 'Value if no Parent') expression.
This could then be a filter within the parent workflow to trigger an email to notify the user of a change in field value, like this:
Enable chaining from the first workflow - in this case the child workflow:
For more information about the configuration and uses of workflows, click here