I am working on cpq,and my requirement is to use quote fields in one span document so please help me to get it.
September 28Created
September 28Last Updated
a year agoLast Reply
5Replies
51Views
2Users
0Likes
0Links
Duo_Liang | Posts: 3776
Reply to: Getting Issue with merging fields on document
Thursday, September 28, 2023 at 10:09am
0
votes
Hi Pradip,
Thanks for your post!
Have you got the chance to try the sample Apex code I provided in this previous post? Generally speaking, you would read quote fields via SOQL and create Label Fields with its value to merge the fields.
can you please provide detailed guide,how that code can be execuited in salesforce, and where that will be mapped in template on in transaction beacuse my requirement is i am automating all process providing document directly from salesforce and creating transaction.
Reply to: Getting Issue with merging fields on document
Saturday, October 7, 2023 at 12:26pm
0
votes
We are using button and passing data to parameter that you are provided /apex/esl__package?ParentId={!Account.Id}&Name={!Account.Name}%20Agreement&TemplateID=a0G360000018BdREAU
is there any other way to create transaction via apex or any else.
Also also we found apex SDK on OneSpan documentation if we are not getting that how we can use it if you can provide detail steps to create transaction via apex SDK its helpful for us
Reply to: Getting Issue with merging fields on document
Monday, October 9, 2023 at 09:30am
0
votes
Hi Pradip,
Thanks for the info!
Although I haven't had the chance to attempt the OSS for the Salesforce CPQ connector, this custom button link looks familiar to me. If you are looking for a way to merge Salesforce data into a field, try to follow this guide and add a convention which consists of two parts - Recipient Label and Field Mapping:
By adding Recipient Label to each signer which consists of a list of text tags, it defines the fields' names and locations. From what you described, use label field or text fields.
Then, add Field mapping to link the field name to their corrsponding Salesforce data, guide here.
Finally, this guide covers all the available custom button parameters. In particular, search for "ConventionID" and "SignerXLabel" for more information about how to specify convention and signer label via the custom button/link.
Reply to: Getting Issue with merging fields on document
Thursday, September 28, 2023 at 10:09amHi Pradip,
Thanks for your post!
Have you got the chance to try the sample Apex code I provided in this previous post? Generally speaking, you would read quote fields via SOQL and create Label Fields with its value to merge the fields.
Duo
Reply to: Getting Issue with merging fields on document
Thursday, September 28, 2023 at 11:20pmThank you Duo_Liang
can you please provide detailed guide,how that code can be execuited in salesforce, and where that will be mapped in template on in transaction beacuse my requirement is i am automating all process providing document directly from salesforce and creating transaction.
Reply to: Getting Issue with merging fields on document
Friday, September 29, 2023 at 07:08amHi Pradip,
Are you using OneSpan Sign for Salesforce CPQ connector? Or are you doing your own integration via Apex code?
Duo
Reply to: Getting Issue with merging fields on document
Saturday, October 7, 2023 at 12:26pmWe are using button and passing data to parameter that you are provided /apex/esl__package?ParentId={!Account.Id}&Name={!Account.Name}%20Agreement&TemplateID=a0G360000018BdREAU
is there any other way to create transaction via apex or any else.
Also also we found apex SDK on OneSpan documentation if we are not getting that how we can use it if you can provide detail steps to create transaction via apex SDK its helpful for us
Reply to: Getting Issue with merging fields on document
Monday, October 9, 2023 at 09:30amHi Pradip,
Thanks for the info!
Although I haven't had the chance to attempt the OSS for the Salesforce CPQ connector, this custom button link looks familiar to me. If you are looking for a way to merge Salesforce data into a field, try to follow this guide and add a convention which consists of two parts - Recipient Label and Field Mapping:
By adding Recipient Label to each signer which consists of a list of text tags, it defines the fields' names and locations. From what you described, use label field or text fields.
Then, add Field mapping to link the field name to their corrsponding Salesforce data, guide here.
Finally, this guide covers all the available custom button parameters. In particular, search for "ConventionID" and "SignerXLabel" for more information about how to specify convention and signer label via the custom button/link.
Duo