function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Manny OmideyiManny Omideyi 

Lightning Component unable to populate Docusign form

Hi,

I have a button in Lightning that calls a Docusign URL and populates the resulting form. We need to be able to hide and expose the button as required, but as it is not possible to create a validation rule on a button, I have instead built a Lightning Component. 
  
<aura:component implements="force:lightningQuickAction,flexipage:availableForAllPageTypes" >
	<ui:button label="Open in New window" press="{!c.openActionWindow}"/>
</aura:component>


Controller:

({
	openActionWindow : function(component, event, helper) {
		 window.open("https://uatna11.springcm.com/atlas/doclauncher/OneClickDocGen?aid=17166&config=Docusign configuration&eos[0].Id={!Opportunity.Id}&eos[0].System=Salesforce&eos[0].Type=Opportunity&eos[0].Name={!Opportunity.Name}&eos[0].ScmPath=/Salesforce/Account/{!Account.Name}/Opportunity");
	}
})

The problem I have is that, although the component is able to call the URL, it is then not able to populate the form, and returns the following error

User-added imageThe response from Salesforce Dev Support is that, given the way the URL was provided by Docusign, it uses references to the Opportunity ID and Account ID within the link, which would resolve when used with a standard button, but would not resolve without proper handling within the Javascript button. A custom Javascript button would therefore need to handle retrieving this data.

Would anyone be able to help out with this, and owuld the code be easy to maintain going forward?
RSuzukiRSuzuki
The issue I believe are the merge tags you are using "{!Opportunity.Id}", "{!Opportunity.Name}" etc. 
You'll have to add an implements="force:hasRecordId" and actually load the context record using LDS. 

For example: 
<aura:component implements="flexipage:availableForRecordHome,force:hasRecordId" >
   <aura:attribute name="record" type="Object"
                    description="The record"/>
    <aura:attribute name="OptyRecord" type="Object"
                    description="Simple Record of object"/>
    <aura:attribute name="recordError" type="String"
                    description="Error msg bound to force:recordData"/>

    <force:recordData aura:id="record"
                      layoutType="FULL"
                      recordId="{!v.recordId}"
                      targetError="{!v.recordError}"
                      targetRecord="{!v.record}"
                      targetFields="{!v.OptyRecord }"
                      mode="VIEW"
                      fields="Account__r.Name"
/>

	<ui:button label="Open in New window" press="{!c.openActionWindow}"/>
</aura:component>


Controller:

({
	openActionWindow : function(component, event, helper) {

		 var Opty = component.get('v.OptyRecord');
window.open("https://uatna11.springcm.com/atlas/doclauncher/OneClickDocGen?aid=17166&config=Docusign configuration&eos[0].Id="+Opty.Id+"&eos[0].System=Salesforce&eos[0].Type=Opportunity&eos[0].Name="+Opty.Name+"&eos[0].ScmPath=/Salesforce/Account/"+Opty.Account__r.Name+"/Opportunity");

	}
})


 
Manny OmideyiManny Omideyi
Hi @RSuzuki, thanks for responding. I'm not a coder at all, so I'm a bit lost with what you've done. I copy/pasted, but the button now just doesn't generate anything. I'm guessing I need to modify the code somehow, but I'm not sure where to start. Can you please advise?
RSuzukiRSuzuki
Taking a look at your issue further, could this documentation be a solution? 
https://support.docusign.com/en/articles/DFS-URL-buttons-for-Lightning-basic-setup-limitations