Posts tagged "QPAC"

LiveCycle ES: com.adobe.idp.DocumentError using the UserPlus QPAC with attachments

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

Issue

The following error occurs at run-time when you use the UserPlus QPAC from Avoka with attachments in Adobe LiveCycle ES 8.2.1:

javax.ejb.EJBException: EJB Exception: : com.adobe.idp.DocumentError: The document pointing to the file 
"/mydomain/AdobeDocumentStorage/session_wfattach443760/6261454814295665168" has expired. Consider increasing 
the document disposal timeout.
 at com.adobe.idp.DocumentFileBackend.checkFileExistance(DocumentFileBackend.java:412)
 at com.adobe.idp.DocumentFileBackend.copy(DocumentFileBackend.java:419)
 at com.adobe.idp.Document.passivate(Document.java:1065)
 at com.adobe.idp.Document.passivate(Document.java:1012)
 at com.adobe.idp.Document.<init>(Document.java:565)
 at com.adobe.idp.Document.<init>(Document.java:621)
 at com.adobe.idp.DocumentStorage.persist(DocumentStorage.java:78)
 at com.adobe.idp.taskmanager.dsc.client.task.AttachmentInfoImpl.persistDoc(AttachmentInfoImpl.java:201)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsToTask(CopyAttachments.java:326)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsForward(CopyAttachments.java:291)
 at com.adobe.idp.taskmanager.dsc.service.TaskManagerServiceImpl.createTask(TaskManagerServiceImpl.java:465)
 at sun.reflect.GeneratedMethodAccessor1243.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)

Reason

Attachments are stored in the Adobe DocumentStorage directory for LiveCycle 7 and in the GDS directory for LiveCycle 8. An error occurs in LiveCycle 8 if the attachments are stored in the DocumentStorage directory, and are not available in the GDS directory.  This can occur if you have upgraded your server from LiveCycle 7 to LiveCycle ES.

Solution

Manually copy the documents from the LiveCycle 7 DocumentStorage directory to the LiveCycle ES GDS directory.

reference: (181472965)

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.

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

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

Posted on April 15, 2009 by dmcmahon | Comments (0)

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)