Registering a new Form Action Item for the Form Container is not working as expected

[briankasingli]

For AEMaaCS, it looks like if we are trying to introduce a new form action item for the forms container, the only way to do this is by adding a new node into this structure "/libs/core/wcm/components/form/actions/*".

Now, from looking at the code, https://github.com/adobe/aem-core-wcm-components/blob/main/bundles/core/src/main/java/com/adobe/cq/wcm/core/components/internal/servlets/FormActionTypeDataSourceServlet.java:line66, it looks like it's trying to find all instances of sling:resourceType = "foundation/components/form/action", but it is not able to do so. So even if I decide to add a new custom action with the sling:resourceType under /apps/my-app/components/form/actions/customaction, this does not work. Odd enough, if I create a new node like /libs/core/wcm/components/form/actions/customaction, now I can see my new custom form action inside of the forms container component's touch ui options (for authors).

Bug Report

Current Behavior
The only way to add a new form action in the forms container is to add a new node structure under /libs/core/wcm/components/form/actions/*, and in this case, if I were to add the new structure, it would be /libs/core/wcm/components/form/actions/customaction.

Expected behavior/code
Expected, I should be able to add a new form action to the core forms container component under either

• /apps/core/wcm/components/form/actions/customaction
• /apps/my-app/components/form/actions/customaction

Environment

• Latest AEMaaCS 2023 December Version

Possible Solution

• I am not sure what the solution is, but we can't be overlaying components under /libs, that is bad practice.