Create and Store Submissions

Overview

When users complete long forms or multi-step processes, they may need to save their progress before submitting final data to Salesforce. This is useful when information must be reviewed, completed later, or checked before it is added to a Salesforce record.

Saving submissions also gives your team a way to manage captured data before it becomes part of your main Salesforce process.

Titan Solution

Titan lets you save submitted information as a draft or stored submission before sending it to Salesforce. You can review the captured content and decide when to save it to Salesforce.

By default, Titan stores submissions in Salesforce using the Titan-managed package submission object. This means you can save and review submissions without creating a custom Salesforce object for this purpose.

You can also use the Store Submission JSON option when you need to save submission data to a custom Salesforce object or an external storage location, such as Google Drive.

How to Guide

Storing a submission allows the administrator to choose what to save and when. The submission will be saved in your Salesforce under the Titan-managed package submission object. It will not affect other Salesforce data.

Note:

Prerequisites:

Gear icon > Project Settings > Tools > Custom Variables

• Create a custom static variable for this option that will be used in the Submission ID field, for instance, called “submissionid.”
• Create a custom static variable in the JSON file to be sent to Salesforce if you want to use that functionality.
• Create a custom system variable. Select the option called “Project ID.” The project ID is used for added security.

The Submission ID and Project ID parameters will be used when loading a submission.

In this example, we have a form that a customer can complete, and a Submission button that will save the form to a draft.

1. Configure the On Click Action on the button. The On Click Action screen opens.

2. Click the + icon to add a node. The Add Node screen opens.

3. Select the Submissions option and click the Next button. The Add Node/Submissions screen opens.

4. Select the Store radio button.
5. Select the Create radio button.
6. Use the What would you like to store? drop-down arrow to open the list. The options are as follows:
   • On Page
   • From Strip
   • Field
   • Field Group
7. Click an option to select it. The screen changes as follows:

In this example, On Page will be used:

1. Select the On Page option. The parameters for On Page are shown on the right side of the screen.
2. Enter a parameter name in the text field. This is the name under which the information will be saved in the submission. When loading the fields, you must state which parameters to load and reference this name.
3. If necessary, click the Skip Empty Values checkbox. Empty values will not be added to the submission.
4. Click the Next button.

5. Use the drop-down list to select the location to store the submission ID. The submission ID is the variable you need when loading the submission. It will not load if this variable is incorrect.
6. Additionally, use the drop-down list to select the location to store the submission JSON.
   • The data from the submission is saved to a JSON file that can be saved to Salesforce.
   • It is saved to a variable and can be pushed to any file, for instance, Accounts.
   • Use this if you don’t want to save the file to the Titan object in Salesforce but rather to a custom object.
   • You can save it externally, for instance, to Google Drive.
   • Add the Salesforce action after the Submissions action on the On Click Action screen to push the file to Salesforce or the external file location.

Note:

If you do not enter a unique name, the field ID of the element will be used.

7. Add a tag if necessary.
8. Click the Insert button. The Submissions Node is added to the On Click Action screen.
9. Click the Apply button.

View the created submission

You can see whether the submission was successful:

1. Browse to the Project Settings and select the Salesforce option.
2. Select the Integration Logs option and then click the ContentVersion (create) – Record ID link.

The JSON file opens via Salesforce, for instance: