I'm currently working on integrating docusign API into the backend. So far developers can generate an envelope through:
Documents list
Single template through templateId& templateRoles
Composite Templates (my current approach since it's versatile)
Once users are in either sending/signing view, they have to view all documents in one huge scroll and it's hard to tell which document they're viewing at the moment. In contrast, Documents List approach provides a better experience to separate each document and users can click on the "next" button to get to the next one.
Is it possible to change the behavior of Composite Templates envelopes the same as the ones using Document List?
Do you mean that the tab navigation button does not appear during signing if the envelope is created with the composite template? The composite template also provides a tab navigation button and you can navigate the page with it.
Yes, you can use "Smart Sections" to present the documents first "folded".
Live example 1
Live example 2
Related
I would like to know if it is possible to show/hide parts of DocuSign document template depending on the data which is passed in as a request.
I already have document template created and uploaded to DocuSign. I then use templateId to create envelope for that document and I also send some data (as json) to prepopulate certain fields inside the envelope.
The thing I am asking now is:
If the template has, let's say, 3 paragraphs, is it possible to hide one of them completely, based on the passed in json data?
Creating and uploading multiple templates is not an option due to large number of conditionally displayed sections.
I have been reading DocuSign API documentation, but couldn't find an answer to this.
To do that you will have to use Responsive Signing.
This feature change the format of the document you sign from PDF to HTML.
With HTML being the format, there are a lot more things you can do.
For example, you can use what we call "Smart Sections" which is exactly what you want. Sections that can be shown off/on based on logic you set.
Find out more about the responsive signing API here - https://developers.docusign.com/esign-rest-api/guides/responsive-signing/api-overview
Hoping someone can point me in the correct direction for an XPages application we are writing inside the Domino Client (Notes?) viewer.
I have a view of documents which is being returned, this view has categories on it, and shows fine as this in an XPage, we now apply a filter to the view to limit it to specific owners of the documents, but as soon as we apply the filter, the categories disappear, which means we are left with a long list of documewnts, but unsorted - is there any way to display a filtered view in a categorized manner, on an XPage.
Moving further down my list, I also need to be able to select these documents (and one or many owners) to send to an Lotus Agent which will then create a JSON document to be sent to our friends at DocuSign requesting signatures from the selected owners on the selected documents. I'm not sure what an Agent is yet, but that is the goal ...
Caveat: I'm not a Domino developer, so excuse me if some of the terminology is incorrect.
Categorised views are a very "Notes" construct. When you filter a view, it will only show documents, but not categories. While they are practical in the back, they are cumbersome in the UI.
There are a few design considerations how to tame them in a webUI. However if your users love them, you might consider to flatten them out and recreate the categories in the UI (client side) only.
The actual better way for your use case: add another view that is firstly categorised by the owner and secondly by your category. Use the category filter of the view control to limit the documents to that author. This should do the trick. Eventually use one of the controls from the extension library.
For the agent: don't bother, that's "old Notes speak". An agent would be a piece of code (LotusScript or Java, but since you do web interaction: Java) that gets triggered by an event: manual, on schedule, on document create/update (with some delay).
Since you are in an XPage, you have easier options at your disposal: create a Bean that has the JSON format you need, add a method that takes a Notes document as parameter to populate it, something like public void populate(final Document doc) {...} and use e.g. the GSON library to simply marshall them to JSON (or a collection of them). The GSON library probably is on a current Domino, I put it there as part of VoP 1.0.
Then use a managed bean to talk to Dokusign. When traveling down the managed bean road is is much easier to test than trying to mess with agents.
Hope that helps and ask more questions! (Check the Learning XPages Cheatsheet too)
I am trying to create envelope using templates. I have a unique use case where I would need to repeat one of the pages on the template based on the user input upfront before generating the docusign envelope to sign.
My template-1 has 12 pages with sign tab on 12th page. Based on user input I might have to include multiple page#4 and multiple pag#10 in between at the time of envelope creation. So my final docusign document for signature will be having pages 1,2,...4, 4a, 4b, 5, ........9, 10, 10a, 10b, 1oc, 11,12.
One suggestion I got was to use composite templates and have the pages added on the fly. But my question is, then wouldn't that require my template-1 to be broken down into multiple templates based off where new pages need to be inserted? Is there any other way I can achieve this, as I might end up having quite a bunch of split templates out of a single template.
Is it possible to add extra pages to the middle of the document on envelope created and ready to send from a set template.
Use case:
Using DocuSign UI, Template-Sample saved with 4 pages, signing tab at the end of 4th page
Using API on code, envelope is created with the Template-Sample
Add 1 or more pages (with data contents) after 3rd page on template
Send for signing.
Yes. While the envelope is in the Created status (draft), it is no problem to change the envelope's contents.
Changing a specific document within the envelope is only supported by changing the entire document. That's possible, but the easier way is to have a series of separate documents in the envelope, and then only insert the new document.
Eg, if you still want the signing page at the end of all the pages, you'd have three documents:
The front matter document
The document that you're changing on the fly
The final document, including the signature page
Doing this sort of document manipulation usually involves the use of composite templates. Please ask additional questions if you'd like more help.
So basically I am making a Jail Management System. The first part is where an inmate is booked and that session has 5 screens namely:
Booking Screen 1
Booking Screen 2
Booking Screen 3
Medical
Property
Commissary
I have created entities and forms for all of them. I want the functionality where i can move from the first booking screen to the rest by using like a "Next" button like we usually have in online forms over the internet. Can i achieve this?
or is there some way where I don't have to go to every entity and create a New record manually?
Regards
Depending on the number of fields you could use 5 tabs instead of pages. The last field of every tab could hold a javascript that opens the next tab and close the previous tab.
You can achieve this by creating a Dialog which will pass the values to Custom workflow activity(Written in c#). I have recently created a dialog for user registration.
Have a look at these link:
Link 2
Link 1
Link 3
Link 4
As Scorpion suggestion, you can use dialog if all of input fields were in the same entity. If you want to use the Wizard to collection fields which were held in different entities. Then you can make a custom web page(e.g. ASP.NET) to handle it.