Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Migrating 6.1 custom forms components to 6.2

roberth55706517
Level 4
Level 4

We have some custom components we wrote to be used in 6.1 forms. First, are 6.2 form components extendable? Second, we have some JSP code that uses NodeStructureUtils.getFragPrefixString() to get the fragment prefix and set it as the fragment holder in the TLS.

Is there a document that would help me migrate some of these custom components to be compatible with 6.2?

3 Replies
rahkumar
Level 1
Level 1

Yes Existing components can be extended. You will have to create a new dialog of your custom components to be used in new touch optimized UI in forms 6.2

This article should be helpful

https://docs.adobe.com/docs/en/aem/6-2/develop/components/components-touch-optimized.html#Extending Existing Components and Dialogs

roberth55706517
Level 4
Level 4

That does seem to be the case. The problem I'm now encountering is that the ID that is assigned to the elements in the HTML portion of the form does not match the ID that is in the binding context so when the form validation runs, it cannot find the elements and they do not correctly validate.

roberth55706517
Level 4
Level 4

The problem I'm having is that the somEpxression that the validation routines save in the list of failed elements does not match the somExpression of the elements on the page so calling the gudeGridge._getGuideDomElement() with the som expression of the failed element does not resolve to an element.

We have too much messy script to control the form elements and the way the page is rendered and the items cached makes it even worse.