Posts in Category "Workbench"

LiveCycle Workbench ES: PATRuntimeException: Invalid variable type

Issue

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.PEUtil.executeAction(PEUtil.java:551) at
com.adobe.workflow.engine.ProcessEngineBMTBean.executeAction(ProcessEngineBMTBean.java:1933) at
com.adobe.workflow.engine.ProcessEngineBMTBean.asyncExecuteActionCommand(ProcessEngineBMTBean.java:1878) at com.adobe.workflow.engine.adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.asyncExecuteActionCom
...

Reason

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.

Solution

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:

  1. Copy the component jar file to a local folder on the server
  2. Open Workbench
  3. Show View -> LiveCycle 7.x components
  4. Right click in the LiveCycle 7.x components view, and select “Deploy new component”
  5. Browse to the component jar file from step 1 above
  6. Set the appropriate deployment properties for the component
  7. 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.

reference: (180802977/2302710)

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

LiveCycle ES: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.

Issue

When reading XML data into a process variable in LiveCycle ES you may receive the following exception:

Target exception: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
at bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:74)
at bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:69)
at bsh.Interpreter.eval(Interpreter.java:594)
at bsh.Interpreter.eval(Interpreter.java:682)
at bsh.Interpreter.eval(Interpreter.java:672)
at com.adobe.workflow.qpac.script.ScriptService.execute(ScriptService.java:88)

This particular exception occurred using the Script QPAC to read in the XML data using script as follows:

String clean_xml = patExecContext.getProcessDataStringValue("/process_data/myxmlbranch");

clean_xml = clean_xml.replaceAll("(<)","<");

clean_xml = clean_xml.replaceAll("(>)",">");

patExecContext.setProcessDataValue("/process_data/myxmlbranch",clean_xml);

This script works fine in LiveCycle 7, but after upgrading to LiveCycle ES, the script throws the error.

Reason

There are some unexpected characters in the XML data stream.

Solution

In this case there were quotation marks at the start and end of the XML stream.  Such characters were stripped away automatically in LiveCycle 7, but LiveCycle ES is more strict with the format of the incoming  XML.  You must remove the unexpected characters manually and then it will process the XML without problems.

Additional Information

If a LiveCycle 7.x process, that is upgraded to LiveCycle ES, includes the Script QPAC, the Script QPAC may contain script that was developed using the LiveCycle 7.x API. To ensure compatibility with LiveCycle ES, the script may need to be rewritten based on the LiveCycle ES API.

In this case the getProcessDataStringValue() and setProcessDataValue() methods of the patExecContext embedded object are available in ES just as they were in LiveCycle 7 so there were no changes necessary in the script.

reference: (180833653)

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

LiveCycle Workbench ES: QPAC properties dialog not appearing for LC7 components

Issue

When importing processes from LiveCycle7 into Workbench ES, and clicking on the LiveCycle7 component in Workbench, the properties dialog for that component may not appear. This behaviour can also be observed when attempting to drag one of these LiveCycle7 components onto a new process map in Workbench.

Reason

When the LC7 Components in Workbench have not been updated to be compatible with the ES compatibility layer, you will not see the properties dialog. Most QPACs from LC7 need to be updated for use in LC ES, especially to use the new “lc7form” variable, in place of the old LC7 “form” variable type.

This information can be found in the following document:
http://help.adobe.com/en_US/livecycle/8.2/upgrade_changes.pdf#page=4

If you analyse the QPAC JAR file and open the manifest.mf in a text editor, you can check the version. The version of Adobe’s QPACs which are compatible with ES all start with version 8.x for example “AdobeVersion: 8.2.xxx.xxx.x”. If the version of the QPAC is 7.x, then it has not been updated for use in ES. This applies to the Adobe QPACs only. Other software vendors may not use the same version numbering.

Solution

Get a version of the QPAC compatible with the LC ES compatibility layer, and deploy it in the LC7.x Components view in Workbench ES. You will then be able to view and change the properties of the activities in your LC7 imported process maps.

reference: (180802977/2302710)

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