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
BedrockMission!

Learn More

View all

Sign in to view all badges

Migrating 6.1 custom forms components to 6.2

Avatar

Avatar
Validate 10
Level 3
roberth55706517
Level 3

Likes

3 likes

Total Posts

101 posts

Correct Reply

7 solutions
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 5
View profile

Avatar
Validate 10
Level 3
roberth55706517
Level 3

Likes

3 likes

Total Posts

101 posts

Correct Reply

7 solutions
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 5
View profile
roberth55706517
Level 3

08-08-2016

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?

Replies

Avatar

Avatar
Level 1
rahkumar
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
rahkumar
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
rahkumar
Level 1

10-08-2016

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

Avatar

Avatar
Validate 10
Level 3
roberth55706517
Level 3

Likes

3 likes

Total Posts

101 posts

Correct Reply

7 solutions
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 5
View profile

Avatar
Validate 10
Level 3
roberth55706517
Level 3

Likes

3 likes

Total Posts

101 posts

Correct Reply

7 solutions
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 5
View profile
roberth55706517
Level 3

10-08-2016

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.

Avatar

Avatar
Validate 10
Level 3
roberth55706517
Level 3

Likes

3 likes

Total Posts

101 posts

Correct Reply

7 solutions
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 5
View profile

Avatar
Validate 10
Level 3
roberth55706517
Level 3

Likes

3 likes

Total Posts

101 posts

Correct Reply

7 solutions
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 5
View profile
roberth55706517
Level 3

10-08-2016

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.