Open Documentation Menu

Flows

Salesforce Flow enables you to automate complex business processes. Use the DMS options in Flow Builder in order to work directly with your documents in your flows.

You can carry out simple document actions as well as more complex processes with the help of ready-made modules. You can also put together your own processes from the individual modules. You can use the following modules, among others:

  • Apex actions

  • Apex-defined data types

  • Subflows

  • Flow templates

Retrieving a document

You can retrieve the properties of a DMS document in a separate flow.

You can use the Apex action Get DMS Document to determine the properties of a document within a flow based on the document ID.

Creating the input variables

The Apex action expects a required parameter: The ID of the DMS document. We recommend creating a corresponding variable for this parameter so that you can configure the variable as an input for your flow, for example.

This is how it works 

  1. Navigate to Flow Builder > Toolbox.

  2. Click New Resource to create a new variable for the document ID (DMS Document ID).

  3. Select Variable as the resource type.

  4. Enter a unique name for your variable (e.g. dmsDocumentId).

  5. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  6. Optional: Give your variable a default value or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

Calling the Apex action

Once you have created the variable resource for the input, call the Apex action Get DMS Document.

This is how it works 

  1. Add the Action element to the flow.

  2. Select the filter Dvelop or Apex action as the Category or Type.

  3. Select the Get DMS Document action in the selection list.

  4. Under Label, enter a label for your action. 

  5. Under API name, enter a unique name for your action.

  6. Use the variables you have already created for the input values.

  7. Optional: Define the input value Run as Service-User. Use the value True if the access details of the general system user are to be used. If you leave the input value blank or use False, the access details of the executing user are used.

Handling the output

When the Apex action has been executed, the Apex action returns the DMS document. If you want to continue using the DMS document, we recommend creating a variable.

This is how it works 

  1. Create a new variable for the DMS document. To do so, follow the instructions under Creating the input variables.

  2. Select your Apex action.

  3. Click Edit element.

  4. Under Advanced options, activate the option Manually assign variables.

  5. Under Output Value, select your new variable for the DMS document.

Updating a document

You can update the properties of a DMS document in a separate flow.

You can use the Apex action Update DMS Document to update the properties of a document within a flow.

Creating the input variables

The Apex action expects two required parameters: The ID of the DMS document that is to be updated and a list of properties that are to be adapted. We recommend creating corresponding variables for these parameters so that you can configure them as inputs for your flow, for example.

This is how it works 

  1. Navigate to Flow Builder > Toolbox.

  2. Click New Resource to create a new variable for the document ID (DMS Document ID).

  3. Select Variable as the resource type.

  4. Enter a unique name for your variable (e.g. dmsDocumentId).

  5. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  6. Optional: Give your variable a default value or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

  7. Click New Resource to create a new variable for the list of properties to be updated (Updated Attributes).

  8. Select Variable as the resource type.

  9. Enter a unique name for your variable (e.g. updatedAttributes).

  10. Select Defined by Apex as the data type for your variable.

  11. Select the Apex class dvelop_docs_dev__DocumentAttribute. 

  12. Activate the check box for Allow multiple values (collection).

  13. Click New Resource to create an auxiliary variable. The auxiliary variable defines an updating property that is added to the list created previously.

  14. Select Variable as the resource type.

  15. Enter a unique name for your variable (e.g. attributeContainer).

  16. Select Defined by Apex as the data type for your variable. Select the Apex class dvelop_docs_dev__DocumentAttribute. Leave the check box for Allow multiple values (collection) deselected.

You can add additional optional parameters to the Apex action, e.g.:

  • Updated Category 

    • Type: Text

    • Collection: No

Repeat steps 2 to 6 for the other parameters that you wish to use.

Filling the variables

You can use the Apex class dvelop_docs_dev__DocumentAttribute to define a list variable. An auxiliary variable is required for the list variable. The auxiliary variable temporarily isolates the required data for an attribute. You then add the auxiliary variable to the list variable.

This is how it works 

  1. Add the Assignment element to the flow.

  2. Select dvelop_docs_dev__DocumentAttribute and key under Variable.

  3. Select the operator Equal.

  4. Enter the attribute key (e.g. objecttitle) for the value of the assignment.

  5. Click Add assignment.

  6. Define the value of your attribute. To do this, repeat the procedure and select the property value of your auxiliary variable under Variable.

  7. Optional: Add more values for the updated attribute, e.g. for an attribute with a lot of values. To do so, proceed as follows:

    1. Click Add assignment.

    2. Under Variable, select your auxiliary variable and the values property of the auxiliary variable (note the plural). Please note that the value property is always required for the first value of the attribute; otherwise, incorrect attribute values can occur.

    3. Select the operator Add.

    4. Enter the next desired value for the attribute.

  8. When you have assigned all values to the property, click Add assignment.

  9. Select your list of attributes as the variable.

  10. Select the operator Add.

  11. Select your auxiliary variable as the value.

  12. Repeat all of the preceding steps for the remaining attributes.

Calling the Apex action

Once you have created the variable resources for the input, you can call the Apex action Update DMS Document.

This is how it works 

  1. Add the Action item to the flow.

  2. Select the filter Dvelop or Apex action for Category or Type.

  3. Select Update DMS Document in the selection list.

  4. Under Label, enter a label for your action.

  5. Under API name, enter a unique name for your action.

  6. Use the variables you have already created for the input values.

  7. Optional: Define the input value Run as Service-User. Use the value True if the access details of the general service user are to be used. If you leave the input value blank or use False, the access details of the executing user are used.

Handling the output

After executing the Apex action, you will receive the ID of the updated document for further processing. If you want to continue using the ID, we recommend creating a variable for the ID.

This is how it works 

  1. Follow the instructions under Creating the input variables and create a new variable for the document ID.

  2. Select your Apex action and click Edit element.

  3. Under Advanced options, activate the switch Manually assign variables.

  4. Select your new variable as the output value for the document ID.

Creating a folder

You can use the Apex action Create DMS Folder to create a folder in the DMS within a flow.

Creating the input variables

The Apex action expects two required parameters: The ID of the DMS document that is to be updated and a list of properties that are to be adapted. We recommend creating corresponding variables for these parameters so that you can configure the variables as inputs for your flow, for example.

This is how it works 

  1. Navigate to Flow Builder > Toolbox.

  2. Click New Resource to create a new variable for the DMS category of the folder (Category).

  3. Select Variable as the resource type and enter a unique name for your variable (e.g. folderCategory).

  4. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  5. Optional: Give your variable a default value or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

  6. Click New Resource to create a new variable for the list of properties for the folder (Attributes).

  7. Select Variable as the resource type and enter a unique name for your variable (e.g. folderAttributes).

  8. Select Defined by Apex as the data type for your variable. Select dvelop_docs_dev__DocumentAttribute as the Apex class. Activate the check box for Allow multiple values (collection).

  9. Click New Resource to create an auxiliary variable.

  10. Select Variable as the resource type and enter a unique name for your variable (e.g. attributeContainer). The auxiliary variable defines a property for the folder that is then added to the list created previously.

  11. Select Defined by Apex as the data type for your variable. Select dvelop_docs_dev__DocumentAttribute as the Apex class. Leave the check box for Allow multiple values (collection) deselected.

Filling the variables

You can use the Apex class dvelop_docs_dev__DocumentAttribute to define a list of document attributes. To fill such a list variable, an auxiliary variable is required that temporarily encapsulates the necessary data for an attribute and is then added to the collection of attributes.

This is how it works 

  1. Add the Assignment element to the flow.

  2. Under Variable, select your auxiliary variable of the Apex-defined data types dvelop_docs_dev__DocumentAttribute and the key property.

  3. Select the operator Equal.

  4. Enter the attribute key (e.g. objecttitle) for the value of the assignment.

  5. Click Add assignment.

  6. Define the value of your attribute. Repeat the process for this and under Variable, select the value property of your auxiliary variable.

  7. Optional: Add more values for the updated attribute, e.g. for an attribute with a lot of values. To do so, proceed as follows:

    1. Click Add assignment.

    2. Under Variable, select your auxiliary variable and then the values property (note the plural). Please note that the value property is always required for the first value of the attribute; otherwise, incorrect attribute values can occur.

    3. Select the operator Add.

    4. Enter the next desired value for the attribute.

  8. When you have assigned all values of the property, click Add assignment.

  9. Select your list of attributes as the variable.

  10. Use the operator Add.

  11. Select your auxiliary variable as the value.

  12. Repeat all of the preceding steps for the remaining attributes.

Calling the Apex action

Once you have created the variable resources for the input, you can call the Apex action Create DMS Folder.

This is how it works 

  1. Add the Action element to the flow.

  2. Select the filter Dvelop or Apex action for Category or Type.

  3. Select the Create DMS Folder action in the selection list.

  4. Under Label, enter a label for your action.

  5. Under API name, enter a unique name for your action.

  6. Use the variables you have already created for the input values.

  7. Optional: Define the input value Run as Service-User. Use the value True if the access details of the general service user are to be used. If you leave the input value blank or use False, the access details of the executing user are used.

Handling the output

After executing the Apex action, you will receive the ID of the created folder for further processing. If you want to continue using the ID, we recommend creating a variable for the ID.

This is how it works 

  1. Follow the instructions under Creating an input variable and create a new variable for the folder ID.

  2. Select your Apex action and click Edit element.

  3. Under Advanced options, activate Manually assign variables. 

  4. Select your new variable as the output value for the folder ID.

Downloading a document

You can download a single document in the DMS in a separate flow and attach it to a data record.

You can use the Apex action Download DMS Document to Record to download a document within a flow based on the document ID and attach it to a Salesforce data record.

Creating the input variables

The Apex action expects two required parameters: The ID of the data record and the ID of the DMS document. We recommend creating corresponding variables for these parameters so that you can configure them as inputs for your flow, for example.

This is how it works 

  1. Navigate to Flow Builder > Toolbox.

  2. Click New Resource to create a new variable for the ID of the data record (Record ID).

  3. Select Variable as the resource type and enter a unique name for your variable (e.g. recordId).

  4. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  5. Optional: Give your variable a default value or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

  6. Click New Resource to create a new variable for the ID of the document (DMS Document ID).

  7. Select Variable as the resource type and enter a unique name for your variable (e.g. documentId).

  8. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  9. Optional: Give your variable a default value or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

Calling the Apex action

Once you have created the variable resources for the input, you can call the Apex action Download DMS Document to Record.

This is how it works 

  1. Add the Action element to the flow.

  2. Select the filter Dvelop or Apex action for Category or Type.

  3. Select the Download DMS Document to Record action in the selection list.

  4. Under Label, enter a label for your action.

  5. Under API name, enter a unique name for your action.

  6. Use the variables you have already created for the input values.

  7. Optional: Define the input value Run as Service-User. Use the value True if the access details of the general service user are to be used. If you leave the input value blank or use False, the access details of the executing user are used.

Handling the output

After executing the Apex action, you will receive the ID of the created document (ContentDocument) for further processing. If you want to continue using the ID, we recommend creating a variable for the ID.

This is how it works 

  1. Follow the instructions under Creating an input variable and create a new variable for ContentDocument.

  2. Select your Apex action and click Edit element.

  3. Under Advanced options, activate Manually assign variables.

  4. Select your new variable as the output value for ContentDocument.

Downloading several documents

You can download several DMS documents in a separate flow and attach them to a data record.

You can use the Download Documents subflow to download several documents within a flow based on the document IDs and attach them to a Salesforce data record.

Creating the input variables

The subflow expects two required parameters: The ID of the data record and a list of IDs of the DMS documents. We recommend creating corresponding variables for these parameters so that you can configure them as inputs for your flow, for example.

This is how it works 

  1. Navigate to Flow Builder > Toolbox.

  2. Click New Resource to create a new variable for the ID of the data record (recordId).

  3. Select Variable as the resource type and enter a unique name for your variable (e.g. recordId).

  4. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  5. Optional: Give your variable a default value or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

  6. Click New Resource to create a new variable for the list of IDs for the DMS documents (documentIdsToDownload).

  7. Select Variable as the resource type and enter a unique name for your variable (e.g. documentIds).

  8. Select Text as the data type for your variable. Activate the check box for Allow multiple values (collection).

Filling the variables

You can fill a list of document IDs in different ways. For example, you can fill the entire list by writing the output of a previous action directly to the variable. The simplest way, however, is to add individual IDs using an assignment element.

This is how it works 

  1. Add the Assignment element to the flow.

  2. Select the list variable you created previously as the variable.

  3. Select Equal as the operator.

  4. Enter the ID of a DMS document for the value of the assignment.

  5. Repeat all of the preceding steps for more document IDs.

Calling the subflow

Once you have created the variable resources for the input, you can call the Download Documents subflow.

This is how it works 

  1. Add the Subflow element to the flow.

  2. Select the flow d.velop: Download Documents.

  3. Under Label, enter a label.

  4. Under API name, enter a unique name.

  5. Use the variables you have already created for the input values.

  6. Optional: Define the input value Run as Service-User. Use the value True if the access details of the general service user are to be used. If you leave the input value blank or use False, the access details of the executing user are used.

Handling the output

After executing the subflow, you will receive a list of all IDs of the created documents (ContentDocument) for further processing. If you want to continue using the IDs, we recommend creating a variable for the IDs.

This is how it works 

  1. Follow the instructions under Creating an input variable and create a new variable for ContentDocument. 

  2. Tag the variable as a collection.

  3. Select your subflow and click Edit element.

  4. Under Advanced options, activate Manually assign variables.

  5. Select your new variable as the output value for ContentDocument.

Uploading a document

You can upload a document to the DMS in a separate flow.

You can use the Apex action Upload ContentDocument to upload a document within a flow based on its ContentDocument ID and thereby adapt the properties of the DMS document to be created.

Creating the input variables

Once you have created the variable resources for the input, you can call the Apex action Upload ContentDocument.

This is how it works 

  1. Add a new Action element to the flow.

  2. Select the filter Dvelop or Apex action for Category or Type.

  3. Select the action Upload ContentDocument in the selection list.

  4. Under Label, enter a label for your action.

  5. Under API name, enter a unique name for your action.

  6. Use the variables you have already created for the input values.

  7. Optional: Define the input value Preserve file after upload. Use the value True if the document is to be retained after it has been successfully uploaded to Salesforce. If you leave the input value blank or use False, the document will be deleted once it has been uploaded.

Filling the variables

You can use the Apex class dvelop_docs_dev__DocumentAttribute to define a list of document attributes. To fill such a list variable, you require an auxiliary variable that temporarily encapsulates the necessary data for an attribute and is then added to the collection of attributes.

This is how it works 

  1. Add the Assignment element to the flow.

  2. Under Variable, select your auxiliary variable of the Apex-defined data types dvelop_docs_dev__DocumentAttribute and the key property.

  3. Select Equal as the operator.

  4. Enter the attribute key (e.g. objecttitle) for the value of the assignment.

  5. Click Add assignment.

  6. Define the value of your attribute. Repeat the process for this and under Variable, select the value property of your auxiliary variable.

  7. Optional: Add more values for the updated attribute, e.g. for an attribute with a lot of values. To do so, proceed as follows:

    1. Click Add assignment.

    2. Under Variable, select your auxiliary variable and its values property (note the plural). Please note that the value property is always required for the first value of the attribute; otherwise, incorrect attribute values can occur.

    3. Select the operator Add.

    4. Enter the next desired value for the attribute.

  8. When you have assigned all values of the property, click Add assignment.

  9. Select your list of attributes as the variable.

  10. Use the operator Add.

  11. Select your auxiliary variable as the value.

  12. Repeat all of the preceding steps for the remaining attributes.

Calling the Apex action

Once you have created the variable resources for the input, you can call the Apex action Upload ContentDocument.

This is how it works 

  1. Add the Action element to the flow.

  2. Select the filter Dvelop or Apex action for Category or Type.

  3. Select the action Upload ContentDocument in the selection list.

  4. Under Label, enter a label for your action.

  5. Under API name, enter a unique name for your action.

  6. Use the variables you have already created for the input values.

  7. Optional: Define the input value Preserve file after upload. Use the value True if the document is to be retained after it has been successfully uploaded to Salesforce. If you leave the input value blank or use False, the document will be deleted once it has been uploaded.

Searching for documents

You can search for DMS documents in a separate flow.

You can use the Apex action Search DMS Documents to search for DMS documents within a flow.

Creating the input variables

The Apex action expects a required parameter: The ID of the data record that is to be used as context for the search for the DMS documents. Depending on this ID, search categories and search attributes are determined from the configured mappings and assignments. We recommend creating a corresponding variable for this parameter so that you can configure the variable as an input for your flow, for example.

This is how it works 

  1. Navigate to Flow Builder > Toolbox.

  2. Click New Resource to create a new variable for the ID of the data record (Record ID).

  3. Select Variable as the resource type and enter a unique name for your variable (e.g. recordId).

  4. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  5. Optional: Define a default value for your variable or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

You can add additional optional parameters to an Apex action to specify and format the search results. Below is a list of the parameters with their respective data types. Repeat steps 2 to 4 for the other parameters that you wish to use.

  • Search Categories 

    • Type: Text

    • Collection: Yes

  • Search Attributes 

    • Type: Apex-defined (dvelop_docs_dev__DocumentAttribute)

    • Collection: Yes

  • Hide Folders? 

    • Type: Boolean

    • Collection: No

  • Sort-Property 

    • Type: Text

    • Collection: No

  • Sort-Direction 

    • Type: Text (ascending/descending)

    • Collection: No

  • Search Text 

    • Type: Text

    • Collection: No

  • Maximum Age of Results in Days 

    • Type: Number

    • Collection: No

Defining additional search attributes

To search for additional attributes, you must fill your previously created list variable with the values of the attributes.

You can use the Apex class dvelop_docs_dev__DocumentAttribute to define a list of document attributes. To fill such a list variable, an auxiliary variable is required that temporarily encapsulates the necessary data for an attribute and is then added to the collection of attributes.

This is how it works 

  1. Add a new Assignment element to the flow.

  2. Under Variable, select your auxiliary variable of the Apex-defined data types dvelop_docs_dev__DocumentAttribute and the key property.

  3. Select Equal as the operator.

  4. Enter the property key (e.g. objecttitle) for the value of the assignment.

  5. Click Add assignment.

  6. Define the value of your attribute. To do this, repeat the procedure and select the property value of your auxiliary variable under Variable.

  7. Optional: Add more values for the updated attribute, e.g. for an attribute with a lot of values. To do so, proceed as follows:

    1. Click Add assignment.

    2. Under Variable, select your auxiliary variable and its values property (note the plural). Please note that the value property is always required for the first value of the attribute, otherwise incorrect attribute values can occur.

    3. Select the operator Add.

    4. Enter the next desired value for the attribute.

  8. When you have assigned all values of the property, click Add assignment.

  9. Select your list of attributes as the variable.

  10. Use the operator Add.

  11. Select your auxiliary variable as the value.

  12. Repeat all of the preceding steps for the remaining attributes.

Calling the Apex action

Once you have created the variable resources for the input, you can call the Apex action Search DMS Documents.

This is how it works 

  1. Add a new Action element to the flow.

  2. Select the filter Dvelop or Apex action for Category or Type .

  3. Select the Search DMS Documents action in the selection list.

  4. Under Label, enter a label for your action.

  5. Under API name, enter a unique name for your action.

  6. Use the variables you have already created for the input values.

  7. Optional: Define the input value Run as Service-User. Use the value True if the access details of the general service user are to be used. If you leave the input value blank or use False, the access details of the executing user are used.

Handling the output

After executing the Apex action, you will receive the ID of the DMS documents found for further processing. If you want to continue using the ID, we recommend creating a variable for the ID.

This is how it works 

  1. Follow the instructions under Creating an input variable and create a new variable for the DMS document IDs.

  2. Select your Apex action and click Edit element.

  3. Under Advanced options, activate Manually assign variables.

  4. Select your new variable as the output value for the DMS document IDs.

Searching for documents based on IDs

You can search for DMS documents in a separate flow based on IDs.

You can use the Apex action Search DMS Documents With IDs to search for DMS documents within a flow based on IDs.

Creating the input variables

The Apex action expects two required parameters: A list with IDs of the DMS documents and the key of the property that is assigned to the document ID in d.velop documents. We recommend creating a corresponding variable for this parameter so that you can configure the variables as input for your flow, for example.

This is how it works 

  1. Navigate to Flow Builder > Toolbox.

  2. Click New Resource to create a new variable for the list of document IDs (DMS Document IDs).

  3. Select Variable as the resource type and enter a unique name for your variable (e.g. documentIds).

  4. Select Text as the data type for your variable. Activate the check box for Allow multiple values (collection).

  5. Click New Resource to create a new variable for the key of the ID property (Searchattribute Key).

  6. Select Variable as the resource type and enter a unique name for your variable (e.g. documentId).

  7. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  8. Optional: Give your variable a default value or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

Filling the variables

You can fill a list of document IDs in different ways. For example, you can fill the entire list by writing the output of a previous action directly to the variable. The simplest way, however, is to add individual IDs using an assignment element.

This is how it works 

  1. Add a new Assignment element to the flow.

  2. Select the list variable you created previously as the variable.

  3. Select Equal as the operator.

  4. Enter the ID of a DMS document for the value of the assignment.

  5. Repeat all of the preceding steps for more document IDs.

Calling the Apex action

Once you have created the variable resources for the input, you can call the Apex action Search DMS Documents With IDs.

This is how it works 

  1. Add a new Action element to the flow.

  2. Select the filter Dvelop or Apex action for Category or Type .

  3. Select the Search DMS Documents With IDs action in the selection list.

  4. Under Label, enter a label for your action.

  5. Under API name, enter a unique name for your action.

  6. Use the variables you have already created for the input values.

  7. Optional: Define the input value Run as Service-User. Use the value True if the access details of the general service user are to be used. If you leave the input value blank or use False, the access details of the executing user are used.

Handling the output

After executing the Apex action, you will receive a list of the DMS documents found for further processing. If you want to continue using this list, we recommend creating a variable for it.

This is how it works 

  1. Follow the instructions under Creating an input variable and create a new variable for the DMS documents.

  2. Select your Apex action and click Edit element.

  3. Under Advanced options, activate Manually assign variables.

  4. Select your new variable as the output value for the DMS documents.

Sending e-mails with documents

In a separate flow, you can send e-mails with DMS and Salesforce documents attached.

You can use the Apex action Send Email with Documents to attach several DMS and Salesforce documents to an e-mail and send it within a flow.

Creating the input variables

The Apex action expects several required parameters: The e-mail subject, the body of the e-mail and a list of recipients. We recommend creating corresponding variables for these parameters so that you can configure them as inputs for your flow, for example.

This is how it works 

  1. Navigate to Flow Builder > Toolbox.

  2. Click New Resource to create a new variable for the subject of the e-mail (Subject).

  3. Select Variable as the resource type and enter a unique name for your variable (e.g. subject).

  4. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  5. Optional: Define a default value for your variable or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

  6. Click New Resource to create a new variable for the content of the e-mail (Body).

  7. Select Variable as the resource type and enter a unique name for your variable (e.g. body).

  8. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  9. Optional: Define a default value for your variable or make the variable available for input (e.g. to include the flow on a Lightning record page). Neither is necessary for the Apex action.

  10. Click New Resource to create a new variable for list of recipients (Recipients).

  11. Select Variable as the resource type and enter a unique name for your variable (e.g. recipients).

  12. Select Text as the data type for your variable. Activate the check box for Allow multiple values (collection).

You can add additional optional parameters to an Apex action in order to add attachments to the e-mail or add additional recipients (on Bcc/Cc). Below is a list of the parameters with their respective data types. Repeat steps 2–4 for the other parameters that you wish to use.

  • CC Recipients 

    • Type: Text

    • Collection: Yes

  • BCC Recipients 

    • Type: Text

    • Collection: Yes

  • DMS Document IDs 

    • Type: Text

    • Collection: Yes

  • ContentDocument IDs 

    • Type: Text

    • Collection: Yes

Filling the variables

You can fill a list of document IDs in different ways. For example, you can fill the entire list by writing the output of a previous action directly to the variable. The simplest way, however, is to add individual IDs using an assignment element.

This is how it works 

  1. Add a new Assignment element to the flow.

  2. Select the list variable you created previously as the variable.

  3. Select Equal as the operator.

  4. Enter the ID of a DMS document for the value of the assignment.

  5. Repeat all of the preceding steps for more document IDs and ContentDocument IDs.

Calling the Apex action

Once you have created the variable resources for the input, you can call the Apex action Send Email with Documents.

This is how it works 

  1. Add a new Action element to the flow.

  2. Select the filter Dvelop or Apex action for Category or Type .

  3. Select the Send Email with Documents action in the selection list.

  4. Under Label, enter a label for your action.

  5. Under API name, enter a unique name for your action.

  6. Use the variables you have already created for the input values.

  7. Optional: Define the input value Run as Service-User. Use the value True if the access details of the general service user are to be used. If you leave the input value blank or use False, the access details of the executing user are used.

Using the document list as a screen flow component

You can integrate the document list into a screen flow.

Creating the input variable

The screen flow component expects a required parameter: The ID of the required record. We recommend creating a corresponding variable for this parameter so that you can configure it as input for your flow, for example.

In addition, you have the option to create a variable to deactivate the upload.

This is how it works 

  1. Navigate to Flow Builder > Toolbox.

  2. Click New Resource to create a new variable for the data record ID.

  3. Select Variable as the resource type and enter a unique name for your variable (e.g. recordId).

  4. Select Text as the data type for your variable. Leave the check box for Allow multiple values (collection) deselected.

  5. Optional: Give your variable a default value or make the variable available for input (e.g. to include the flow on a Lightning record page).

Integrating the screen flow component

Once you have created the variable resources for the input, you can integrate the components in a screen.

This is how it works 

  1. Add the Screen element to the flow.

  2. Select the custom component d.velop archive in the selection list.

  3. Enter a label and a unique API name for the component.

  4. Use the variables you have already created for Record Id.

  5. Optional: Define the input value Run as Service-User. Use the value True if you want to prevent document uploads in this screen flow. If you leave the input value blank or use False, the upload area of the document list is displayed and works in the context of Record Id.

You can now use and expand the flow.