Author Archive: Trevor Ward

LiveCycle 8.2.x Form Guides is now LiveCycle 2.5 Guides

Hi,

LiveCycle Form Guides has been updated to LiveCycle Guides, the blog for it can be found at:

 http://blogs.adobe.com/lcguidebuilder/category/guide-builder-es2

LC Guides are authored in LiveCycle WorkBench and can be built leveraging a XFA based XDP /PDF or an Adobe Data Model.

LiveCycle 8.2.x Form Guides are automatically migrated to the new Guide format when openned in Guide Designer in WorkBench.

Here is a link that I hope is helpful:

http://help.adobe.com/en_US/LiveCycle/9.5/WorkbenchHelp/WS92d06802c76abadb-6093cecf128f4330f05-7fa3.html

Trevor

Offline Form Guides via PDF

This post describes how to take any deployed Form Guide and embed it in a PDF so that the Form Guide may be emailed or used offline. The resultant PDF looks and behaves just like any other XFA based PDF as far as LiveCycle processing or Reader/Acrobat is concerned. The Form Guide’s data is stored in the standard XFA Datasets part of the PDF.

Adobe Reader/Acrobat 9.0 is the minimal client requirement.

Here is a sample Form Guide delivered as a PDF.

The basic component is a generic base bootstrap PDF into which a Form Guide SWF is added as an Attachment. The bootstrap PDF has some XFA script and an embedded SWF Loader app that invokes the script to find and load the Form SWF. The submission process uses Readers Email option to submit back to the Server process. The target email account is defined in the XFA Script along with the format of the submission which can be the whole PDF or just the xml data.

The PDF will need to be Reader Enabled to allow Reader users to Save the PDF to their disk.

It is also possible to include a optional “document view” XFA based PDF, but requires a minimum of Reader/Acrobat 9.2. The data entered into the Form Guide can automatically update the PDF document (it is expected be a non-interactive document, as data only flows in one direction)

Attached are a White Paper describing the full process flow of generating a PDF of this flavor, sample Guides in PDFs, the basic source Bootstrap PDF and the source for the embeded SWF Loader. The Bootstrap PDF can be loaded into LiveCycle Designer in order to see/modify the XFA script. There are a few options that can be activated/deactivate by modifying a list of supported features defined at the top of the script object.

This technique can also be used to attach a Flex App instead of a Form Guide, as long as the App implements the following functions at the Application root:

function getData():String – returns XML as a string
function setData(xmlData:String):void
function validate():Boolean

The supplied BootStrap SWF Loader can be easily extended to handle many different unique requirements. Those features can include displaying buttons that allow the user to click and Print/Save/Email/ the document without actually seeing the document view or importdata/exportdata or process more than one SWF APP attachment. Note that the PDF will need to be Certified to allow the Print option to work.
Let me know if more information is desired on how to do this.

More Samples:

FormGuide with Document View PDF attached as well
Another FormGuide with Document View PDF attached as well

Source Files:

PDFBootStrap_Raw.pdf
PDFBootStrap_AutoUpdateData.mxml
xfaScriptObject.txt

The cookbook process for creating a generic PDF for delivery of RIAs is Patent Pending.

Other solutions to leverage PDF as an RIA container can be found at:

http://pdfdevjunkie.host.adobe.com/RMA1_acrossTheBridge.shtml

http://www.jamesward.com/2008/11/05/portable-rias-flex-apps-in-pdfs/

Patch to Guide Builder SDK for FlexBuilder Usage

Form Guide components need to be built using the same SDK as the core Form Guide Libraries. Flex Builder has updated its’ SDK but since the Guide Buider and the LC Server where shipped using a 3.0.1 version of the sdk, the default in Flex builder no longer works.

Guide Builder’s version of the Flex SDK is missing a file that Flex Builder needs in order for it to recognize the sdk version. Without the identifier file Flex Buidler assumes it is a 2.x sdk and does not load it correctly.

Click, download and save this flex-sdk-description.xml file into the Guide Builder flex-sdk directory.

The Default install location is:
C:\Program Files\Adobe\LiveCycle Designer ES\8.2\plugins\GuideBuilder\flexsdk

After applying the simple patch, in Flex Builder on your Project Properties, select “Flex Library Compiler”, (configure sdks if needed), and select “use a specific SDK”. Point to the Guide Builder 3.0.1 version of the SDK.

Form Guide in an AIR app with a PDF

Here is a sample that is to be taken “as is”, as just a basic sample of how to make an AIR app that has a Form Guide in it that can share data with a PDF that is also in the AIR app. It was created by one of my collegues just to see if it could be done. It is not an officially support solution at this time, but numerous people are starting to build apps of this type. Please keep that in mind. You can retieve your Guide SWFs to use from the temporary Preview directory.
This is a Flex Builder 3.0.1 project zipped up.

Download file

NOTE: TOO MEET the USER LICENCE AGREEMENT for Guide Builder, you must use LiveCycle Forms Service to generate the Guide SWF. The use of the Designer Preview is for Development purposes only.

To get just the SWF returned (instead of the html with callbacks) from the normal LC FormGuide request add/set “cb=1″ to the request.

The GAClientRuntime.swc and XFAModel.swc Library files can be found in LC Designer’s install directory under plugins/GuideBuilder, the project will need to point there on your system.

Patch for Guide Builder Preview

This post is about an issue I uncovered while assisting a client with creating a Form Guide.

Under some circumstances the “history.js” script that ships with Guide Builder, as part of the Guide Preview processing, can adversely affect the Guide and PDF communication messaging as well as have a possible performance impact while previewing. Attached is an updated file for the Guide Builder that will allow preview to work correctly and more effieciently. Basically, I have just disabled the history processing which was of no value in Preview anyway.

Included in this post is a replacement version of the “history.js” file. It should be copied into the installed Guide Builder program directory’s “bin” subdirectory.

Steps to apply the patch:

1. Make sure there are no instances of Guide Builder running.

2. Download ‘history.js’ file, then Copy “history.js” into the “bin” subdirectory of Guide Builder.

For WorkBench installations:
C:\Program Files\Adobe\LiveCycle ES\Workbench ES\Designer ES\8.2\plugins\GuideBuilder\bin

For Designer standalone installations:
C:\Program Files\Adobe\LiveCycle Designer ES\8.2\plugins\GuideBuilder\bin

3. Open Guide Builder and do Previews.

Please let me know if this post was of value to you.