Create and Store Submissions

Business Background

Store information as a draft or review the contents before saving it to Salesforce.

Titan Solution

Titan lets you temporarily save information as a draft. You can review the content before saving it to Salesforce. The submission will be saved in your Salesforce under the Titan-managed package submission object and will not require any customization from the organization’s side. All these are pre-built in the product and the application.

Use the Store Submission JSON option to save the file to a custom object in Salesforce, or an external location, for instance, Google Drive.

How to Video

Coming soon!

How to Guide

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

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:

Option	Screen
On Page
From Strip	Use the Strip Element drop-down to select a stip.
Field	Use the Fields to Store drop-down to select a field. You can only select one field.
Field Group	Use the Fields to Store drop-down to select fields. You can select multiple fields.

In this example, On Page will be used:

1. Select the On Page option. The parameters for On Page are shown on the right of the screen.
2. Enter a parameter name in the text field. This is the name that the information will be saved under 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 needed when you load the submission. It will not be able to load if this variable is not correct.
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: