Yes, I found that flag and enabled it.  Floating fields are now working. The real problem is an "interactive" floating field.  In the PDF world, they were able to overlay and interactive field and the "#f1#            #" notation allowed it to be a fixed size during interaction.  When sent for outpu...

Ok, I found that this is a legacy/deprecated notation for floating fields - awesome that I know the problem.  Now the problem is that they use the fields in HTML5 to modify the data and floating fields are not interactive in HTML5 - ugh.  Anybody have any ideas for a workaround, that would be great.

I have a customer form that is being rendered in 6.1 and the fields appears to be behaving like floating fields.  You can see the below picture that the <period> is flush against the word SCRUBBED12.    The same XDP rendered in 6.5 is as expected - fixed width. You can see in Designer, it is not a f...

We are displaying forms using 6.5 as HTML with great success however, there are a few forms using some javascript that doesn't seem to translated. The particular line of code that seems to be acting different from PDF to HTML is this line: var root = xfa.resolveNodes("xfa.record.mynode[*]") In PDF, ...

This is officially not support in this fashion.  Please read the response from Adobe support below: I have tried to replicate this at my end and can see the same behavior. After checking this with engineering, I can confirm this is working as defined.In AEM, there is no way to associate an email id ...

Hello, I have AEM installed behind Apache as a reverse proxy.  Everything is working well.  However, there are a few specific areas of concern and I believe it might be the proxy.  I can open a form in AEM Inbox.  I click Submit.  After clicking confirm at the Confirmation window, I get the swirling...

Correct.  It was a bug.  I upgraded and it was fixed.

I am using the Send Email component in OSGI workflow.  I'm attaching a file and sending - it works. However, the file is coming across with the name of "Attachment_0_0".  I have a "literal" expression and have it configured as "dor.pdf".It is not working. Any help would be appreciated. Thanks,Charle...

Yes, I need to implement the purge, but this is not exactly what I was looking for. I fixed the problem by manually removing nodes in CRX under this node:/var/workflow/instances/server0 

I have several failed tasks in my administrator inbox that belong to workflow models that are long gone.  How can I purge them? Thanks.