Posts tagged "workspace"

LiveCycle ES: Processes in Workspace and AdminUI appearing as “null – 0.0″

Issue

After you upgrade from LiveCycle 7 to LiveCycle ES 8.2.1, some of the processes in the Admin user interface and Workspace appearing as “null – 0.0″.

Reason

Corruption in the LiveCycle ES database causes process names and versions to be listed in the Admin user interface as “null – 0.0.”.  The corruption can be caused if the database content has been modified manually, or if you are using an external (not from Adobe) purge tool on the database.

Solution

Restore the database to a valid state.

reference: (181491899)

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

LiveCycle ES: Link to help files returns 404 error with localized Workspace

Issue

When you use the localized version of LiveCycle ES 8.2.1 Workspace in a web browser, clicking the link to the Help files may return a 404 error. The link works correctly when you use the standard English locale.  This issue has been reported particularly on French and German locales.

Reason

This was a bug in LC ES 8.2.1.2 and previous versions.

Solution

This issue has been fixed in LC ES2 9.0.0.0 and later versions.  There is a patch available for LiveCycle ES 8.2.1.x, so you should contact enterprise support if you require this patch.

reference: (181413026/2542542)

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

LiveCycle ES: Change Workspace AMF Polling interval

Issue

If you are using LiveCycle Workspace ES you will notice that it is polling the LC server every few seconds for updates. You can see the polling frequency by using a web logging tool like Fiddler2 and analyzing the logs for the entries related to “messagebroker/amfpolling”.

The polling is used to update the user and group queues with task information. Each Workspace client polls the server with this frequency, which may start to affect the performance. In this case, the polling interval can be changed, especially if you are using task assignment e-mails, which makes the automatic updates in Workspace less critical.

Solution

The polling interval in Workspace uses the default value defined by the AMFChannel. Unfortunately, it is not possible to build a patch to expose this property or to set it to a fixed value. Doing so would mean creating a customized version of Workspace for one customer and maintaining this version separately from the standard Workspace for all other customers.

A better solution is to allow you to control this property in your own Workspace version. This can be achieved through a small modification of the Workspace source, which would be applied when you are customizing your Workspace client.

In the createChannelSet() method defined in lc.core.Manager, the AMFChannel is created as follows:

var channel:AMFChannel = new channelClass(channelId, channelUrl);

You can add the following line just below that to set the pollingInterval to whatever value works best:

Channel.pollingInterval = xxxx;

Note: The xxxx value is in milliseconds (ms).

Additional Information

In Workspace ES3, the polling interval can be configured via the Workspace Global Administration.   Customizing Workspace is no longer required.

Just export the global settings file under Services > Workspace > Global Administration > Export Global Settings, change the value of

<client_pollingInterval>3</client_pollingInterval>

…, save the file, and re-import it.  Restart the application server.

reference: (181438652/2555685)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.0/10 (1 vote cast)

LiveCycle ES: process_name missing in Workspace for migrated tasks

Issue

You have migrated to LiveCycle ES from a LiveCycle 7 environment and notice that some of the tasks do not have a process name populated in the task view in Workspace. This problem occurs in the migration scripts, which do not correctly update the task information in the database.

Solution

This issue has been addressed in LiveCycle ES2 (9.0.0.0) and later versions.  A patch is available to solve this issue in LiveCycle ES 8.2.1.2. Contact the Adobe support team if you require this patch and ensure that it is suitable for your environment.

Additional information

The patch can only be applied during the migration process. If you have already migrated and are seeing this issue, the patch will not fix the already migrated tasks in the database. To correct this issue in this situation, manually run the following SQL:

UPDATE tb_task
SET process_name =
 (SELECT tb_process_instance.service_name
 FROM tb_process_instance
 WHERE (tb_process_instance.id = tb_task.process_instance_id))
WHERE process_name IS NULL

You should backup your database before applying the above SQL changes.

reference: (181372257/2526063)

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

LiveCycle ES: Workspace Group queue does not refresh automatically to show new tasks

Issue

If you are using group queues in Workspace ES you may notice that new tasks assigned to one of your group queues are not showing up automatically.  The user queues always refresh and show the new tasks automatically, but the group queues do not.

Solution

This issue has been fixed in ES 8.2.1.3 and later versions.  A patch is available to fix this issue in LiveCycle 8.2.1.2. Contact support if you require this patch, to ensure that it is compatible with your environment.

Additional information

If the patch does not fix the issue, check the server log for JGroups messages for more information about the possible root cause.

Also check the Global Workspace admin settings:

in LiveCycle Administration Console, click Services > LiveCycle Workspace ES > Global Administration. Under Export global settings, click Export.

Check the properties defined under server_remoteevents_JChannelConnectionProperties.  These are the connection properties for JGroups that are used to communicate between the server (on which a service event is processed by the RemoteEvent service) and all instances of Workspace ES.

If necessary, change the UDP values for the multicast IP address (mcast_addr), the multicast IP port (mcast_port), and the TTL for the multicast packets (ip_ttl). By default, the multicast IP address and port values are randomly generated and, generally, the values do not need to be changed. However, if your company has any network policies in regard to specific multicast ranges for multicast IP addresses, you sometimes need to change these values.

Note: The TTL must be greater than the number of network switches between the servers in the cluster.  However, if the value is set too high, it can cause multicast packets to travel into subnets, where they are discarded.

Do not change the remaining properties.

reference: (181372259/2542619)

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

LiveCycle ES: Queues in the Workspace To Do view are not sorted

Issue

If you are using the To Do view in Workspace ES, you may notice that the queue list is not sorted. The queues appear in the list in the order in which tasks arrive, which can be confusing and difficult to find when you are a member of many groups and shared queues.

Solution

This issue is fixed in LiveCycle ES2 (9.0.0.0), and later versions, where the queues are now sorted alphabetically, with the group queues appearing above the shared queues as follows:

Personal Queue 

Group QueueA

Group QueueB

Group QueueC

Group QueueD

…..

Shared QueueA

Shared QueueB

…..

This arrangement is the most logical behavior, since the group queues are more commonly shared and usually occur more often for one user. They also tend to change (that is, receive tasks) more often than shared queues.

Additional information

There is a patch available for LiveCycle ES 8.2.1.2, so contact Enterprise Support if you require this patch.

reference: (181421696/2544926)

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: http://livedocs.adobe.com/livecycle/8.2/wb_help/001004.html.

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: http://livedocs.adobe.com/livecycle/8.2/wb_help/001330.html.

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)