> For the complete documentation index, see [llms.txt](https://docs.valorx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valorx.com/valorx-fusion/design-studio/workflow-and-ux/common-tasks.md). # Common Tasks The Task feature includes several sections, one of which is **Common Tasks**. As the name implies, this section contains frequently used and familiar functions. Expand the **Common Tasks** group to view its subsections, which include **Display**, **Save**, **Notification**, **Decision**, and **Connect**. ![](https://2472585788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFqFFf4143HS0_Wagnz%2Fuploads%2F3YONHxA8ylQsLdnzkM96%2FCommon%20Tasks.gif?alt=media\&token=43ee4dcb-f526-45e4-9b30-a02557d4b688) ## 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. ![](https://2472585788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFqFFf4143HS0_Wagnz%2Fuploads%2FmV4uMieXWems9KO3lY0y%2FDisplay.gif?alt=media\&token=8f8aa036-964b-49cb-b097-2a897c67a868) *** ## 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. ![](https://2472585788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFqFFf4143HS0_Wagnz%2Fuploads%2F2uKrdtWOLkG9oAN6s3FM%2FSave%20Task%20Properties.gif?alt=media\&token=185ac33d-5013-437d-b1b2-825ff1203a8a) *** ## Notification The Notification task shows a message to users while a workflow is running. You can use it to share information, warn users before an action, ask a simple question (such as Yes/No or OK/Cancel), or collect input from users. Based on the button the user clicks, the workflow continues along a different path.

### Notification Properties

Property	Description
Step Name	The name of the Notification step in the workflow.
Message Type	Choose where the message comes from: Static (type the message yourself), Cell Reference (read the message from a cell), or Named Range Reference (read the message from a named range). Click Preview to see how the notification will look.
Message	The message shown to users. For Cell Reference or Named Range Reference, select the cell or named range instead.
Image	The icon shown with the message. Choose an icon that matches the purpose of the notification: Information, Error, Warning, Question, Stop, Exclamation, Hand, or Asterisk.
Loop threshold	The maximum number of times this step can run in a single workflow run. See Loop Threshold below.
Options	The buttons shown on the notification window: Ok, Ok Cancel, Yes No, or Custom. See Options below.
Configure Data Capture	Adds input fields to the notification so users can enter information. Click Configure Data Capture to set up the fields and choose where the data is saved. See Data Capture below.
Include Save Summary	Adds the data captured in this notification to the Save Summary. After a Save task runs, the changes appear in the Save Summary popup window.
Silent Mode	Writes the message to the logs instead of showing the notification to users. Leave this unchecked when users need to see the notification or enter data.

#### Options The Options setting controls which buttons appear on the notification window. Each button is linked to a workflow path: **OK** and **Yes** follow the **True** path, while **Cancel** and **No** follow the **False** path. For each path, choose the next step the workflow should go to, or select **Exit Workflow** to stop the workflow.

Option	Buttons shown	True path	False path
Ok	OK	OK	Not available
Ok Cancel	OK, Cancel	OK	Cancel
Yes No	Yes, No	Yes	No
Custom	Buttons you set up yourself	True button	False button (optional)

#### Custom Options Choose **Custom** when you want to name the buttons yourself or choose which buttons appear. The following settings are available:

Setting	Description
True and True Button Label	The path for the True button and the text shown on it. For example, change the label to Approve.
Show False Button	Shows a False button on the notification window. When selected, you can set the False path and False Button Label.
Allow Data Capturing on False Button	Saves the user's input when they click the False button. Available when Show False Button and Configure Data Capture are selected. See Data Capture below.
Exit Button	Shows an Exit button that closes the notification window without saving any data.

#### Data Capture When **Configure Data Capture** is selected, the notification window includes input fields for users to fill in, such as a comment or a value. The data they enter is saved to the cell or named range you assign. **Set Up Input Fields** Click **Configure Data Capture** to open the Notification window. Here you can add, edit, and remove the input fields shown to users. 1. Click **Add User Input**. The **Enter Input Details** window opens. 2. Enter the following details:

Field	Description
Input Label	The name shown next to the input field, for example Comment. This field is required.
Data Type	The type of data users enter: String (text), Number, Boolean (true or false), Date, File, or Picklist (a list of values to choose from). For Picklist, see Set Up Picklist Values below.
Input Type	Where the data is saved: Cell Reference or Named Range Reference.
Cell for location or Named Range	The location where the data is saved. For Cell Reference, type the cell address (for example, Sheet1!$A$1) or click the Excel icon to select it. For Named Range Reference, choose a named range from the list. This field is required.
Default Value Intake	The value already filled in when the notification opens. Users can keep it or change it. Choose None (empty field), Static (type the default value), Cell Reference (read the value from a cell), or Named Range Reference (read the value from a named range).
Required	Select this if users must fill in the field before continuing.

3. Click **Save**. The input field appears in the list. 4. Repeat these steps to add more input fields. Click **Preview** to see how the input fields will look to users. 5. Click **Save** to close the Notification window 6. To change an input field, click the edit icon next to it. To remove it, click the delete icon.

**Set Up Picklist Values** When you choose **Picklist** as the Data Type, click the **Picklist Values** icon (the gear icon next to Data Type) to choose the values users can pick from. In the **Configure Picklist Options** window, select a **Picklist Type**:

Picklist Type	Description
Existing Picklist	Uses the values of an existing picklist field in your CRM. Select the Object and Field, for example Account and Account Type.
Custom Picklist	Uses a list of values you enter yourself. Click the icon next to Custom Picklist Values, enter one value per line, then click Add. You don't need to put quotes around the values.
NamedRange Picklist	Uses the values in a named range in your workbook. Choose the named range from the Selected NamedRange list.

Click **Save** to apply the picklist values. **When Data Is Saved** By default, data is saved only when users click the **True** button. With **Custom** options, you can also save data when users click the **False** button by selecting **Allow Data Capturing on False Button**.

Button clicked	Data saved?
True	Yes
False	Only when Allow Data Capturing on False Button is selected
Exit	No, the notification window closes without saving data

This is useful when you need input from users whichever way they respond. For example, in an approval workflow, you can collect a comment from users whether they approve or reject a request. #### Loop Threshold Depending on how paths are set up, a workflow can loop back and run the same step more than once. The **Loop threshold** sets how many times this step can run in a single workflow run. If the limit is reached, the workflow stops. This prevents the workflow from running in an endless loop. *** ## 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. ![](https://2472585788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFqFFf4143HS0_Wagnz%2Fuploads%2FPn1ydOS6dwmuMqTiXHxj%2FConnect.png?alt=media\&token=06c506f0-9349-4fb3-a55b-d2fe7f644256) 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. ![](https://2472585788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFqFFf4143HS0_Wagnz%2Fuploads%2Fgp0rY8oOjJbA7AxfThhg%2FConnect.png?alt=media\&token=b59e6b0d-3e6a-4644-b2ba-1ccef4d367c8)