| Conditional steps || |
| Condition verification || Specifies an "if(condition) - then »instruction. |
| Conditional branch || Specifies an "other - if - then" logical instruction. This can only be used with a check condition. |
| Default action || Specifies a logical "else" statement. This can only be used with a check condition. |
| Waiting steps || |
| Wait condition || Waits until a specific condition is met. Not applicable for real-time workflows. |
| Parallel Wait Branch || Specifies another wait condition with a set of additional steps that can be performed once the initial criteria are met. |
| Action steps || |
| Create record || Creates a record of the specified entity with the specified default values. |
| Update Record || Updates the selected record with specified or dynamic values. |
| Assign Record || Assigns the selected record to a user or a team. |
| Send e-mail || Sends an e-mail. |
| Perform action || Specifies custom workflow steps (and actions). These custom steps should be developed by a CRM developer. |
| Change status || Changes the status of the selected record. |
| Stop workflow || Stop the current workflow |
Example flow ofwork
In this example we will create a simple workflow that runs in the background to assign any newly created contact record to a specific user and then send a welcome email to the customer .
Step 1 - Go to Settings → Processes.
Step 2 - Click New.
Step 3 - In the CreateProcess window, enter the following details -
Process name - New client workflow (This can be any name you want)
Category - Workflow
Entity - Contact (This will be the on which you create the workflow. In our case it is Contact)
Execute this workflow in the background (recommended) - Check this option because we are creating a workflow hrone in the background. Finally, click OK.
Step 4 - In the New Process window, enter the following details -
Activate as - Process
Scope - User
Start when - L 'recording is created
Click on Add a step → Assign a recording.
Step 5 - You will see a new step added to the workflow. In this step, we will specify the user to which all created contacts should be assigned. Enter the name of the stage as Assign Record to Team . The Assign option will be defined by default as the entity on which we create the workflow (Contact in our case). Click the Search icon.
Step 6 - In the search window, select the user you want. You can even select a specific team to which you want to assign the recordings. Click on Add.
Step 7 - Add another step by clicking Add step → Send email. In this step , we will configure the sending of e-mail to the client.
Step 8 - A new step will be added. Enter their name as Email Customer. Click Set Properties.
Step 9 - In the next window to configure e-mail, do the following -
From - Cliquez on Of field. In the right panel, select OwningUser and User. Click Add → OK.
To - Click on the To field. In the right panel, select Contact & Contact. Click Add → OK.
Subject - Enter a relevant subject.
Body - Enter relevant Body content.
Step 10 - Click Save, then click Activate.
Step 11 - In the next Process Activate Confirmation pop-up window, click Activate.
Step 12 - Go to the Contacts tab and create a new contact. As soon as you create a new contact by saving the record, you will see the Owner field set to the user, which you had configured in the workflow. Additionally, if you click on the Activities tab, you will see an email activity being created for this contact. This confirms that the workflow executed correctly.
Workflow vs Plugin
Workflows and Plugins d can both be used to extend and automate CRM functionality.In many scenarios, bothoches can be used interchangeably in place of each other. For example, if you have a simple requirement to email your customers, you can do so through a plugin or a workflow.
So, how do you choose between creating a workflow or a plugin? The following list tries to explain the same thing -
Although plugins and workflows can both be used to execute synchronous logic and hrone, plugins are generally preferred for synchronous logic, while workflows for hrone logic.
In general, to implement complex business logic, plugins are preferred over workflows. Workflows are preferred when you want to achieve relatively simpler functionality (such as sending emails, assigning users, etc.)
Plugins should be developed with coding, while workflows pcan be configured directly by professional users without any knowledge of workflows.
Workflows can be executed on demand. Therefore, if there are any requirements for which the user wants to execute logic manually, then workflows would be a better choice.
From a performance point of view, synchronous plugins offer better performance (and better throughput) compared to real-time workflows in scenarios where the frequency of requests is higher.
This chapter introduced us to one of the most important features of CRM - Workflows. We first understood the sync / hronize workflows, messages, scope, steps and finally looked at a live example of creating and running a workflow. Finally, we saw the differences between a workflow and a plugin.