Overlayed Form Start component not working after migrating from AEM 6.2 to AEM 6.4 | Community
Skip to main content
Akanksha_Pratih
Level 2
Sep 12, 2018 7:15 AM UTC
Solved

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

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.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Akanksha_PratihAccepted solution
    Level 2
    Sep 17, 2018 1:54 PM UTC

    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 reply

    3 replies

    Akanksha_PratihAuthorAccepted solution
    Level 2
    Sep 17, 2018 1:54 PM UTC

    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)"

    Translate
    Akanksha_PratihAuthor
    Level 2
    Sep 14, 2018 6:33 AM UTC

    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 ?

    Translate
    smacdonald2008
    smacdonald2008
    Level 10
    Sep 13, 2018 2:36 PM UTC

    we asked internal ppl if they have thoughts here.

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...