" /> LiveCycle Doc team: October 2008 Archives

« September 2008 | Main | November 2008 »

October 29, 2008

Localizing the Share Queue Request form (queuesharing.swf file)

In Livecycle Workspace ES, a user can request access to another user's (say Alex Pink's) task queue. This initiates a queue sharing process and a Share Queue Request form appears in the Alex’s To Do list. The Share Queue Request form is a Flex application provided with LiveCycle Process Management ES and is available in LiveCycle Workbench ES in the queuesharing.swf file.

In earlier releases of LiveCycle ES, the source code for the Share Queue Request form was not provided with the rest of the LiveCycle Workspace ES source code, therefore, if you localized Workspace ES to another language, such as Spanish, the Share Queue Request form would still appear in English. In LiveCycle ES Update 1 SP 1 (8.2.1.1), the source code for the Share Queue Request form is now available in the LiveCycle ES SDK so that you can localize it. However, before you can localize the for, you you must configure your development environment for customizing Workspace ES as described in Customizing the LiveCycle Workspace ES User Interface and complete the localization customization.

To localize the Share Queue Request form:

  1. Copy the adobe-workspace-src.zip file, which is in one of the following two locations, to a folder in your development environment, such as testwssource:
    • [installdir]/LiveCyle_ES_SDK/misc/Process_Management/Workspace, where [installdir] is the location that LiveCycle ES is installed on the server.
    • [installdir]/LiveCyle_ES_SDK/misc/Process_Management/Workspace, where [installdir] is the location that LiveCycle Workbench ES is installed.
  2. Extract the contents of the adobe-workspace-src.zip file. You should see two subfolders:
    • Workspace: Includes the source code and files that you use to create your own custom version of Workspace ES.
    • LCAs: Contains the source code for the Share Queue Request form.
  3. In Flex Builder, select File > New > Flex Project.
  4. In the New Flex Project dialog box, in the Project name field, type a name for your project, such as ESQueueSharingForm.
  5. Deselect Use default location and click Browse.
  6. In the Select Project Location dialog box, go to the folder where you had extracted the Share Queue Request form in step 2. For example, /testwssource/LCAs/queuesharing.
  7. Delete the default MXML file that is created for you when you create a new Flex project.
  8. Right-click the folder of the language located under the locale folder that you want to localize the text from and select Copy. For example, right-click the en_US folder.
  9. Right-click the locale folder and select Paste.
  10. In the Name Conflict dialog box, type the locale code of the language you are localizing to.For example, es_ES for Spanish.
  11. Open the queuesharing.properties file from the folder that you created in the previous step.
  12. Modify the text in the right-hand side of each property-value pair and when you are done your changes, save the file.
  13. Open the build.xml file and at each approximate line number indicated below make the following changes:
    • Line 28, for the location attribute, put the location where you installed the Flex SDK compatible with LiveCycle ES. (See "Installing the Flex SDK" in the Customizing the LiveCycle Workspace ES User Interface guide.)
      <property name="flex.sdk.home" 
      location="C:\Program Files\Adobe\Flex Builder 3\
      sdks\3.0.1.lc"
      />
    • Line 29, specify the location of the LiveCycle Workspace ES SWC file: specify the location of the LiveCycle Workspace ES SWC file:
      <property name="workspace-runtime.swc"
      location="C:/Adobe/LiveCycle8.2/LiveCycle_ES_SDK/
      misc/Process_Management/Workspace/
      workspace-runtime.swc"
      />
    • Line 73, add your new locale:
      <arg value="-locale=en_US, de_DE, fr_FR,
      ja_JP, es_ES"/>
    • Line 192, add your new locale to compile options:
      <compiler additionalCompilerArguments=
      "-services "${root}/common/services-config.xml"
      -locale en_US fr_FR de_DE ja_JP es_ES
      -source-path+=${basedir}/locale/{locale}"
      copyDependentFiles="true"
      generateAccessible="false"
      strict="true"
      warn="true"
      htmlGenerate="true"
      htmlPlayerVersionCheck="true"
      htmlPlayerVersion="9.0.0" htmlExpressInstall="true"
      htmlHistoryManagement="true" outputFolderPath="bin"
      outputFolderLocation="${gateway.hot-deploy.client}/
      flexform"
      rootURL="${gateway.hot-deploy.url}/flexform"
      sourceFolderPath="src">
  14. In a command line, navigate to the root folder of your Flex project, and type ant to compile the project. You must use the ant command and not the builder that comes with Flex Builder.
  15. In the export folder, which is created after you run the ant command, you will see the queuesharing.swf file. Start LiveCycle Workbench ES and drag the queuesharing.swf folder to the Process Management > Workspace folder and update the existing QueueSharing.swf file in the Resources view. You may need to click Refresh to see the version number increment. The QueueSharing process uses the more recent version of the queuesharing.swf file for all new processes.

To test your updated Share Queue Request form, in a web browser, select the locale that you want to test in the languages settings, such as International Spanish (es_ES), and confirm that when you view the Share Queue Request form in Workspace ES, the localized version of the form is seen.

Note: Before you can test your localized Share Queue Request form, you must localize and deploy the custom Workspace ES application in the same language as you are localizing the Share Queue Request form. The custom Workspace ES application is a separate instance (EAR file) that you can deploy on the LiveCycle ES server. (See Customizing the LiveCycle Workspace ES User Interface.)

October 28, 2008

Configuring Rights Management ES Client Access

Adobe's LiveCycle Rights Management ES solution has been in the market since the beginning of 2005 and, as of our LiveCycle ES Update 1 release this past summer, can be used to protect a growing variety of file formats - PDF, Office, CAD, and FLV. The server works together with Adobe Acrobat and Adobe Reader clients to protect, view, and manage sensitive PDF documents. Because support is included in every copy of Acrobat and Reader 7.x, 8.x, and 9.x, we have more than 700 million machines world-wide that are capable of receiving protected PDF documents with absolutely no configuration required or any special software to be deployed.

We give you the option to allow documents to be viewed on any of these clients out of the box, but understand that in certain cases you might wish to restrict clients to the latest version. For example, there may be cases where you want to take advantage of newly introduced functionality, such as the new AES-256bit encryption algorithms introduced earlier this year.

As such, we now allow you to configure each deployed server to restrict which client versions or applications the server may communicate with. Technical details can be found at http://www.adobe.com/devnet/livecycle/articles/deny_services.html.

October 27, 2008

LiveCycle 8.2 Service Pack 1 now available

We’re pleased to announce the release of LiveCycle ES 8.2 Service Pack 1. This release not only addresses a number of customer related issues, but also includes updates to the documentation set.

The following documentation was updated for this release:
- All Installation guides
- All Upgrade guides
- All Clustering guides
- Administering LiveCycle ES guide now includes content for Content Services ES
- LiveCycle ES Error Code Reference
- Hardening and Security for LiveCycle ES
- Several of the admin help systems (Rights Management, User Management
- Contentspace End User and Admin Help
- LiveCycle Workspace ES Help
- LiveCycle Rights Management ES Help
- Three of the admin help systems (Rights Management, User Management, Generate PDF)
- LiveCycle ES Services guide
- Transformation Reference
- Creating Flex Applications Enabled for LiveCycle Workspace ES
- Programming with LiveCycle ES

Check out the resource site at http://www.adobe.com/go/learn_lc_documentation_82 for the latest guides. And don’t forget to read the Release Notes for those last minute updates.

For information on how to obtain this service pack, please refer to your Maintenance and Support welcome package or to the Customer Support portal for contact details.

October 24, 2008

Using LiveCycle Designer ES to create and print RFID labels

LiveCycle Designer ES lets you create and print RFID labels to capture data. RFID (radio-frequency identification) is an automatic identification technology whereby digital data that is encoded in an RFID tag or smart label is captured by a reader by using radio waves. It is similar to barcode technology but uses radio waves to capture data from tags, rather than optically scanning the bar codes on a label. Using RFID does not require the tag or label to be seen in order to read its stored data. [obtained from zebra.com.]

For example, airports use RFID labels for labeling luggage. RFID readers can accurately capture the information and flight details for each item that passes through a baggage handling system, regardless of its orientation or the speed of the conveyor. Some tags can even be immersed in water and continue to function with the same accuracy!


What you'll need

  • Adobe LiveCycle Designer ES 8.1 or later
  • LiveCycle Output ES
  • A Zebra printer that is capable of generating RFID output, such as a Zebra 110 XiIII plus printer
  • Documentation for the Zebra printer
  • RFID labels available from the printer manufacturer
  • Adobe XDC Editor (installed with LiveCycle Workbench ES)

How to do it
Here are the steps to creating and printing RFID labels.

=>Add the RFID object the form design
1. In the Object Library palette, click the Barcodes category and then click the RFID object.You can place only one RFID object on a form because the output can only be to a single RFID chip on the label.
2. Click in the area of the form where you want to place the RFID object.

=>Set the data length of the RFID object
To set the data length of the RFID object, click the Field tab and, in the Data Length box, type the length of the data.

The data length of the RFID object depends on the type of RFID tag type you are rendering. For example, if you are using RFID tag type 4, which corresponds to EPC Class 1 96 bit, you need to generate 96 bits of data. 96 bits of data corresponds to 12 bytes, which is represented by 24 hex values. Therefore, the value of the data length you enter is 24. The following table lists the RFID tab types and their values.

Tag Type...............................Value
0 ....................................... None
1 ....................................... EPC Class 0
2 ....................................... EPC Class 0 Plus
3 ....................................... EPC Class 1 64-bit
4........................................ EPC Class 1 96-bit
5 ....................................... ISO 18000-06B

=>Bind the RFID object to the XML data
Bind the RFID object to the XML data. (See To create a data connection to an XML data file in LiveCycle Designer ES Help.) The data length in the XML data must match the length that you set for the RFID object.

=>Configure the XDC file
Using the XDC Editor, modify the following RFID options options:
rfidBlockRetries
Controls the number of times the printer attempts to write to a particular block of a single RFID tag. The accepted values for this option is between 0 to 10. If you do not specify a value for this setting, the printer uses the default value of 0.
rfidLabelRetries
The number of labels that are attempted in case of an encode or write failure. This number is different from the rfidBlockRetries setting. The accepted values for this option are between 0 to 10. If you do not specify a value for this setting, the printer uses the default value of 3.
rfidTagType
Controls the encoding type of the data in the RFID label. The RFID readers should have the same tag type as the RFID printer. The accepted values for this option vary from printer to printer. (See your printer documentation for this information.) Generally, this option uses values between 0 to 5.
rfidTransponderPosition
Represents the distance of the microchip on the label from the top. Specify this value in dots. The accepted values are between 0 to length of the label. If the microchip is located at the beginning of the label, set this option to 0.

=>Map the XDC file to the printer
This XDC file should be mapped to the printer output device, which corresponds to your Zebra printer.

=>Verify the printed RFID label
After you print the RFID label, verify that the original data appears on the RFID label. The only supported output format for RFID is ZPL, which is for Zebra printers. RFID output cannot be rendered in PDF, PostScript, or PCL.

October 17, 2008

Creating a Simple Calculation with FormCalc

You can use the FormCalc scripting language to quickly add basic calculations to a form. Adding basic calculations to a form enhances the form-filling experience by eliminating the need for users to manually calculate values by hand, and helps to reduce data entry errors.

This video clip shows you how to add an arithmetic funtion to an object to perform a basic calculation. Thanks again to Lauren McGuire-Wood, our summer intern, for creating it!

Play clip


To learn more about using FormCalc, go to the LiveCycle Designer ES Help and search for FormCalc.

October 10, 2008

The Basics of Form Guides

What is a form guide?

A form guide is a wizard based in Adobe Flash that you can create as an alternative method for your users to enter data onto your form. A user is literally guided through the data entry process, which helps to reduce entry errors by limiting the amount of information presented to the user at any given moment. So instead of seeing a mass of fields and text – because the powers that be demand that you cram as much as possible onto that one sheet of 8.5” x 11” – the user sees chunks of information with animated transitions to move them from one chunk to another. It makes filling out forms feel less like, well, filling out forms.

Click here to see what a form guide looks like.

Note: To view form guides you must have Adobe Flash Player 9 or later installed.

Why would I want to use a form guide?

There are lots of reasons why you might want to use form guides, but here’s an example modeled on a real world case. The following image is of an immunization form.

immunization.png


To see a larger image, click
View image

The requirements of the form stipulated that users can print and fold it into a booklet in which medical staff could then manually write records of immunizations for a particular patient. Somewhere along the way someone decided it might be nice to also make the same form available in electronic format, but the user should print and fold the form after entering the data. Given this situation, you could create two separate forms, or you could go 21st century and make a form guide. The image below shows the form guide created for the immunization form. As you can see it’s a lot nicer than having to rotate your head ninety degrees every so often.

immunization_swf.png


View image

How do you create form guides?

You create form guides using Guide Builder, a tool available in LiveCycle Designer ES. As it turns out this is a handy arrangement because you create form guides from form designs, which are also created in LiveCycle Designer ES. Once you create a form guide for a particular form design, the form guide definition is actually saved inside the form design itself.

If you want to view a form guide as if you were the user doing the data entry, you can preview it right in Guide Builder. However, when you want to actually deploy a form guide to users, you will need to either:

  • Create a process design in Workbench ES that renders a form guide to Workspace ES. Your users then access the form guide through Workspace ES.
  • Render the form guide from a Java or web services applications using the LiveCycle Forms ES service to render the form guide. Your users access the form guide using the Java or web services application.

Read More

You can find a bunch of information about form guides in our product documentation. Check out the links below:

Have fun creating your own form guides. Drop us a note to tell us about your experiences.


October 6, 2008

Tech Notes: August 23, 2008 – October 5, 2008

Here is a list of Knowledge Base tech notes that the LiveCycle documentation team has published within the last month or so:

Conversion setting changes in the Generate PDF service are not reflected in Adobe Acrobat (kb405597)
Form images cannot be retrieved from a remote location at run-time (Acrobat, LiveCycle Designer ES) (kb405595)
Data loss if PDF size = the size of the LiveCycle ES setting: Default document max inline (kb405476)
Porting LiveCycle Workspace ES (8.0.1.x) customizations to LiveCycle ES Update 1 (8.2) (kb406317)
Using the proper Workspace ES source code for patched versions of LiveCycle ES (kb406320)
LiveCycle Policy Server policy and license migration fails after upgrade to Rights Management ES (kb406469)
Limitation to using Content Services ES and Connectors for ECM when used in processes (kb405812)
Potential migration issue between LiveCycle Designer 8.1 and LiveCycle Designer 8.2.1 (kb404758)
Security patch addresses protected document vulnerability (kb406070)
Queries required to clean up the LiveCycle Content Services ES database tables (kb405444)
FTP over SSH is not supported by LiveCycle Workbench ES process invocations (kb404801)
Configuring SSL authentication for LiveCycle Forms ES and LiveCycle Output ES on UNIX (kb404433)
Target version and originalXFAVersion (kb404872)

Other LiveCycle teams (like Adobe Support) also publish tech notes. You can search the Knowledge Base for a complete list of tech notes that were published within the last 30 days.

October 2, 2008

LiveCycle Workspace ES in a nutshell...

Did you know that you can use LiveCycle Workspace ES to interact with processes that involve users set in LiveCycle ES? Workspace ES is an RIA (Rich Internet Application) that comes with Process Management ES and allows end users to participate in and start processes that you developed. They can also search for processes using provided search templates and see custom messages in the Workspace ES banner. The search templates and banner messages are set by you as the Workspace ES administrator.

For example, Tony Blue, who is a client of Insur@nce Corp, needs to submit an insurance claim. The insurance claim he submits in Workspace ES automatically gets routed to insurance agents at an insurance company. The application form might be provided as a form guide, which is a Flash-based form that provides an easier experience for filling out the details. After the form is completed and submitted, it gets routed to the agents, where the form might be displayed as a PDF. There can be business logic set in the process so that certain types of applications are routed to different insurance agents. Since there can be many agents at the insurance company, who can get hundreds of applications a day, their list of applications to review can be managed using individual or team queues. Workspace ES also allows the agents to share their queue with each other to balance the workload or re-route applications when they are out of the office. Below is what Tony sees when he fills out his claim:

WorkspaceFGClaimForm.jpg
To see a larger image, click here


Before automating your business process for use in Workspace ES, you must design a form and a process In LiveCycle Designer ES, you design the form, which displays and captures information from users involved in the process. The form can be displayed in PDF, HTML, or as a form guide. You can also design the form in Flex Builder or the Flex SDK. Flex forms can provide an enriched experience that transcends traditional forms designed in Designer ES. In LiveCycle Workbench ES, you design the process map, which is a graphical representation of your business process. You can configure the process map with business rules, inputs, and outputs.

After designing your form and process map, you configure your automated business process for use in the LiveCycle Administration Console by setting the process to be started from Workspace ES.

Since Workspace ES comes out-of-the-box, you may want to customize it for your organization. You can rebrand it with your own colors and images or you can build your own RIA using pieces of the Workspace ES User interface and components from the Workspace ES API.