- Set up the Data Destination
- Destination Response Output
- Testing and Troubleshooting
The Salesforce Document Data Destination creates documents in Salesforce when mobile forms are submitted. Account and contact information are completed based on answers provided in forms. Combine with other Salesforce data destinations to perform other actions (like creating a case) with the data from a single form submission.
Note: ProntoForms currently supports Salesforce API version 24 for this data destination.
|Organizations of all sizes use the Salesforce platform to manage customer relationships and power their business in the cloud. Looking for two-way integration? Read more about the ways ProntoForms can connect to Salesforce.|
Create the data destination, selecting Salesforce Document Data Destination as the type.
- Name the destination.
- Select "auto-link" to link any forms you create in the future.
- Manually link existing forms to the destination.
- Optionally set up filter rules. The data destination will only create/update a record when these conditions are met.
- Connect the destination to Salesforce. Use an existing connection, or set up a new Salesforce Connection.
4. Document Fields
Provide values for the standard document fields. Use Data Record Expression Language (DREL) to reference data in form submissions.
"The Document is Public" and "This Document to be used internally":
- Will only accept the values "true" or "false". Values must be in lowercase.
- If using DREL to fill these fields, use a radiobutton, drop down, or Yes/No control type to avoid user errors in data entry.
- The Yes/No control type returns "true" and "false" as answers.
- Keywords: Separate with a comma.
Send data to the object's custom fields. Note: The Geolocation custom field is currently not supported.
- Salesforce API Name: Enter the API name of the custom field (found through the "Describe Salesforce Object" button).
- Value Expression: Use Data Record Expression Language (DREL) to reference data in form submissions.
5. Document Component
NOTE: In order to choose which document to send, attach the document to this data destination in the Form Builder. Read here for more about attaching documents and destinations to forms.
This specifies the path or directory to transfer the completed form data to. This can be a static destination (I.e. for a folder named “Expenses” enter “Expenses”), or it can be dynamically derived from the submitted data through Data Record Expression Language. For example, entering “%a[Unique ID]” will use the answer to the specified question as the folder title; this is often used to organize data into folders based on customer name. Read more about unique IDs here.
- If the folder expression is left blank: all documents will be saved to the personal documents folder of the Salesforce user whose credentials were used to establish the Salesforce Connection.
- If the folder specified does not exist: a new folder will be created. Note: When creating a new documents folder through the data destination, the folder name must begin with an alphanumeric character, not end with an underscore, and not contain two consecutive underscores.
- If the folder specified already exists: documents will be published to this folder. Type the folder name exactly as it appears in Salesforce -- spaces are allowed. The Salesforce user used to establish the connection must have read/write level access to this folder.
Destination Response Output
Destination response outputs allow users to make sequential requests to other systems, typically to create parent-child relationships in the data or objects you are creating in those systems. For example, a user might want to create an object in a first destination, and have destination response outputs pass the ID for that object to the next destination to add an appropriate attachment to it.
Click here for more information: Destination Response Output
Test all data destinations before using them in production. This is key to ensuring that ProntoForms data is received. Please read the recommendations for testing and troubleshooting data destinations.