In this activity, we learnt how to build and customise workflows.

We learned about the anatomy of a workflow and how to configure tools like scope and actions, as well as things to consider about security and ownership.

We first discussed the major building blocks of workflow configuration. We talked about the four major areas to consider when you’re configuring a workflow: when to start them. Should they be real-time or background? What actions should they perform? And under what conditions should these actions be performed?

We also discussed how the workflow can be configured to start automatically in response to the events, such as create, update, delete, change in record status, or change in record ownership.

They can start manually by a user or as a child workflow that will be started by another workflow process.

We learned about actions, which are the steps you can add to the workflow process. These actions control the flow of the workflow and allow you to create branches of actions that only get processed when certain conditions are met.

We discussed the different types of actions, including conditional actions, such as check conditions, condition of branches, weight conditions, and so on.

We discussed modification actions, such as create record, update record and then other actions, such as sending an email, starting a child workflow, stopping a workflow, and custom actions.

We then practised by creating, configuring, and testing a workflow.

We also learnt about why to use a custom action, when to use them, and how to create and use one. Custom actions are a type of process very similar to real-time workflows. They have similar properties created and edited in the workflow editor and used the same building blocks, stages, conditions, and actions.

We then learned a few more advanced workflow items. We discussed using real-time workflows. Though we discussed scope before, we went into a bit deeper detail for some advanced scope capabilities, as well as some of the security context to keep in mind for background and real-time workflows.

We discussed runtime management as well as common patterns and techniques. As well as about working with other automation. When building automation, including workflows, you need to take into consideration other automation that already exists or will be built.

Join the discussion

Think of a workflow that you would like to initiate in your business. Share with us some the techniques or steps that you would like to implement within the workflow so that it becomes a seamless process within your business.

Use the discussion section below and let us know your thoughts. Try to respond to at least one other post and once you’re happy with your contribution, click the Mark as complete button to check the step off, then you can move to the next step.