RequiredFields not working

Hi asimao, Now I understand your use case! Your previous workflow is fine, the only thing is, you need to update your layout to make the fields mandatory. Simply create another layout with the same name, which will override the existing one. Duo

Hi asimao, I've checked the template against the package, and looks like all the 9 required fields in the template are all not mandatory in the package. I created a template with the same fields and signatures, but can't reproduce the issue when I created a package from this template. So here's few questions: (1)Does the issue consistent? If you created another package based the template, do you see the same unexpected behavior? (2)If you create the package from web portal, will you hit the same problem? (3)Did you call the API or SDK to "create the package from template"? Can you share the JSON or the code you used? Duo

Hi Duo_Liang, thanks for the support. 1 - Yes the issue is constant. 2 - If I create by web portal, using the transaction template, it actually works. But by reading your answer I think I didnt explain myself correctly, by API 1- I build a package by template (the one you mentioned) - all good here 2- I added a document eslClient.UploadDocuments(mypackage.Id, new List() { doc }); 3- I applyed to the document a Layout ( eslClient.LayoutService.ApplyLayoutByName(mypackage.Id, mypackage.Documents[1].Id, "Layout_########_####_2019"); 4 - Now if I iterate through Fields of the mypackage.Documents[1].Signatures, I see all fields from the Layout and the propertie isRequired is correctly defined. (Most of the mandatory fields are for CustomId= "29ae46c6-a5ec-4919-98ae-7589d9e1263d") Soo if apply a "layout" to a document and i can see all fields and the properties of each one, IsRequired included, why do you say that " looks like all the 9 required fields in the template are all not mandatory in the package" ?

Hi asimao, I see, I checked the layout under your account and found that all fields are NOT required. Few thinkings for this issue: (1)if you already create a package out of a template (your template includes the document and all the fields for this document), why you still need to apply the layout(all the fields for a particular document)? (2)if you want to check your layout, you'd follow this process: -log onto your web portal to get a browser cookie -once logged in, hit this link:https://sandbox.esignlive.com/a/transaction/eXHfOpkgH9LYfyQpP7TgD7IkNkM=/design, which will bring you to the layout designer page where you will see all the fields are NOT required there. ("eXHfOpkgH9LYfyQpP7TgD7IkNkM=" is your layout ID, matches the name of "Layout_########_####_2019") Duo

Hey Duo_Liang, thanks for the replie. (1) in each transaction i need to customize the signers and i need to replace the document with a specific one, but maintaining the fields and their properties (for that I was applying the layout) By that I thought I had to upload the new document and apply the layout. (2) I checked the link and now i understand that what your saying. Soo how can I do step 2 by API: step 1 - created a transaction by template, customized the signers (done and ok) step 2 -need to replace the document with a specific one (Z) ,but maintaining the fields and their properties of the template/layout ? (Z is a document with same structure but some data changed).

Hum... Soo i can't edit the existing layout, i have to create another one with the same name. ok, gonna try this. In the transaction build with tneplate, to replace the default document only need to upload a document ( eslClient.UploadDocument) with the Id of previous document?

Hi asimao, Actually you can edit the existing layout: update the fields in the link I provided above, you don't need to resend or save the layout, it's saved automatically (just in most cases, users don't know how to view the layout by building the link I provided above) To replace the document, the easiest way is to use the same document ID to override the existing document, instead of using a two-step approach to delete then upload. Duo

Worked but it wasn't suppose to be that hard!!! If I CreatePackageFromTemplate, then set Attributes of my package and later UploadDocument, it didnt work!!! For it to work i had to CreatePackageFromTemplate and then immediately do the UploadDocument. Why is this so tricky!!!?