How do you fire Docusign in Salesforce using workflow or process builder. When a field (for example "send docusign") equals true, need a workflow that sends a docusign template to an email address on a custom object. Is there a formula I can use in Process Builder?
Related
I'm creating a custom salesforce URL button to launch Conga Composer which generates a document to send through Docusign.
The button is working great with the exception of the Opportunity Contact Roles getting mapped to the correct role i.e. Signer vs Carbon Copy. In the current form, all contacts listed in the contact roles translate to "Signers" in Docusign even though they have a Carbon Copy role in Salesforce.
The code below is formatted with Conga Composer requirements which are slightly different than Docusign's. This isn't the full code but the important pieces for the Contact Roles & Recipients. I currently have 2 contacts listed in SF's Opp Contact Roles - 1 is a signer & 1 is a Carbon Copy. They are both coming across as Signers. In the code below, I also have a person that needs to sign so they are hardcoded as "Signer 2"
/apex/APXTConga4__Conga_Composer
?serverUrl={!API.Partner_Server_URL_370}
&id={!Opportunity.Id}&id={!Opportunity.Id}
&DocuSignRelatedAccountId={!Opportunity.AccountId}
&TemplateId=a1234000004CYiDAAW
&DocuSignVisible=1
&DocuSignIgnoreOCR=0
&DocuSignSendReminders=1
&DocuSignRemindIn=3
&DocuSignRemindAgainIn=3
&DocuSignSendAsUserId=00580000003Jfs3AAC
&DocuSignBrandName=TestCompany
&DocuSignEndpoint=demo
&SelectTemplates=1
&FP0=1
&DocuSignR2Name=Steve+Tester
&DocuSignR2Email=steve#testing.com
&DocuSignR2Role=Signer+2
&DocuSignR2Type=Signer
&DocuSignR2RoutingOrder=2
Are you using a DocuSign template for this?
If you are then you should check the recipient type for each signer in the template is correct.
If the template isn't an issue then you may want to contact conga support for assistance in mapping roles to different signer types
I want to make employee task schedule chat bot : for example employee A go to company X at 4pm, employee B go to company Y at 2pm. Chat bot should send task and reminder to employees, and employee A can see his tasks and not employee B tasks and the same apply for employee B.
Can you suggest how to make this chat bot using Dialogflow, and may be how to implement employee login (using username and password ) using Dialogflow. Many Thanks!
Note that the main focus of Dialogflow is Natural Language Processing - Dialogflow is an NLU platform that makes it easy to design and integrate a conversational user interface into your mobile app, web application, device, bot, interactive voice response system, and so on.
If you want your chatbot to function as a task reminder that sends a message to its users based on a schedule, you’ll have to create your own implementation for it. On your custom backend, you’ll have to send a detectIntent request to your Dialogflow agent based on the user’s respective schedules.
You may check the respective documentation for ES detectIntent and CX detectIntent.
By default, Dialogflow is built in such a way that it will not provide a response unless it receives a user query from the end-user or an event from a client app first. However, based on your desired use case, the Dialogflow agent would have to initiate the conversation by sending a task reminder to the user.
To initiate a conversation with the user, you can try the following:
If you are using a custom integration, you may use a custom event to initiate a conversation with the user.
You can initiate a conversation by sending a detectIntent request to your agent to trigger a custom event. This lets your agent trigger a page with the custom event and send a response to the user without any user query or input.
To create a Custom Event is Dialogflow ES, you can follow the steps as described in the Configure an intent for events section of the Events documentation. You can then invoke the event via API by filling the queryInput.event field in your detectIntent request body.
To create a Custom Event in Dialogflow CX, you can follow the steps below:
Inside your flow, select the page you want to add a custom event to then click the "Event handlers". If the "Event handlers" is not visible, click the “Add route type” button to add the Event handlers.
Click on the + sign beside “event handlers” field and select any event.
Tick the check box beside “Use custom event”.
Add the name of the custom event you want to use.
Add the desired response under “Agent says”
Click save.
You can then invoke the event via API by filling the queryInput.event field in your detectIntent request body.
You can use Dialogflow ES’s Client Libraries and APIs or Dialogflow CX’s Client Libraries and APIs to create your own implementation/integration.
If you wish to use built-in text-based integration, you can also utilize the Dialogflow ES Messenger / Dialogflow CX Messenger integration.
You can utilize Dialogflow Messenger’s HTML “intent” attribute [ES/CX] to set an event to trigger the first intent when the chat dialog is opened.
Here’s an example of how to add the custom event name as value for the “intent” attribute of Dialogflow Messenger’s HTML embed code:
Dialogflow ES Messenger
Dialogflow CX Messenger
There are also JavaScript functions [ES/CX] available in which you may either choose from rendering a simple text message or a custom payload as an initial response to your end users. You may consider using the showMinChat [ES/CX] function to display a minimal version of the message list upon page reload.
You may check the respective documentations for ES Integrations and CX Integrations for more details.
Moreover, note that Dialogflow does not have a built-in user login feature - it is up to your chatbot’s front-end to require the user to login. One possible way to add a login feature to your chatbot is by creating a custom front-end for your chatbot that provides a login interface.
I have integrated Conga with Docusign in Salesforce. I ran the process of generating and sending the document to the user for signing. This has worked very well without using the background mode Conga parameter(&DS7=17) with docusign status updated in salesforce(with signed date and time) but, when I use background mode enabled, docusign status of that object(Contact or Opportunity) in salesforce doesn’t gets updated(no record gets added).I'm very much new to all these tools. Sorry, if i'm asking a silly question over here. Button url used:
https://composer.congamerge.com
?sessionId={!API.Session_ID}
&serverUrl={!API.Partner_Server_URL_290}
&id={!Contact.Id}
&TemplateId=a3X6F000000R4ue
&DocuSignVisible=1
&DocuSignR1ID={!Contact.Id}
&DocuSignR1Type=Signer
&DocuSignR1Role=Signer+1
&DocuSignEndpoint=demo
&DS7=17
Sign into DocuSign admin
Click connect
Click salesforce
Scroll to the connected objects section
Edit dsfs_DocuSign_status
Add a new field
If it is the Account object use the Account reference Id and map it to the Envelope External Source Id
Try that the rest of the settings are located there. It took me forever to figure it out too!
Here is my example of setting it up to the Order object
enter image description here
I am using Powerforms as an approach to get signatures using the DocuSign. What I want is to send some part of the data back to Salesforce from the PDF while the user signs it. I created custom fields on the PDF, related them to Salesforce, checked the writeback and allow sender to edit boxes but the data hasn't got back to SF yet. Any help?
When you send from Salesforce, there is information passed to document (such as the SourceID and Source Object Type), that DocuSign Connect will attempt to match to a record to process a request to push the data back into Salesforce.
If you are using a PowerForm, you would have to pass along similiar data and setup DocuSign Connect correctly for it to relate the data back to a Salesforce record.
This is something that is doable with customization, but not functional out of the box.
I have a problem that no one has been able to help with yet.
I have created a "Send Agreement" Account button in Salesforce that is linked to my default Docusign template ID using their DST command. This works, but what I need to do is to pull the signers (contacts) who need to sign the document based off of a custom field named, "Signing Role". The button should pull only those account contacts who have a signing role defined in their respective contact records.
Can anyone help?
Thanks in advance!!
Shaun
You can filter out the signers based on their Contact Role by using the custom button parameters CCRM and CCTM.
Say that you have several Contact Roles in an Opportunity, but you only want to pull out those contacts with role Business User. The partial script might look something like this:
// CCTM Maps Salesforce Role with a DocuSign TYPE (Signer, Carbon Copy, etc.)
// CCRM Maps Salesforce Role with a DocuSign ROLE (Signer 1, Signer 2, etc.). Usually used with DTS to call template
CCTM=’Business User~Signer’;
CCRM=’Business User~Signer 1’;
So the code above implies that the Business User will be Signer 1 and will act to sign the document. If he is using a custom field SigningRole created in Opportunity to determine the role, it might look look something like this:
CCTM=’{!Opportunity.SigningRole}~Signer’;
CCRM=’{!Opportunity.SigningRole}~Signer 1’;