Building some code for CreateEnvelopeRequest (package)
Wednesday, March 20, 2024 at 06:14pmIn my code I have 2 parameters that I am passing string uniqueId, string coBrand can you elaborate on this comments?
Co-Branding: To apply co-branding, you would typically configure these settings directly in your OneSpan Sign account settings, ensuring that every package created inherits the branding configurations without the need to specify them for each transaction.
Handling Unique Identifiers: For tracking or linking purposes, consider using the ExternalId property or similar features provided by the SDK to associate your own identifiers with OneSpan Sign packages.
Reply to: Building some code for CreateEnvelopeRequest (package)
Thursday, March 21, 2024 at 08:10amHi Alfredo,
As per your description:
Co-Branding: You can only specify one logo and color branding per each account. You can do it in your sender UI portal, check this guide more details.
Handling Unique Identifiers: Is this Unique Identifier a reference ID from the other platform (e.g. order ID, opportunity ID, deal ID)? Or do you mean the transaction ID of each package/envelope?
Duo
Reply to: Building some code for CreateEnvelopeRequest (package)
Thursday, March 21, 2024 at 11:07amThanks a lot for your help. The uniqueId is an internal JobId and I just found out that we have a SQL DB where we keep all the variables for the CoBranding, APIKeys,, BaseURL etc. I will keep this ticket open in case I have more questions.
Reply to: Building some code for CreateEnvelopeRequest (package)
Thursday, March 21, 2024 at 11:19amIf you want to store an internal Job ID as part of the package JSON, put it under the custom data section - follow this guide.
Duo