I'm fairly new to using Docusign (I have just created an account). I'm curious if the following functionality exists.
I currently have an existing system that generates PDFs, but currently when the PDFs are generated for signing they are sent to an external vendor website/portal to have the docusign elements dealt with.
Each PDF that is generated by the system contains different information,so using templates via Docusign won't work.
I'm attempting to take a flat PDF file, and insert Docusign elements to be completed at a later time. Is this something that Docusign can do, or how should I go about approaching this?
Yes it is possible "to take a flat PDF file, and insert Docusign elements to be completed at a later time."
How should I go about approaching this?
See the Rest API Recipe here for requesting a Signature using Docusign
This recipe allows you to supply a PDF document(or multiple documents) and supply Tabs based on your requirements.
The Docusign developer Center is a great place to start
C# SDK:
There is also a useful C# SDK to integrate DocuSign into your app.
Related
I'm trying to understand the difference between the SP add-ins and SP Framework.
I need to refactor a Django app on SP online. The web app does the following:
Takes input from the user into a form (mostly y/n) questions
based on the responses generates a pdf document which is returned to the user plus a .docx document which is stored on SP (the end user has no access to the .docx)
Potentially sends an email to notify other stakeholders
Now, if I have to implement it on SP, I understand that the full logic will be in the client, while at the moment for example part of the logic runs in Python.
The form itself should not be an issue. I was wondering how to generate the pdf and the docx. Is that possible using SP workflows? Or should I use Power Automate? I mean, how to properly populate a HTML/word template and then convert it to Pdf if we have no access to server side code? Thanks
You can create a SharePoint Application using spfx framework https://learn.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview and the client side code can call server side APIs. You could use any backend to take the Form submission and return a generated PDF file.
Please find below my thoughts:
-UI and backend base logic(capturing form data) you can do with SpFx.
PDF Generation: There are few client side js scripts(e.g., jspdf)
available to generate a pdf. This can be done from SpFx. We did generated this one of the project but it was console app using csom.(but we used js files for pdf generation)
Word file generation: Power Automate can be handy here, which uses a
premium connector to convert. You might need to rely on onedrive for that.
Or
Azure Function: you can write Azure Function for the conversion
logic(pdf/docx)
API: as astanley86 said, you can create the API (takes care of conversion) and call it from spfx
SpFx is the modern development approach which is recommended by MS. SP Add-in has few cons which you can easily find from knowledge base.
I sent a PDF to Docusign (using the API).
Some of the form fields are not rendered and are invisible in Docusign.
They show up completely fine on Chrome, pdfjs, Okular (Linux), Adobe PDF and Master PDF Editor.
This screencast shows the issue:
In docusign no field value is rendered.
I download the same PDF and open it in Okular (Linux, Poppler based PDF viewer) and the values are there.
I also open it up in Chrome and the values are there.
Please note that:
It happens to a specific PDF. We have a lot of PDF's that are working just fine.
The PDF is displayed properly using many different PDF software including pdfjs
DocuSign flattens / rasterizes incoming PDF documents to eliminate the security threats otherwise inherent in the PDF language.
PDF Form fields can be automatically converted to DocuSign fields (tabs). This can be done either while uploading a PDF using the DocuSign webtool or while uploading via the API.
If you have a specific PDF that doesn't render properly, you can contact DocuSign customer service for additional help.
If you want to maintain all of the PDF's features (not flatten it) you can use the DocuSign Signature Appliance to sign the PDF.
I am trying to create a solution in SharePoint 365 (I am new in SharePoint). Below is what I am looking for:
1. A user logs in and opens a form which they fill details and forwards/submits to the supervisor for approval. There are about 20 fields to be filled
2. Once approved, a certificate, preferably in PDF, is generated based on the details entered by the user.
3. The 20 fields are made available for download in Excel whereby the 20 rows form 20 columns in the Excel.
I am not sure if SharePoint with designer or Infopath can accomplish this.
Hope you can assist me to know if this is possible and what extra tools I may need on top of SharePoint.
Your questions is very generic, it might be flagged by some moderator later. Anyway... for SharePoint Online (not SharePoint 365), you will need to write your solution using the SharePoint Framework (SPFx), to achieve this you will need to familiarize yourself with TypeScript, NPM, GULP, Yeoman Generator, React JS, and a to some degree of JavaScript.
The other possible way is to familiarize yourself with the Office 365 architecture, this options might be limited to fully achieve your goals but might be the best option if you are not a developer.
Basically you will need to create a "workflow", you can create using Flow (when a list item is submitted), inside the Flow you will read the fields submitted and send for user manager's approval (reading the property from user profile), and once the "workflow" is approved, you can capture the data, and send to Excel (you can even specify to which Excel flavor you want: Excel Online - Business, Excel Online - OneDrive, or simply Excel).
Once your Flow adds the information your target (Excel file), you add a new step in your Flow to use the "Adobe Sign" to use the create a certificate - you can use this step to get a document from an signed agreement or any other you find suitable there
You have the hard way by coding through SPFx or making your way through Flow (the easy way), it is now up to you, go with Flow, you will achieve this in probably a couple of hours.
After initial browsing in Google, I couldn't work out the scope of DocuSign API.
I would like to know if it's feasible to implement these features
Multiple templates with custom form fields
Assign workflow to templates - multi-user e-signing by stages?
automate e-signing internally
User management/privileges - to create new document, recall/cancel, etc
Manage List of recipients - type association
Reporting such as; number of documents signed in the last month,
Please briefly explain what is DocuSign capable of and what needs to be developed differently
Thanks in advance
The general answer to your question is "yes." The DocuSign website, Developer Center, and Signature API reference documentation can help you understand the DocuSign Signature product and APIs.
If you have additional questions, you can talk with DocuSign staff, or try it for yourself. The Developer center enables you to create a free developer sandbox.
For API issues, you can also ask questions here on StackOverflow. Note that your questions should be much more specific than the questions you listed above. You also should show what you have already tried and what is not working for you.
Just downloaded the docusign app for Sharepoint online. It's on an HR publishing site and the page is for all new hire documentation. I want to put a button on the page to associate with the specific document that needs to be signed. I don't want users to have to go into the library and use the docusign tab. Is there a way to do this?
I can't quite see how this will work.
The ribbon command will have some code behind it. Presumably it uses the Docusign API so if you can find the code, you will be able to see what to do. Or review the API docs.
On your page, you would need to trigger the same code on each icon but I assume that the icon already triggers an action (e.g. downloading the file or something), so you would likely need a second icon or link to trigger the docusign action instead.
Not trivial. And I couldn't find another similar issue on Google.