Posted in Digital Signatures, ES2 Highlights, LiveCycle ES2, Process Managment, Workbench, tagged approvals, Digital Signatures, Electronic Signatures, eSignature, PKI, Workspace on October 21, 2009|
Leave a Comment »
LiveCycle ES2 now supports electronic signatures in Workspace (in addition to digital/PKI based signatures). The eSignature solution leverages the following features:
Ability to Route Arbitrary Content
Now you can route a flat pdf, .jpeg, .gif etc… for approval (basically anything that can be displayed in a web browser).
A Workspace mode specifically designed and tailored for approval processes.
Gives the LiveCycle developer full control over the buttons presented in the Workspace Chrome, and the order in which they appear. Also provides tighter integration with process routing via Destinations.
Approval Confirmation Dialog
Allows you to present a confirmation dialog with a custom EULA and inform the user that this is a binding agreement. To get this option in Workbench simply double click a defined User Action.
IP Address Auditing
The ip address of the signer/approver is captured in the output of the Assign Task & Multiple Assign Task operations. This can be used to build an audit log.
Read Full Post »
Description: Workspace based Digital Signature workflow. An XDP file is pulled from the repository, rendered, Reader Extended and presented to two users for fill and sign. Note: When using Reader 9, this tasty treat is yellow triangle free!
- 1 xdp template
- 1 custom render service
- 1 Reader Extensions credential
- 1 DocumentForm variable
- 1 Task Manager Endpoint
Here is a video showing an overview of the process as well as the final application – Watch a video of the workflow
Collateral – LiveCycle Archive (.lca) and installation instructions:
- When designing your form in Adobe LiveCycle Designer, avoid using the standard process fields when targeting Digital Signature workflows. Instead, use a basic submit button, and set the submit type to PDF. An additional requirement is to make the submit button invisible at design time; This will result in a yellow triangle free workflow when targeting Adobe Reader 9.
- Instead of using an XFAform variable, use a DocumentForm variable; A DocumentForm variable is used when you want to pass a PDF document around a workflow and maintain a persistent state, as opposed to passing around an XDP file and rendering the form for each user. When using a DocumentForm variable the render only occurs once, at the beginning of the workflow.
- When targeting Adobe Reader as a client with this particular workflow, you must Reader Extend the form and grant the following Usage Rights: Basic form fill-in and Digital signatures. The Apply Usage Rights activity should be added as the last step in the render process.
- When working with XDP templates and Reader Extensions, in your render service, modify the Render to PDF form activity, so that the Render At Client option is set to No, otherwise the Usage Rights will be invalidated for subsequent users.
Read Full Post »