Yep - I have found exactly the same issue as you. There isn't a fix for this as far as I am aware and the steps you have done is exactly the same steps as I used. I don't ever remember having this issue until the release of AEM Forms 6.3.This is also the case if you ever want to use Integrated Authe...

You should be able to find all the public dermis stuff in the aemfd client SDK [1]. The dermis APIs are located at the top of the list on the API page [2] [1] Maven Repository: com.adobe.aemfd » aemfd-client-sdk » 6.3.0 [2] AEM Forms API

If Its a static list of items, you can set the default value on the component itself by entering a value into the Default Value fielde.g. to set "Item 2" as the default:or using the Rules Editor:If its a dynamic list, you can set the value property [2] once the list is initialized [3][2] Adaptive Fo...

As Mayank Gandhi​ has already said - you have to use the AEM Forms asset services to upload your PDF for Forms Portal to see the additional metadata. Reason is, they are two different upload services and the AEM Forms asset service adds in extra metadata to the PDF. They both share the same DAM work...

That error message (ALC-XTG-032-303) is generated by the XML Form service when you try to render a PDF Form where the render version is lower than the target version specified in the XDP at design time.Check the Forms Workflow activity or the Java code you are using to ensure that you are specifying...

Some of this was explained on an old Adobe blog that seems to have disappeared now. But this was old ES4 SP1 workings, so its likely to have changed since then.There is not a lot of technical documentation on this that I have ever found. Without it we rely heavily on either asking via Adobe support ...

You are correct - these backup solutions are all manual workarounds. Unfortunately, AEM Forms doesn't version each time you make a change so you will have to manually revert your changes back.If you are creating and modifying forms on the Production Author, I would create a versioned package in Pack...

I talked a bit about versioning of Adaptive forms and what makes it so complex here: Re: Version history is not created for AEM forms If you require a version history to be always usable then I would suggest not using shared form fragments. Once a fragment is shared between two forms then you lose t...

There is actually a good breakdown of the licensing model and how it works [1]. For actual pricing you will need to contact your local Adobe office and they should work out licensing based on expected volumes, processing model and eventually number of production cores required. If you have existing ...

From memory, the guideContainer.af.internalsubmit servlet just gets the submitted data from the form before submitting to the actual submission servlet guideContainer.af.submit. I can't remember the actual reason why it is done in two parts, it was a while ago when I asked.The actual server-side val...