Posts in Category "Workspace"

LiveCycle ES2: Search template returns results outside of date filter

Posted on October 10, 2011 by dmcmahon | Comments (9)

Issue

If you are using Search Templates in Workspace ES2 to search for tasks between certain dates for a particular process, you may notice that the results return tasks outside of the specified dates.

This problem occurs when using a localized Workspace and adding the Task Start date in the search template criteria as seen below:

Then you specify a date range when executing the search template in Workspace ES2:

The results returned from the localized Workspace versions are not filtered at all on date, whereas in the English Workspace they are (i.e. it only returns the results between the given dates):

Reason

This is a bug in the localized versions of LiveCycle Workspace ES2 where the results are not filtered by the date criteria specified.

You can check this by using a database logging to track what SQL statements are being sent to the database when the search template is executed.  In the localized Workspace the SQL is as follows:

SELECT  DISTINCT T0.id, T0.status, T0.step_name, T0.route_list, T0.process_name, T0.process_instance_id, T0.action_instance_id, T0.update_time, T0.create_time, T1.id, T1.type, T2.id, T2.status, T2.complete_time, T3.id, T3.workflow_principal_id, T4.id, T4.commonname, T5.id FROM tb_task T0  INNER JOIN tb_assignment T1  ON (T0.current_assignment_id = T1.id) INNER JOIN tb_process_instance T2  ON (T0.process_instance_id = T2.id) INNER JOIN tb_queue T3  ON (T1.queue_id = T3.id) INNER JOIN EDCPRINCIPALENTITY T4  ON (T3.workflow_principal_id = T4.id) INNER JOIN tb_task_acl T5  ON (T0.id = T5.task_id) WHERE (T5.user_id = ’9B365DDD-C7D4-102C-8DFF-00000A24CEC9′  AND T0.process_name = ‘Task_Forwarding/Task_Forwarding_Test’ )

whereas in the English Workspace the SQL contains the date criteria at the end:

SELECT  DISTINCT T0.id, T0.status, T0.step_name, T0.route_list, T0.process_name, T0.process_instance_id, T0.action_instance_id, T0.update_time, T0.create_time, T1.id, T1.type, T2.id, T2.status, T2.complete_time, T3.id, T3.workflow_principal_id, T4.id, T4.commonname, T5.id FROM tb_task T0  INNER JOIN tb_assignment T1  ON (T0.current_assignment_id = T1.id) INNER JOIN tb_process_instance T2  ON (T0.process_instance_id = T2.id) INNER JOIN tb_queue T3  ON (T1.queue_id = T3.id) INNER JOIN EDCPRINCIPALENTITY T4  ON (T3.workflow_principal_id = T4.id) INNER JOIN tb_task_acl T5  ON (T0.id = T5.task_id) WHERE (T5.user_id = ’9B365DDD-C7D4-102C-8DFF-00000A24CEC9′  AND T0.process_name = ‘Task_Forwarding/Task_Forwarding_Test’  AND T0.create_time >= ’2011-08-14 00:00:00′  AND T0.create_time <= ’2011-08-22 00:00:00′ )

Solution

There is a patch available for Workspace ES2 SP2 (9.0.0.2), so contact enterprise support if you require this patch.  The issue will also be fixed in future versions of Workspace (Es2 SP3, and ADEP).

reference: (182579627/2951216)

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

LiveCycle ES 8.0.1.2: Workspace memory leak using IE6 or IE7

Posted on September 6, 2010 by dmcmahon | Comments (0)

Issue

When you use Workspace ES 8.0.1.2 in Internet Explorer 6 or 7 and you log in, open an XFA form, and log out repeatedly, the memory usage increases. Usage increases between 500 KB to 3 MB when you close forms, and up to 30 MB when you log out of Workspace.

Solution

This is a bug in Workspace 8.0.1.2.  Contact Enterprise Support to obtain a patch for LiveCycle ES 8.0.1.2. Or, use LiveCycle ES 8.2.1.1 or later.

reference: (180457723/1906173)

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

Posted on March 21, 2010 by dmcmahon | Comments (0)

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: duplicate user queues appearing in Workspace ES

Posted on March 19, 2010 by dmcmahon | Comments (0)

Issue

Users have duplicate queues in Workspace in Adobe LiveCycle ES 8.2.1. The first queue is the user’s personal queue (in blue below), and the second seems to be a shared queue (in red below).

 

Reason

Duplicate queues can appear if you had a custom application in LiveCycle 7 that created more than one queue per user. By default, LiveCycle doesn’t create more than one queue per user. LiveCycle clients, like Workspace (LC ES) and FormManager (LC 7) do not support multiple queues for the same user. The workflow engine in the background does support multiple queues per person, but this functionality is rarely used.

When there are multiple queues for a user, each queue has a row with a unique ID in TB_QUEUE. The ID in the default_queue_id column is the ID of the queue that workspace always uses for that user.

Solution

Remove the duplicate (shared) queue from the TB_QUEUE table. Before deleting the queue, run the following query to ensure that there are no assignments referencing the shared queue:

Select count(*) from tb_assignment where queue_id = xxx

Where xxx is the queue ID of the queue that is not the user’s default queue. That is, the queue ID not listed in the default_queue_id column.

reference: (181496045)

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

Posted on February 22, 2010 by dmcmahon | Comments (0)

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

Posted on February 18, 2010 by dmcmahon | Comments (0)

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

Posted on February 15, 2010 by dmcmahon | Comments (0)

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

Posted on February 10, 2010 by dmcmahon | Comments (2)

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)

Workspace ES: Error 500: Null input provided: Accepted-Language null

Posted on October 13, 2009 by dmcmahon | Comments (0)

Issue

 If you are trying to access Workspace in the internet browser you may receive the following error:

An error occurred determining the locale.

Error 500: Null input provided: Accepted-Language null

This may be accompanied by the following exception in the server.log:

[2/5/08 16:35:59:984 EST] 0000003f WebApp E [Servlet Error]-[determine-locale]: 
java.lang.IllegalArgumentException: Null input provided: Accept-Language null
at com.ibm.ws.genericbnf.impl.BNFHeadersImpl.appendHeader(BNFHeadersImpl.java:470)
at com.ibm.ws.webcontainer.channel.WCCResponseImpl.addHeader(WCCResponseImpl.java:149)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.addField(SRTServletResponse.java:288)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.addHeader(SRTServletResponse.java:1534)
at javax.servlet.http.HttpServletResponseWrapper.addHeader(HttpServletResponseWrapper.java:202)
at com.ibm.ws.cache.servlet.CacheProxyResponse.addHeader(CacheProxyResponse.java:421)
at com.adobe.workspace.users.DetermineLocale.doGet(DetermineLocale.java:37)

Reason

 The workspace client code uses the browser language settings to control the locale.  Unfortunately, on the client there is no way to ask the browser for that setting.  So as a workaround, the HTML wrapper requests the determine-locale servlet from the server.  The determine-locale servlet simply returns the Accept-Language header that the browser sent.  So the string returned by determine-locale completely depends on the settings and capabilities of the client you hit that servlet from.  In this case, the browser should be sending the ‘Accept-Language’ headers so either the browser did not send this information, or it was stripped along the way.

Solution

 This has been fixed in Lc ES 8.2.1, to correctly handle the situtation where no ‘Accept-Language’ information is received from the browser/server.

reference: (1708975)

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

LiveCycle Workspace ES: how to disable/hide the complete button

Posted on May 8, 2009 by dmcmahon | Comments (0)

Issue

When working with forms in Workspace, you automatically get a complete button which often hides the submit buttons on the form.  It is a common requirement to hide this complete button, especially if you have pre-submit validation scripts on your form, or multiple submit buttons depending on the context.

Solution

You can disable this button in the following ways:

  1. You can customize the Workspace interface in Flex Builder
  2. You can modify the standard rendering services (for e.g. you can remove the route to the last two steps “Workspace enable” and “Reader extend” in the LC7UpgradeRender service)
  3. Use multipe in-direct submit buttons on the form, that contain a call to the click event of the hidden FS_SUBMIT button

Notes

The submit/complete button will still be available on the card/list view in the Workspace todo list.  This enables users to submit the form without even opening the form itself in Workspace.  In order to disable this button in the card view, you have two choices.  Firstly you can specify the ‘Form must be saved’ setting in ‘Form Data Mappings’ in Workbench.  The other option is to change the “client_routes_formViewOnly” to “true” in the workspace global settings, as described here:

http://livedocs.adobe.com/livecycle/8.2/admin_workspace/wwhelp/wwhimpl/js/html/wwhelp.htm?&accessible=true

under: Workspace Administration Help > Importing and Exporting Global Settings > Workspace ES global settings

Additional Information

To understand the situations when the complete button is displayed, and when the form submit buttons are displayed, please refer to the following description of the Inject Form Bridge service.

INJECT FORM BRIDGE

Adds javascript code to an Adobe PDF form or Adobe Acrobat form to enable it to function within LiveCycle Workspace ES. The PDF form must have been created using Adobe LiveCycle Designer ES, version 8.2, or Adobe Acrobat 7.0.5 or later.

If your process uses Adobe XML forms (XDP files), you can render the form to PDF and then use the Inject Form Bridge operation. To render to PDF, you use the renderPDFForm operation that the Forms service provides.

Workspace ES provides a Complete button that users click to submit their forms. However, forms can also include submit buttons. When the Inject Form Bridge operation is used on a form, Workspace ES either hides the submit button, or disables the Complete button.

Form design

Result

The form includes no submit button.

Workspace ES disables the Complete button and users cannot submit the form.

The form includes one submit button.

Workspace ES hides the submit button and enables the Workspace ES Complete button.

The form includes a button (indirect submit) that points to a submit button (direct submit)

Indirect-submit buttons always take precedence over direct-submit buttons, even if multiple submit buttons exist. Workspace ES always shows the indirect submit buttons.

Workspace ES hides the submit button and enables the Workspace ES Complete button.

The form includes multiple indirect-submit buttons that point to one or more direct-submit buttons.

Workspace ES disables the Workspace ES Complete button. The user must click the appropriate button on the form to submit it.

The user can still save a draft version of the form or take the form offline

The form includes either an indirect- or direct-submit button in a repeating subform.

Workspace ES excludes these buttons for submitting the form in Workspace ES.

Note: When the submit button, that was added to the form design with the Process Fields,  is hidden, the button still provides the functionality for submitting the form.

Submit requests are handled by Workspace ES, which acts as an intermediary between the LiveCycle ES server and the form. Also, forms can be used both offline and online.

reference: (180833713)

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