Archive for January, 2010

LiveCycle: data variable values lost for migrated LC7 process containing branches


If you have a process created using LiveCycle 7.x that has been migrated into LiveCycle ES, and it contains branches, you notice that data variables lose their values when moving from one branch to the next.

Consider this example:


The example shows two branches, each containing a User activity, which assigns a task to a user’s queue with a form merged with data. Different data is set for each user in the first step in each branch. Therefore User1 opens a form in Workspace and expects to see <BRANCH 1 DATA>; User2 expects to see <BRANCH 2 DATA>.

Note the following variables for this process:

There are separate variables for each branch. However, when the process is run and the flow reaches the first User activity in branch1, it overwrites the data in branch2 (in the branch2_form), which means that both users see <BRANCH 1 DATA> in the form at run time.


This issue has been fixed in ES SP4 (, ES3 (10) and later versions.  If you require a patch for this issue for LiveCycle ES 8.2.1. contact Enterprise Support.

reference: (181371341/2528237)

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

LiveCycle ES: How to enable task assignment emails and links to forms in Workspace

Enabling e-mail feature

Adobe LiveCycle Administration user interface has a feature that enables ‘Assigned Task’ e-mails to be sent to users as soon as a task in Workspace is assigned to them. To access or configure this feature for all users, a LiveCycle administrator enables it under: Home > Services > LiveCycle Process Management ES > Server Settings > Task Notifications. The template that is displayed can be customized with the tags as described here:

Enabling e-mail link

You can add an HTTP link to the e-mail template that points to the form in Workspace that the user must complete to continue the process. If the user is not already logged in to Workspace, or if their session has expired, they get re-directed to the login dialog before being taken to the form. You can add an HTTP URL to this notification e-mail as described in the documentation here:

The default setting for the link is: http://[server name]:[port]/workspace/Main.html?taskId=[value]

The URL http://[server name]:[port]/workspace?taskId=[value] also works.

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

LiveCycle ES: “Documents in this folder are not available” trying to access the repository through WEBDav


If you are using WEBDAV (i.e. web folders) to access your forms and resources in the repository you may encounter the following error in Windows Explorer:

"Documents in this folder are not available.  They may have been moved or deleted, or network problems may be preventing a connection to the server."

This error occurs when some of the folders in the repository contain spaces, so the spaces get replaced with “+” characters for the standard URL encoding.  Internet Browsers are able to handle this URL encoding and you can access the folders and files, however WEBDAV cannot handle these URL encoded folder paths.


 If there are spaces in the folder names, and they are displayed as “+” characters in the WEBDAV folder view, then you can workaround the behaviour temporarily by just renaming the folder and removing the “+” characters.  Then you will be able to browse into the folder.  This will revert back to the folder name with “+” characters when you re-connect to the WEBDAV folder.

The other option would be to link the WEBDAV folder directly to the problem folder (i.e. the one with the “+” characters), instead of linking to the repository root.  This would require a WEBDAV folder entry for each problem folder in the repository, which may not be realistic depending on how many folders you have.

The ultimate solution here is to get the patch which addresses this issue in the LiveCycle repository.  The issue has been fixed in LC ES SP4 (, ES3 (10) and later versions.  Please contact Adobe enterprise support if you require this patch, to ensure you get a version that will work on your platform and LC version.

Additional information

 WEBDAV refers to the method of setting up a Network Location pointing directly to the LiveCycle repository on the LiveCycle server as follows:

1. goto network places

2. add location

3. http://<LCServer_ip_address>:<port>/repository

4. enter LiveCycle credentials for WEBDAV folder (e.g. administrator:password)

5. open WEBDAV folder

reference: (181280536/2526842)

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

Acrobat/Reader 8: PDFs rendering or behaving differently

If you have upgraded from Adobe Reader 7 or earlier to Adobe Reader 8 or later, you notice some differences in the PDF behavior. For example,

  • Form events not fired in the same order, or with the same frequency (particularly the layout:ready event). As a workaround, you can move the script to another event in Designer (for example, form:ready).
  • Text is shifted or clipped
  • PDF field values are modified (particularly checkbox and radio-button values)
  • Tabbing order is different (read-only fields are included in the tabbing order). As a workaround, set the field property in Designer to “protected” instead of “read-only“.

These differences result from a change in the rendering engine in Adobe Reader 8 and later.  The rendering engine was redeveloped to improve performance of large dynamic forms (100+ pages). The rendering engine in Adobe Reader 8 and later uses direct or AGM rendering. Some of  the changes mentioned above (form events, tabbing order) are side-effects of the rendering engine modifications, and others (text-clipping, field values) are product issues. The side-effects have known workarounds as outlined above, whereas the product issues have been addressed in the subsequent versions of Reader (8.2, and 9.3).

If you encounter other issues not mentioned above, and you want to restore the behavior from Adobe Reader 7, you can use a compatibility flag. The flag instructs the rendering engine to use the legacy engine from version 7.  Place the following flag in the XML source:


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