Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Overlayed Form Start component not working after migrating from AEM 6.2 to AEM 6.4

Avatar

Level 2

Hi Experts

We have overlayed foundation form start component in AEM 6.2. After overlaying a few changes were done in the dialog, like the action id dropdown was disabled such that it always uses one specific value from dropdown options and the view data CTA still did work. Now after migrating to AEM 6.4, the View Data CTA is disabled and we are not able to move to bulk editor on click of the CTA.
On debugging found that its disabled as the action id dropdown is disabled by us. It used to work fine in 6.2 even on disabling Action Id dropdown.

Any suggestions will be highly appreciated.

1 Accepted Solution

Avatar

Correct answer by
Level 2

Found the issue, this is happening due to changes in  /libs/cq/ui/widgets/source/widgets/wcm/FormActionSelection.js

where the state of calling dialog field is passed on to the rendered dialog field.

"wi.setDisabled(this.disabled)"

View solution in original post

3 Replies

Avatar

Level 10

we asked internal ppl if they have thoughts here.

Avatar

Level 2

can it be related to

FoundationDeprecate renderReadOnly on Granite UI form componentsUI Shell 3.0 no longer uses this option

this I found in AEM 6.3 release notes.

If yes, what can be the solution ?

Avatar

Correct answer by
Level 2

Found the issue, this is happening due to changes in  /libs/cq/ui/widgets/source/widgets/wcm/FormActionSelection.js

where the state of calling dialog field is passed on to the rendered dialog field.

"wi.setDisabled(this.disabled)"