while cloning is it possible to clone only the documents and roles need from the template
Thursday, February 27, 2020 at 10:36amIn our scenario we have all the documents created in a temple and user will select some documents from the template in our application to esign or manually sign.
Each time when we create a package/transaction, we are cloning the template and deleting the roles and documents as suggested .
But its seems very difficult and overhead when the number of documents in a template is high .
So it is possible to clone only the documents and roles we need from the template in your future versions at least which will help us a lot .
Reply to: while cloning is it possible to clone only the documents and roles need from the template
Friday, February 28, 2020 at 09:25amAny updates ??
Reply to: while cloning is it possible to clone only the documents and roles need from the template
Friday, June 5, 2020 at 10:06amHi nareshishere,
"Not being able to create package with partial documents out of the template " has been fixed in 11.34 version, which has been deployed to most of the environments. (refer to the trust center for the release date)
Duo
Reply to: while cloning is it possible to clone only the documents and roles need from the template
Tuesday, August 10, 2021 at 05:12amHi Duo,
I'm interested in this creating packages with a partial selection of documents and also signers from the template.
Can you provide a link for documentation on this subject.
Thanks, Mónica
Reply to: Hi Duo, I'm interested in…
Tuesday, August 10, 2021 at 08:48amHi Mónica,
Thanks for the post! Assuming you have a template with 2 placeholder signers and 3 documents and now you only want to create a package out of it with 1 signer and 2 documents, you'd perform a two-steps approach, see below:
Step1: Invoke a clone call with payload similar to below:
POST /api/packages/{templateId}/clone
{
"roles": [
{
"id": "408d9509-bbe5-4cd8-98b2-b0683e186f29",
"signers": []
},
{
"id": "06fffb84-e400-46dc-bb49-4ecab0f6218c",
"signers": [
{
"email": "[email protected]",
"firstName": "John",
"lastName": "Smith"
}
]
}
],
"documents": [
{
"id": "2e3a2136c5ec55b35c70bf8b93d81b898f37678cd4885d46"
},
{
"id": "c6cd356a46c16290cd125b1b6c43930fd49a6b1f107676d8"
}
],
"name": "New Transaction Name",
"language": "fr",
"emailMessage": "New email message",
"description": "New Transaction Desc",
"autocomplete": true,
"status": "DRAFT",
"timezoneId": "EST"
}
Some noteworthy points:
(1)For roles, you will have to create then delete (see step2).
(2)For roles, if you want to keep the type as placeholder, you'd leave the "Signers" an array empty, otherwise, provide at least the email, firstName and lastName
(3)For roles, role ID (not role Name, e.g. Signer1, Signer2 as UI label indicates) is necessary to match with the template signers
(4)For documents, you can include partial document IDs (like role, document ID is necessary to find a match)
(5)You can still customize some of the package level attributes (e.g. transaction name, description, time zone, language, etc.) like I included in the payload
Step2: Delete the placeholder signer:
DELETE /api/packages/{packageId}/roles/{roleId}
Note: (1)package ID is returned from step1 (2)role ID is the same as you included in the package creation JSON.
Duo
Reply to: while cloning is it possible to clone only the documents and roles need from the template
Tuesday, August 10, 2021 at 09:43amHi Duo,
thanks so much!
I'll try it.
Mónica