Posts tagged "process"

LiveCycle Workbench ES3: AttributeNotFoundException trying to create a new process

Issue

If you have installed ES3 SP1 (10.0.3) to your LiveCycle ES3 server and Workbench ES3 you may encounter a problem creating new processes.  Selecting the menu item to create a new process does not have any effect.  If you look in the Workbench log file (C:\Users\<YOUR_USER_NAME>\Workbench ES2\.metadata\.log) you may notice the following exception:

!ENTRY org.eclipse.ui 4 0 2012-05-31 21:58:28.424
!MESSAGE Unhandled event loop exception
!STACK 0
ALC-DSC-110-000: com.adobe.idp.dsc.registry.endpoint.EndpointStoreException: endpoint registry failure.
Caused by: com.adobe.pof.schema.AttributeNotFoundException: Attribute: parent_oid does not exist on object-type: dsc.sc_category.
 at com.adobe.pof.schema.POFAbstractObjectType.getAttribute(POFAbstractObjectType.java:177)
 at com.adobe.pof.omapi.POFDefaultQuery.addSort(POFDefaultQuery.java:323)
    at com.adobe.pof.omapi.POFDefaultQuery.addSortAsc(POFDefaultQuery.java:372)
    at com.adobe.idp.dsc.registry.endpoint.impl.EndpointStoreImpl.getEndpointCategories(EndpointStoreImpl.java:219)
    at com.adobe.idp.dsc.registry.endpoint.impl.EndpointRegistryImpl$2.doInTransaction(EndpointRegistryImpl.java:155)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTransactionCMTAdapterBean.java:357)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew(EjbTransactionCMTAdapterBean.java:299)
    at sun.reflect.GeneratedMethodAccessor546.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)

Reason

ES3 SP1 includes some feature enhancements in Process Management.  This involved addition of new columns and tables to the existing ES3 DB schema and hence requires a DB re-initialization when running LCM.

Solution

You should always read the installation steps in the ES3 SP1 readme (link below) before attempting the installation.  In this case, you will need to re-run LCM and select the step to initialize the database.

https://www.adobe.com/products/livecycle/pdfs/lces3_sp1_readme.pdf

You can download ES3 SP1 here:

https://www.adobe.com/cfusion/entitlement/index.cfm?e=lces3_sp1

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

LiveCycle ES: NullPointerException importing a process XML into Workbench

Issue

 If you are using Workbench 8.2.1 to import a process XML, you may encounter the following error:

java.lang.NullPointerException
at com.adobe.workflow.eclipse.editors.WorkflowEditor.createPartControl(WorkflowEditor.java:610)
at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:183)
at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:153)
at com.adobe.workflow.eclipse.editors.WorkflowMultiPageEditor.createMainBranchPage(WorkflowMultiPageEditor.java:739)
at com.adobe.workflow.eclipse.editors.WorkflowMultiPageEditor.createMainBranchPage(WorkflowMultiPageEditor.java:687)
at com.adobe.workflow.eclipse.editors.WorkflowMultiPageEditor.createPages(WorkflowMultiPageEditor.java:225)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:276)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)

Reason

This error occurs when the process XML is corrupted, and in particular, when there are negative coordinates in the positioning of objects. Each object on a process/orchestration map has x- and y-coordinates to position it on the canvas. These coordinates must be positive values to appear on the canvas.  If any of these values are negative, then the object is positioned off the canvas and isn’t editable in Workbench.

This issue has been fixed in later versions of Workbench.

Solution

There is a patch for Workbench 8.2.1.2 that produces a better error message to show the user exactly what objects have issues in the process XML. You can then edit the process XML in a text editor and replace the negative value (for example, =”-12″) with a positive value (for example, =”12″).  This edit allows the process to be imported without errors.

reference: (181599834/2630027)

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

LiveCycle ES2: results missing when using a Search Template

Issue

There are no search results when using a process variable at the top of the sort order list in a Search Template in the adminui in LiveCycle ES2 SP1.

Solution

This is a bug in LiveCycle ES2 SP1.  Update to LiveCycle ES2 SP2 or later.  You can also contact Enterprise Support if you require a patch for ES2 SP1 9.0.0.1.

Additional information

To reproduce this issue:

  1. Create a search template (Services > LiveCycle Workspace ES2 > Search Template Definition) with process variables in the layout column.
  2. Put the process variable at the top of the sort order list in the sort tab of the Search Template Definition.
  3. Go to Workspace; there are no search results.
  4. Move the process variable down in the sort order list in sort tab and save the Search Template.
  5. Refresh Workspace and there are result rows in the search template.

The search result rows should appear even when the process variable is at the top of the sort order list.

reference: (181660090/2651808)

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

LiveCycle ES2: duplicate process variables in Search Template definition

Issue

When you define search templates in the adminui, some process variables are duplicated in the Criteria and Layout tabs. The duplication occurs after you switch between template names in the Identification tab.

Solution

Use LiveCycle ES2 SP2 or ES3.  Or, contact Enterprise Support to obtain a patch for ES2 SP1, 9.0.0.1.

Additional information

To reproduce this error:

  1. Create two search templates (Services > LiveCycle Workspace ES2 > Search Template Definition) with each having process variables in layout column.
  2. Switch to the other search template name in Identification tab, and switch back to the first several times. The process variable is duplicated under Process Variables heading in Criteria as well as in Layout tabs.

reference: (181648653/2651801)

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

LiveCycle ES: AdminUI does not show all process names in the process search tool

Issue

 If you are using LiveCycle ES to search for processes using the adminui, then you may notice that not all processes are listed under the “Process Name – Version” drop-down list.  Only processes which are activated in Workbench, and which have process instances in the TB_PROCESS_INSTANCE table in the database, will show up in this drop-down list.

Solution

 Check that the process is activated in Workbench, and then you can run the following SQL query to verify that there are existing process instances for that process:

select distinct service_name, count(id) from tb_process_instance

group by service_name

order by service_name

reference: (181613727)

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

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: 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: values in a LC7 SetValue expression are being lost after a process upgrade

Issue

 After upgrading a process from 7.x to 8.2 in workbench, the value expressions that existed in the 7.x SetValue activity no longer exist and appear as blank assignments in the 8.2 SetValue activity.

Example:

7.x SetValue Settings:

/process_data/myXMLVar = '<node>value</node>'

/process_data/myStringVar2 = 'test string'

/process_data/myXMLVar3 = '<node>value</node>'

8.2 SetValue Settings (post upgrade):

/process_data/myXMLVar = ''

/process_data/myStringVar2 = 'test string'

/process_data/myXMLVar3 = '<node>value</node>'

The upgrade appears to be removing XML based strings (unless escaped).

Reason

 This is a bug in LC 8.2.1.2 and is caused by the loss of XML data encoding:

- encoded XML attribute values are read from the input process action template and decoded during read by Xerces

- decoded values are rewritten as XML elements (not attribute values) and never re-encoded.

- the subsequent symptom is that the unencoded XML data is (rightly) interpreted by an XML parser, but should have been interpreted as text data.

Solution

 This issue will be fixed in Workbench ES2.  There is a patch available for LC ES 8.2.1.2, so contact enterprise support if you require this patch.

reference: (181109986/2403113)

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

LiveCycle ES: how to purge old process recordings in Workbench

Information

 Recording information is globally shared by all users.

There is an option in the workbench.ini file that controls the life span of process recordings. It is defined by default as follows:

-Dcom.adobe.workbench.recordings.remove_on_save=false

Changing the default to be ‘true’ would prune away ‘old’ recordings as they get stale.

 

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