After migrating Adobe LiveCycle 7 to LiveCycle ES, the properties dialog for some of the LiveCycle 7 components do not open in imported processes in Workbench. This issue occurs particularly with components from other vendors.
In the server log file, you may find an exception similar to the following:
<Mar 18, 2009 5:38:47 PM CET> <Error> <com.adobe.workflow.AWS> <server> <LCServer1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<anonymous>> <BEA1-30E1940ABA8BD8AE228B> <> <1237394327753> <000000> <stalling action-instance: 803 with message:
com.adobe.workflow.pat.PATRuntimeException: Invalid variable type. Variable: com.adobe.workflow.template.document.DefaultVariableTemplate@5ebcf7d, Type: lc7form at com.avoka.workflow.qpac.userplus.UserPlusService.A(Unknown Source) at
com.avoka.workflow.qpac.userplus.UserPlusService.execute(Unknown Source) at
com.adobe.workflow.engine.ProcessEngineBMTBean.asyncExecuteActionCommand(ProcessEngineBMTBean.java:1878) at com.adobe.workflow.engine.adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.asyncExecuteActionCom
Most QPACs from LC7 need to be updated to be able to handle the new “lc7form” variable type. According to the documentation on the adobe site, this is a pre-requisite for using LC7 QPACs in LC ES.
On pg.4 of the doc at: http://help.adobe.com/en_US/livecycle/8.2/upgrade_changes.pdf
there is the following text:
Changes in variable types
Adobe LiveCycle Workflow 7.x supported a series of variable types that you can use in process definitions. The form variable type is renamed lc7form when you upgrade to LiveCycle ES. The upgrade willautomatically update your processes to use the new variable type name; therefore, in most cases, thechange is transparent. However, if you are using a custom component from a third-party or have created oneinternally and the QPAC makes an explicit reference to the form variable type, the QPAC must be updatedto recognize the lc7form variable type name instead. The new QPAC must then be deployed to the serverfrom Adobe LiveCycle Workbench ES.
For Adobe components, make sure you are using the latest version of the component available from the Workflow SDK. For QPACs from other vendors, please contact these vendors and request an updated QPAC which is compatible with LiveCycle ES.
To deploy the updated component:
- Copy the component jar file to a local folder on the server
- Open Workbench
- Show View -> LiveCycle 7.x components
- Right click in the LiveCycle 7.x components view, and select “Deploy new component”
- Browse to the component jar file from step 1 above
- Set the appropriate deployment properties for the component
- Click OK
You may have to close and re-open the process map in Workbench for the changes to take affect. You should now be able to open the properties dialog for the affected component activity.