Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

Digital Signatures and Table Row Add/Delete

Avatar

Level 3

I have a table that I want to add or delete rows but one of the cells in the row is a signature field; that column, always has a signature field. In the past, I have noticed that Adobe Livecycle Designer prevents the typical add or delete function (.addinstance(0)) when a digital signature field is present. I was wondering if there is a work around. One thought I had was having say 15 rows but hiding 10 of them. The add button would unhide the hidden rows up to the 15 total rows. The delete button would hide rows down to a min of 5 shown.

I was wondering if anyone know whether or not this would work and what the syntax would be. Also, is anyone aware of other work arounds?

Thanks,

Mallard27

2 Replies

Avatar

Level 8

Last time I tried that, ie, to add a digital signature inside a dynamic subform, and I found out that the Signature Field will not show. I think this is by design.

Tarek.

Avatar

Level 5

Signatures can only be placed on the form statically, so having a repeating (1 to many) dynamic subform with a signature is invalid and is not allowed by designer. I think mostly since a signature field cant be created dynamically, it must exist in the pdf prior to loading.

However, You still can have multiple signatures in a static table as you suggested, making the rows visible/hidden depending on content and cant see why it wont work. But you will need to careful with it. I would presume you will need to make sure you are displaying all rows and then hiding those not in use. Doing the opposite will invalidate signatures. Invisible signatures are not the same as visible signatures and will be invalidated and removed. You should probably only create a new line when needed on a button action, since any hiding will invalidate the previous signatures (since its a form change). You cant lock all fields with multiple signatures and will get errors, so you will have to use form object collections and assign each one to an individual signature ( if fields are involved).

Also, If you are using any LiveCycle server components at all, I'm not sure about the level of support there is for processing multiple signatures. I probably think it would have to be done by a custom component to read the multiple signatures on the submitted xfa data.

There is further background about xfa signatures (a bit older reference) here http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/digisig_in_XFA.pdf

Sorry, meant to reply to original post. Message was edited by: dohanlon