Using Conventions: Field Mappings

A Field Mapping is an object that enables the following features:

• Insert: This feature copies a value of a Salesforce field (e.g., Street Address) into a corresponding field of a OneSpan Sign document when a transaction is being prepared. That data can then be retrieved from the signed document. The data in question can be either data about a recipient, or data about a Salesforce related object.

  The relevant OneSpan Sign field must exist before you can insert a Salesforce value into it. You can create the required OneSpan Sign field by using a Text Tag.

• Writeback: This feature copies a value of a OneSpan Sign field (e.g., Street Address) into a corresponding Salesforce field. Using it, data entered by recipients during the Signer Experience can be written back into Salesforce fields, based on Field Mappings defined when the transaction is completed.

  The Writeback feature is disabled by default. The Writeback feature cannot operate unless the Insert option is enabled.

The rest of this section describes:

• Inserting Salesforce Recipient Data into OneSpan Sign Fields

• Inserting Salesforce Related-Object Data into OneSpan Sign Fields

• Updating Salesforce Fields with OneSpan Sign Data (Writeback)

Inserting Salesforce Recipient Data into OneSpan Sign Fields

The following procedure illustrates how to insert into OneSpan Sign documents Salesforce data from a recipient's record (e.g., data about a Salesforce user, contact, or lead).

In particular, it describes how to insert into a OneSpan Sign transaction the address of a Salesforce contact who is also a recipient.

To insert a Salesforce contact’s address into a OneSpan Sign transaction:

Creating a Convention

1. Click the Conventions tab.

2. Click New.

3. Enter a name for the new Convention, and click Save.

Creating a Field Mapping

4. On the Field Mapping related list, click New Field Mapping, and give a name to the mapping.

5. In the Mapping Type drop-down list, select Recipient.

6. In the OneSpan Sign Document Field Reference section, give the OneSpan Sign field name.

7. In the Salesforce Object Field Reference section, click Add new.

8. Choose the desired object. In this case, the object is Contact. A list of the contact’s fields appears on the right.

9. Choose the field to be mapped to a OneSpan Sign field (e.g., the contact's City), and then click Add.

   Ensure that the Insert option is checked when the field is added. This will enable the system to insert data from the Salesforce object’s field into the OneSpan Sign documents. If you are using custom fields, the fields that you create must be accessible (for insert), and editable (for writeback). As such, ensure that your users have the proper access as needed.

10. Click Save to save the Field Mapping.

11. Repeat Steps 4-10 to create a new Field Mapping for each address field (City, Zip Code, etc.).

Creating a Transaction and Inserting Salesforce Data into It

12. Create a OneSpan Sign transaction (giving it a name), and then click the Advanced Options tab.

13. On the OneSpan Sign Convention section, click Lookup and choose the Convention created above.

14. Click the Details tab.

15. Add documents to the transaction, and add the contact as a recipient.

16. Click Prepare. The Designer appears in a dialog box.

17. Add a Signature Block for the contact.

18. To display more options, click the gear icon on the right side of the Signature Block. Then click the + sign to add fields. The list of available fields appears.

19. Click text field to add a text field.

20. To display more options, click the gear icon on the right side of the text field. Then click Settings to see the field settings.

21. Give a name to the Convention Field Names, which are displayed on the left side of the Designer. Then click Save.

22. Repeat Steps 19-22 for each of the Convention's fields.

23. When finished, close the overlay and click Send.

    The transaction will be sent. When the transaction is complete, its signed documents should contain the contact's address. Thanks to this procedure, that address in OneSpan Sign documents will have been inserted directly from Salesforce.

Inserting Salesforce Related-Object Data into OneSpan Sign Fields

The following procedure illustrates how to insert into OneSpan Sign documents Salesforce data from a record linked to a OneSpan Sign transaction object.

In particular, it describes how to insert an address from an Account record into a OneSpan Sign transaction .

To insert a Salesforce Account’s address into a OneSpan Sign transaction:

Creating a Convention

1. Click the Conventions tab.

2. Click New.

3. Enter a name for the new Convention, and then click Save.

Creating a Field Mapping

1. On the Field Mapping related list, click New Field Mapping, and give a name to the mapping.

2. In the Mapping Type drop-down list, select Related object.

3. In the OneSpan Sign document field reference section, give the OneSpan Sign field name.

4. In the Salesforce Object Field Reference section, click Add New.

5. Choose the desired object. In this case, the object is Account. A list of the Account’s fields appears to the right.

6. Choose the field to be mapped (e.g., the Account's City).

   

7. Click Add Field Reference.

8. Ensure that the Insert option is checked when the field is added. This will enable the system to insert data from the Salesforce object’s field into the OneSpan Sign documents. If you are using custom fields, the fields that you create must be accessible (for insert), and editable (for writeback). As such, ensure that your users have the proper access as needed.

9. Click Save to save the Field Mapping.

10. Repeat Steps 4-10 to create a new Field Mapping for each address field (City, Zip Code, etc.).

Creating a Transaction and Inserting Salesforce Data into It

12. Create a OneSpan Sign transaction (giving it a name), and click the Advanced Options tab.

13. On the Conventions field, click Lookup and choose the Convention created above.

14. Click the Details tab.

15. From the Related object type drop-down menu, choose Account (if it is not already selected).

16. Click Lookup to choose the Account record.

17. Add documents to the transaction, and add recipients to the transaction.

18. Click Prepare. The Designer page appears. Add your Signature Blocks.

19. To display more options, click the gear icon on the right side of the Signature Block. Then click the + sign to add fields.

20. Click Settings to see the field settings. The list of available fields appears.

21. Click Text Field to add a text field.

22. To display more options, click the gear icon on the right side of the text field.

23. Type the name of the desired Convention field name. These field names are displayed on the left side of the overlay. Then click Save.

24. Repeat Steps 19-23 for each Convention field.

25. Close the Designer. Then click Send to send the transaction. When the transaction is complete, its signed documents should contain the Account's address. With this procedure, the address will be inserted into OneSpan Sign documents directly from Salesforce.

Updating Salesforce Fields with OneSpan Sign Data (Writeback)

A Field Mapping's Writeback feature can update data in Salesforce fields from OneSpan Sign documents.

For example, suppose that: (1) a recipient notices during the Signer Experience that his address is wrong in a OneSpan Sign transaction document; (2) the recipient corrects his address in that document.

If that OneSpan Sign address is mapped to a field of a Salesforce related object, and the Writeback option has been checked for that mapping, when the OneSpan Sign transaction is complete, the updated address will be written into the Salesforce field.

The data to be written back into Salesforce must be entered during the Signer Experience.

To update a Salesforce field with data from a OneSpan Sign document when the associated transaction is completed:

1. Select the Writeback option for the associated Field Mapping.

2. When the OneSpan Sign transaction is complete, verify that the data updated during the Signer Experience appears in the associated Salesforce field.