Posted in Assembler, ES2 Highlights, LiveCycle ES2, Workbench, tagged Assembler, DDX, DocBuilder, Document Builder, LiveCycle ES2, Workbench on October 21, 2009|
Leave a Comment »
Document Builder is WYSIWYG editor for DDX and ships with LiveCycle Workbench ES2. In previous releases of LiveCycle ES you had to hand code DDX; Document Builder gives you tools to design, validate and test DDX files in a graphical manner.
What is DDX?
To specify documents that you want the Assembler service to produce, you use an XML-based language called Document Description XML (DDX). DDX is a declarative markup language whose elements represent building blocks of documents. These building blocks include PDF pages and other elements such as comments, bookmarks, and styled text. The DDX document can be considered a template for the document(s) that you want the Assembler service to produce.
Document Builder Features:
- WYSIWYG editor for designing DDX
- Full integration with Workbench and Assembler’s Invoke DDX service
- Schema Validation
- Ability to test DDX and to preview results
- Templates for the most commonly used Assembler operations
- Design and Source modes
Read Full Post »
Record and Playback is often considered the most valuable debugging tool in LiveCycle. It allows you to record then step though the execution of a process, to examine the variable values, routes taken etc…
The following Record and Playback improvements were made in ES2:
- A visual indicator (a red dot) will now appear when recording is activated for a particular process
- You can manage process recordings at a global level (Start/Stop/Delete etc…) This allows an administrator to easily disable all recordings on a server.
- You can activate/deactivate recordings for an entire application in a single click
Read Full Post »
In Adobe LiveCycle ES2 the Workbench property sheets have been overhauled to simplify and streamline application creation. Here are a few examples:
Basic | All filter toggle
Most property sheets in ES2 now include two modes — Basic and All. Basic presents the most commonly used settings, while All will present you with all available settings for the service.
Render PDF Form
The FormsService:renderPDFForm service has been greatly simplified, and thanks to the new asset picker there is no longer a need to hand type URIs. Here is the new service in Basic mode.
No longer a need to hand type URIs!
Auto Discovery of Credential Alias Names
You no longer have to look at the adminui to determine the available aliases for Reader Extensions or Signing credentials. This feature applies to Apply Usage Rights, Sign Signature Field, Certify PDF & Certificate Encrypt PDF.
Read Full Post »
In LiveCycle ES2 Action Profiles streamline the creation and management of pre-fill and custom render services. If you are familiar with this pain point from a previous release you are going to absolutely love the flexibility and power of Action Profiles in ES2.
Let’s pre-fill a form for display in Workspace in less than five minutes…
LiveCycle Version: 9.0
If you get stuck… here is the collateral and completed LCA (.pdf w/ attachments): ES2_Prepopulate
- An XML schema (a sample schema is provided in collateral download if you do not have one).
- Launch Adobe LiveCycle Workbench and create a new application.
- Expand the application, right click version 1.0 and select New > Form, this will launch the new Form wizard. When promoted for a data model import your schema (The use of a schema is highly recommended, if you do not have a schema you can use a service such as http://www.hitsw.com/xml_utilites/ to create one based on sample XML).
- Adobe LiveCycle Designer will launch — Drag a few items from the Data View onto your form. This will automatically bind your form fields to the schema. Save and close the form. If you don’t see any items in the Data View, right click the Data Connection and specify the correct root node in the schema.
- Launch the new process wizard by right clicking your application and selecting New > Process. Choose the following options in the wizard: When a user submits a task in Workspace… & Use an existing Form (select the form you just created)
- In the process double click the start point and click on the Manage Action Profiles button.
- Create a new Action Profile named Prefill.
- Make sure your newly created profile is selected and click the Create a Prepare Data Process button, select defaults and click OK. This is going to automatically stub out a new pre-fill process for you. Close the Manage Action Profile dialog and switch back to your process.
- Notice that the new Action Profile you just created is now selected for the Workspace Starpoint. Action profiles are tied to a specific form, you can manage them by right clicking the form in the application view or from the startpoint Presentation and Data settings property editor.
- Save your main process and open the pre-fill process that was created for you (If you left the defaults intact it should be named [YourFormName]PrepareData).
- Examine the stubbed out process — Notice that you already have an xml variable that is backed by the schema that your form is associated with; This is the advantage of using the wizards.
- Drag a SetValue operation onto the canvas from the tool bar.
- To configure the SetValue, the location should be the node you want to set in your form’s input data (Since you are using a schema you can simply drill down into it and double click it to build the XPath statement).
- For this example let’s set the field’s value to the task creator’s name. Double click the empty [Expression], drill down into the Task Context and locate the Common Name, double click it and say OK to complete the SetValue operation.
- Deploy the application by right clicking version 1.0 in the application tree and selecting Deploy.
- Test the application: Right click the main process in your application view (or right click in the canvas) and select the Invoke operation. Choose the option to Open the selected start point in a web browser (another nice ES2 shortcut).
Additional Action Profile Tips:
- For each step in a workflow you may have a different Action Profile e.g. you may want to perform a pre-fill when a process is initiated, but for the second user you may just want to use the default (no-op) profile so that the form is not modified. Action profiles give your this flexibility.
- An Action Profile set is associated with a particular form. You can re-use the associated pre-fill and render processes but each form will have its own Action Profile definition/set.
Read Full Post »