The Bundle comes with the set-up included for following record types:
Customer
Vendor
Contact
Transaction
If you will use the solution for other record types please follow guide below.
When setting up the new E-Signature Field, make dure to click in Record is Parent and to choose the E-Signature Subtab. This way you will be able to see all connected E-Signature directa via the base record, in this case the contact card.
Add the field to the form and adjust ots placement, all entitiy fields should be added to the "General" Field Group.
Open the SC ESign UE script via Customization -> Scripting -> Script -> Filter for Bundle: -> click view on Script "customscript_sc_esign_ue".
Click on Edit and then click on the Deployment Subtab. Choose the record type you want this deployment for, click OK and Save.
After saving the Script record, navigate back to the deployment subtab and open the deployment record you have just created, click Edit.
Within the main field change the status to Released, if this deployment is specific for a role yo can set a role otherwise you can leave the setting as is.
Under the audience tab you have the possibility to choose who is allowed to deploy the script for the record type of your choosing.
As a next step you need to define the parameters, this defines which values will be transferred to the E-Sign record when clicking on the button.
Array of field values that will be transferred from fields on the record to which this script is being deployed, to corresponding fields in the E-Signature record.
Paramater value is a Json object with value pair.
The left hand value of each pair is the source field id in the "deployed to" record. ("id" would always be the id of the "deployed to"-record itself).
The right hand value of each pair is the target field id in the E-Signature record.
This is an example of a paramater value where three fields are transferred to the E-Signature button:
{
"entity": "custrecord_sces_customer",
"custbody_scpa_pdf_document_url": "custrecord_sces_pdf",
"id": "custrecord_sces_transaction"
}
For example the contact deployment:
{ "entityid": "custrecord_sces_customer"}
Double check the field ID on the record you are creating the deployment for, in this way you avoid unexpected script error.
On the parameter subtab you need to enter your WorkspaceID which is the Oneflow account number. You can find this in the browser link when opening your OneFlow account.
After the Set up is completed, you should be able to open a record of your choosing, in this example the contact Anders Larsson, on the record you should see the button E-Signature.
When you click on the button a E-Signatur record i opened and the contact is already filled in correctly. See screenshot below.