2 years ago

In part 1 of this series, we introduced the three most common abstract workflows based on the method in which they are initiated. But what makes an abstract workflow a concrete workflow are the different types of components that make up the workflow.

As we saw under the invitation workflow, this component helps in authenticating and ensuring that the user is actually the legitimate consumer who he/she claims to be.

This component is responsible for provisioning the consumer account in the system, which in fact is the essence of an onboarding workflow.

This is a security component that is used in a workflow to block access to the system until a certain stage in the workflow is passed.