Text Review Widget Drafts

Business Background

The text review widget simplifies version control and text revisions, saving time and reducing errors by clearly showing what’s changed between the two versions. Users can quickly view, accept, or revert edits, ensuring that only approved changes are incorporated before in-line editing begins. This streamlined approach keeps teams aligned on the most current content, enabling efficient decision-making and better collaboration. Ultimately, it enhances productivity, improves content accuracy, and supports agile workflows, making it a powerful tool for businesses, prioritizing precision and efficiency in document management.

Titan Solution

Use the text review widget to save drafts to Titan Submissions. This option is useful if you have a long text to review. You will not lose any changes that you have already made. You can also use it to save your progress if you’ve made some changes and need input from others on the remaining edits.

How to Guide

Note:

The Debug Mode is enabled for this example.

Project settings > Tools > Debug Mode.

Note:

Prerequisites:

1. Configure the text review widget with data from one of the following sources:

• Salesforce
• Affected Elements

2. Add static variables, for instance:

Firstly, you must store the draft in Salesforce, and then you can load it to the webpage.

Store the Draft in Salesforce

1. Add a button element to the canvas and click the On-Click Action icon.

2. Click the + icon next to the Start node to open the Add Node screen.
3. On the System action tab, click the Submissions option and then click the Next button.

4. Click the Store radio button. The Create radio button is selected by default.
5. Use the drop-down list to select Field as the option to store.
6. Use the drop-down list to select the Text Review/Draft field and click the Next button.

7. 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.
8. 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.
9. Change the tag field if necessary and click the Insert button. The Submission node is added to the On Click Action screen.

10. Click the + icon next to the Submissions node to open the Add Node screen.

11. Click the Salesforce Action option and then click the Next button.

12. Click the Salesforce Integration button.

13. Select the Push option and click the Create New button.

14. Use the drop-down lists to select the object in Salesforce and the action. In this example, the following are used:
    • Contact
    • Update

15. Under Condition, configure a condition. In this example, a specific contact is referenced.

16. Use the drop-down list to map the element (in this case, the submission variable) to the Salesforce field (in this case, a newly created “Short description” field on the Contact object).

17. Click the Apply button. The Salesforce action is added.

18. Use the drop-down list to select the integration action and click the Next button.

19. If necessary, change the tag and click the Insert button. The Salesforce Action node is added to the On Click Action screen.
20. Click the Apply button.

Load the Draft from Salesforce

1. Remember to Save the project.
2. Add a button element to the canvas and click the On Click Action icon.

3. Click the + icon next to the Start node to open the Add Node screen.
4. Click the Salesforce Action option and then click the Next button.

5. Click the Salesforce Integration button.

6. Click the Create New button.

7. Use the drop-down lists to select the object in Salesforce and the trigger to execute the pull. In this example, the following are used:
   • Contact
   • User interaction

8. Under Condition, configure a condition. In this example, a specific contact is referenced.

9. Use the drop-down list to map the element (in this case, the submission variable) to the Salesforce field (in this case, the “Short description” field on the Contact object).
   • These must be the same values as you mapped for the Submission Store Salesforce action.
10. Click the Apply button. The Salesforce action is added.

11. Click the Close button on the Salesforce Integration screen.

12. Use the drop-down list to select the integration action and click the Next button.

13. If necessary, change the tag and click the Insert button. The Salesforce Action node is added to the On Click Action screen.
14. Click the + icon next to the After Finish option on the Salesforce Action node to open the Add Node screen.

15. On the System action tab, click the Submissions option and then click the Next button.

16. Select the Load radio button.
17. Use the drop-down lists to select the Field option and then the Submission ID variable you used in the Store action.
18. Use the drop-down list to select the current project as the project ID.
19. Use the What would you like to load? drop-down to select the Field option and then select the Text Review/Draft field to store.
20. Click the Next button.

21. If necessary, change the tag and click the Insert button. The Salesforce Action node is added to the On Click Action screen.
22. Click the Apply button.

23. Save and Preview the project.
24. Click the Compare Salesforce Content button. The changed text is displayed in the text review widget.

25. Accept or revert some changes and click the Save Draft button. The draft is saved to Submissions.

26. Refresh the webpage and click the Load Draft button. The draft is displayed in the text review widget.