Common Tasks

Task has different sections and Common Tasks is one of them. As the name suggests it has common and familiar features. Enlarge the Common Tasks group which will have few sub sections like Display, Save, Notification, Decision and Connect.

Display Display task is used to render data on spreadsheet. User needs to select Maps and its relevant Data Intake to display data. Display Properties shows the list of existing maps and user needs to select relevant Data Intake for the included map. User needs to select at least one map for every Display task.

Save Save task is used to save data of spreadsheet back to CRM. User needs to select Maps for which save operation is to be done. Save Properties shows the list of All save groups and user needs to select at least one save group for every Save task.

Notification During workflow execution at any point if we need to notify user or we need to take simple user input like Yes/No or OK/Cancel to select next execution path Notification task comes handy and very useful.

Notification Properties has a Message Type property which has three possible values Static, Cell Reference and Named Range Reference. For Static message type user needs to provide message while for Cell Reference and Named Range Reference user needs to provide location or select Named Range from available named range list. User can show message content based on Message Type. Next property is Options with values Ok, Ok Cancel and Yes No. Notification has two out going paths named "True" and "False". When Option value is "Ok" there is only true path and for the rest of the options there are two paths. For every outgoing path user needs to select either the Step of the workflow or "Exit Workflow" to stop execution. User can also set the Image of the Notification based on what is the purpose of the Notification task.

And the last property is Loop threshold which is very important. This integer property indicates how many times the Step is allowed to execute in a single workflow execution. Based on outgoing path we may end up creating a loop where the same step gets executed multiple times. To avoid infinite looping of execution this property indicates the threshold value and on exceeding this value at runtime workflow gets terminated.

Decision This task has multiple outgoing paths based on multiple conditions configured. It provides the ability to design conditional flow based on multiple conditions. Decision task is very crucial when you want to have conditional flow in your workflow based on some set of conditions.

Connect Connect task provides the ability to change the CRM connection at runtime when you have to deal with data from multiple CRM connections in a single app. It's a very natural requirement to have data from multiple connections in a single app. To achieve this workflow designer have Connect task. You can have as many connect tasks as you want and each connect task has a property called Connection Identifier which is a unique name used to identify a connection across all workflows. Users can either type in a new connection identifier name or select it from the available list of connection identifiers. When Connect task is executed user needs to provide a connection to assign it to a connection identifier. Once the connection identifier is assigned a connection it remembers it and changes the active connection to the selected connection when executed. Connect properties also provide an option to select a connection for Identifier either "On Step Execution" or "Before workflow Start". If a workflow contains any Connect task configured to provide connection. Before workflow starts, a popup window to select a connection will appear before workflow execution.

Connect task will connect apps to multiple org's workflows, and migrate the data from one app to another during runtime. When a workflow is created using connect task then, the workflow will take the data from Org 1 and display or migrate the data to Org 2.

Follow the below steps to create a workflow with connect task.

  • Open an app and create a workflow.

  • Now, drag and drop the connect from Common Tasks.

  • On the right-hand side now select the Connection Identifier where the user needs to map the workflow to an active connection.

  • Select either you want to execute it " On Step Execution" or "Before the workflow starts" and click Save.

  • Save and run the workflow.

Here, is an example of a Connect task multi-org data migration or comparison app. Steps in Blue are from Org 1 which are connecting the steps in Green from Org 2.

Last updated