I observe the same behavior.
On local AEM 6.5, updating asset metadata creates a new version of the asset, and CQ page.
However, on AEMaaCS instance updating asset metadata does not create a new version of the asset.
My guess is that in local AEM 6.5 the below step in the DAM XML Writeback workflo...
If the author needs to upload JS & CSS, I highly suggest to reconsider the requirement as the author shouldn't be dealing with code, doesn't sound like a good practice.
However, technically you can do this using the embed core component, as @arunpatidar mentioned, which allows the author to put in...
No problems buddy.
I tried again:
- AEM publish 6.5.11
- Configured SAML auth
- Created pages named 'Login', 'login', 'non-login') & marked them as protected ('Authentication required' enabled)
- Confirmed SAML auth being triggered when accessing the protected pages
- Restarted AEM publish
- Still s...
Typically a submitted form shouldn't be allowed to be modified by the end user, but it seems your application is allowing end users to edit a submitted form, this is the issue you're reporting right?
The OOTB forms Portal does not allow end users to edit a submitted form, have a look at this video...
Agree with @Shashi_Mulugu .
If the XML is dynamic then you can follow the below steps to creating a custom servlet:
Create a custom servlet registered by resource type (recommended): https://aem.redquark.org/2019/07/sling-servlet-04-registration-via.htmlFor more understanding of how servlet by resou...
Hey @sk09 , I'm back!
Makes sense about the Sling Authentication OSGi config.
I just tried to reproduce the issue:
- Created page: /mysite/us/en/test-auth
- Enabled Authentication from page properties
- Published the page to publisher
- Access page via AEM publish, authentication is triggered.
Hi @crich2784 ,
The error is due to no payload path provided for the workflow. I downloaded your form, reproduced the issue and was able to fix by following:
When a workflow is triggered on form submission, the form data (XML/JSON) becomes the payload for the workflow, and you kist need to prop...
Hi @uniqvaibhav ,
There's isn't an official way to reate custom components in AEM Forms. But in most cases there shouldn't be a need to create one.
Instead you can group the text and the textbox component in a Form Fragment, which the author can reuse in various forms.
Form Fragment: https://expe...
There are a number of ways to do this:
1. Page template
The custom property can be added to the page by the page template.
If you intend to have the custom property logic only for one site, it would make sense to use this approach.
2. Workflow launcher
Another way is to create a workflow launche...