Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Assembler failing after form saved using ES3 designer(original works saved using ES2)

Avatar

Former Community Member

I am having an issue with a form that was created in ES2.  If you use the form created in ES2, the assembler process works fine.  Once you open the form and save it using ES3, the process fails.  Any idea what to look for, or anybody else see this behavior?  I have also created a new form using the the old form as a template and it also fails. 

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi Jeremy,

Please find attached the lca that will solve your issue

View solution in original post

13 Replies

Avatar

Employee

Hi Jostend,

Can you be more specific with what your are trying to do?

Like what are your trying to do using assembler and how the process is failing?

if possible, can you share the files and ddx that you are using?

Regards,

Sufyan

Avatar

Former Community Member

Here are the files I used. Also the DDX and document map that were passed

into the assembler. In the forms folder, the file named "nbaBaseDoc" is

the file in ES2 Designer format. This is the one that works. The file

that is named "JeremyBaseDoc" is the exact file, but saved in ES3 Designer.

I included the ddx and document map for both a successful and failure

attempt. I also included the error message that is generated in the fail

folder.

Thanks;

Jeremy

Avatar

Former Community Member

Sorry, here are the files...

On Mon, Jun 3, 2013 at 8:35 AM, Jeremy Ostendorf <jeremy.ostendorf@gmail.com

Avatar

Former Community Member

I was unable to attach the files. Here is a tiny url to my skydrive

location where I have the files...

http://sdrv.ms/ZHp41L

On Mon, Jun 3, 2013 at 8:35 AM, Jeremy Ostendorf <jeremy.ostendorf@gmail.com

Avatar

Former Community Member

Here is some additional information.

Error thrown by assember process:

Caused by: com.adobe.internal.pdfm.xfa.XFAServiceException: PDFM_S28008:

XFA Dynamic assembler failed to stitch a fragment.: Invalid node type:

ADBE_JSDebugger

The fault occurred on line 2.

After some more research today. I have found saving in ES3 designer adds

this to the file:

<!--

><destination>pdf</destination><pdf><!

><fontInfo/></pdf></agent><present><! ><pdf><!

-->

On Mon, Jun 3, 2013 at 8:39 AM, Jeremy Ostendorf <jeremy.ostendorf@gmail.com

Avatar

Employee

Hi Jeremy,

You must be extracting the XDP from PDF before passing it to Assembler for stitching. Can you please share the LCA (livecycle application) that you are using?

Regards,

Sufyan

Avatar

Former Community Member

I have created a self contained process that duplicates our issue.

Everything should be in this zip file.

http://sdrv.ms/17meY99

Avatar

Employee

Can you please share the lca.

This you can create by right-clicking the apllication in Adobe LiveCycle Workbench and click "Create New Document Service Archive" and follow the steps.

This should give you a file with extension .lca.

Share it that with me.

Regards,

Sufyan

Avatar

Former Community Member

OK, I have shared it. Thanks for your help.

Jeremy

Avatar

Employee

HI Jeremy,

We are getting this error because input PDF contains two xml tags “<ADBE_JSDebugger/> and <ADBE_JSConsole/>” which are not supported by stitch operation.

In order to get around this you can remove these from extracted XDP using setValue or an executeScript in process before sending it to assembler for stitching.

Xpath for these xml elements is /xdp/config/present/pdf/viewerPreferences/ADBE_JSDebugger and /xdp/config/present/pdf/viewerPreferences/ADBE_JSConsole

These tags are added by ES3 Designer.

Let me know if you need help in getting this work done.

Regards,

Sufyan

Avatar

Former Community Member

Could you provide an example on how to do this using the "set value"

service? Could you also provide an example how to do this using the

execute script functionality. Assume the pdf file was converted into a xdp

document named "BaseDoc".

Thanks;

Jeremy

Avatar

Correct answer by
Employee

Hi Jeremy,

Please find attached the lca that will solve your issue

Avatar

Former Community Member

Thanks for your help. This fix solved my issue.