Archive for July, 2009

LiveCycle ES: Namespace problems in SetValue and Script services

Issue

When working with namespaces in the SetValue and Script objects in LC7, you may receive an error saying the “path” is unreachable, or similar errors pointing to problems in the expressions, after migrating to LC ES.

Reason

These errors can occur in LC ES when using namespaces such as in the following example:

LiveCycle ES now validates XPath expressions more strictly than it did in LiveCycle 7.  LC ES requires you to define the namespaces in the process, whereas Lc7 did not have this requirement.

Solution

Adding the namespace to the process properties will fix the issue.  You only need to add these namespaces once for each process, and all the Script and SetValue activities in that process will be able to reference those namespaces.

To add the namespaces:

Open the process properties and go to the Advanced > Registered Prefixes for Namespaces used in XPaths and enter the prefix (i.e. soap), and the namespace (i.e. “http://schemas.xmlsoap.org/soap/envelope/“).

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Reader 8: how to print comments

Issue

You can use Acrobat 8 to apply usage rights to PDFs, in order to distribute the PDFs for Review and Commenting workflows to Reader 8 users.  This includes the option to print comments.  This is possible in Acrobat 8 using the “Document and Markup” option in the print dialog itself, and if the “Print notes and pop-ups” option in the Commenting preferences in Acrobat is enabled.

However, in Reader there are no Commenting preferences, so the users have no way to enable printing of comments even if they select the “Document and Markup” option from the print dialog.

Solution

There is a registry key in Acrobat that controls the “Print notes and pop-ups” option in the Commenting preferences.  If you set the following key in the Reader registry, then the comments are printed:

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\8.0\Annots\cPrefs]
"bprintCommentPopups"=dword:00000001

_____________________________________

reference: (180910916/2332536)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle Workbench ES: activities not displayed in viewable area in process editor

Issue

 When importing a LC7 process map into Workbench, you may have some graphical display problems, where certain activities are running off the viewable area in the process editor panel.  You can see the route lines leaving the page in Workbench and returning but you cannot access the activity, and so, cannot change it’s properties or move it back onto the page.

Here is an example of the problem on the process editor where you can see the route lines going outside the viewable area and coming back in, but you cannot see the related activities:

Reason

 It can occur that the “x” and “y” position for some activities become negative during the import process.  These values define the positions on an x-y axis, and so, if they are negative, they will not appear in the viewable area in Workbench.  This is a product bug in Workbench ES.

Solution

This issue has been fixed in Workbench ES 8.2.1.3, 9.0.0.0 and later versions of Workbench.  For Workbench ES 8.2.1.2 there is a patch available.  Please contact your Adobe support contact if your require the patch for 8.2.1.2.

The other option (although not recommended) is to modify the process XML, and just remove the minus sign from the x and y values as required.  Be sure not to change the “x-offset” or “y-offset” values.  These are relative values, and so, can be negative.

If you install the patch or are using a later version of Workbench then the values will be restored correctly.  Here is the result of making the manual changes in the process XML for the gateway activity, bringing it back onto the viewable area:

reference: (180802976/2338539)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: Command Line Interface (CLI) for installer and LCM language settings

Issue

 The CLI tool for the LiveCycle installer and Configuration Manager is only supported in English.  You may notice errors in the output if you use the tool in any other language.  Some of the variables for host names may not be resolved in the localized output, or accented characters may not be displayed correctly as in the following screenshots:

French:

German:

It is possible to change the language for the LCM graphical user interface by changing the locale in Regional Settings, or by changing the LCM.lang property in the userValues.properties file found under:

[LiveCycleES root]/configurationManager/config/userValues.properties

Changing the language for the command-line interface however is not supported as it only works in English.

Solution

Ensure that you run the CLI tool on a machine with English regional settings, and change the LCM_lang property value to “en” in the LCM properties files found under: [LiveCycleES root]/configurationManager/config

Additional Information

Note: If you use the GUI version of LiveCycle Configuration Manager, and then chose to use the CLI version, you can use the property file created by the GUI version as the template for the CLI version property file.  When you run the [LiveCycleES root]/configurationManager/bin/ConfigurationManager.bat file, the userValuesForCLI.properties file is created in the [LiveCycleES root]/configurationManager/config directory. You can use this file as input for the LiveCycle Configuration Manager CLI.

You can find further information and a parameter appendix for the CLI tools in the installation guides for each platform:

http://www.adobe.com/support/documentation/en/livecycle/

reference: (181022950)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle Workbench ES: java.lang.RuntimeException “Branch: <Name> already exists”

Issue

 When running the Upgrade Tool in Workbench to upgrade a LiveCycle 7 process to a LC ES orchestration, you may receive the following error:

java.lang.RuntimeException "Branch: <Name> already exists"

Reason

 When working with Split activities in LiveCycle 7  it was allowed to have duplicate branch names in the list of branches for a particular Split activity.  For example:

 Split:

        branch

        branch

In LiveCycle ES however, this is no longer allowed.  All branch names must be unique

Solution

 This issue has been fixed in Workbench 8.2.1.3, 9.0.0.0 and later versions.  There is a patch available for Workbench ES 8.2.1.2.  You should contact Adobe support if you require this patch.

The fix now handles the duplicate branch names by appending an index onto the branch names, for example:

Split:

        branch

        branch1

_____________________________

reference: (180803060/2338552)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: CRON expressions and documentation for Quartz Scheduler

Issue

 If you wish to schedule an LDAP synchronization in LiveCycle you can do so using CRON expressions in the Quartz Scheduler.  The Quartz Scheduler is an open source technology and you can find the official documentation here:

http://www.opensymphony.com/quartz/wikidocs/CronTriggers%20Tutorial.html

Explanation

 The meaning of the fields we use in the CRON expressions are as follows:

Field Name Mandatory Value Range Special Characters
Seconds Yes 0-59 , – * /
Minutes Yes 0-59 , – * /
Hours Yes 0-23 , – * /
Day of month Yes 1-31 , – * ? / L W C
Month Yes 1-12 or JAN-DEC , – * /
Day of week Yes 1-7 or SUN-SAT , – * ? / L C #
Year No empty or 1 , – * /

Examples

0 0 12 * * ?                         Fire at 12pm (noon) every day

0 15 10 ? * *                       Fire at 10:15am every day

0 15 10 * * ?                       Fire at 10:15am every day

0 15 10 * * ? *                     Fire at 10:15am every day

0 15 10 * * ? 2005               Fire at 10:15am every day during the year 2005

0 * 14 * * ?                         Fire every minute starting at 2pm and ending at 2:59pm, every day

0 0/5 14 * * ?                      Fire every 5 minutes starting at 2pm and ending at 2:55pm, every day

0 0/5 14,18 * * ?                  Fire every 5 minutes starting at 2pm and ending at 2:55pm, AND fire every 5 minutes starting at 6pm and ending at 6:55pm, every day

0 0-5 14 * * ?                       Fire every minute starting at 2pm and ending at 2:05pm, every day

0 10,44 14 ? 3 WED            Fire at 2:10pm and at 2:44pm every Wednesday in the month of March

0 15 10 ? * MON-FRI            Fire at 10:15am every Monday, Tuesday, Wednesday, Thursday and Friday

0 15 10 15 * ?                      Fire at 10:15am on the 15th day of every month

0 15 10 L * ?                        Fire at 10:15am on the last day of every month

0 15 10 ? * 6L                      Fire at 10:15am on the last Friday of every month

0 15 10 ? * 6L                      Fire at 10:15am on the last Friday of every month

0 15 10 ? * 6L 2002-2005      Fire at 10:15am on every last friday of every month during the years 2002, 2003, 2004 and 2005

0 15 10 ? * 6#3                    Fire at 10:15am on the third Friday of every month

0 0 12 1/5 * ?                       Fire at 12pm (noon) every 5 days every month, starting on the first day of the month

0 11 11 11 11 ?                    Fire every November 11th at 11:11am

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 7.0/10 (3 votes cast)