Hi,   It sounds like Apache is swapping the + with %20. Could you validate if this behavior occurs when you access it directly from an author or publisher (locally, if you are using the Cloud version)?   Can you check this thread: https://stackoverflow.com/questions/15384828/can-apache-handle-plus-s...

Hi, Are you using AEMaaCS or an on-premise version? Just FYI, AssetManager has been deprecated and is no longer recommended. You can refer to this link: Experience Manager Cloud Service - Developer Reference Material APIs. I believe the best approach is to understand what's going on between the auth...

Hi, Unfortunately, the "Filters" button cannot be overlaid because the logic for building the button is located within a granite:InternalArea (specifically, in /libs/granite/ui/components/shell/omnisearch/searchresults/searchresults.jsp). As a result, you cannot simply add another element or HTML th...

  Hi,   Could you elaborate on what you are trying to achieve? Are you looking to see which agents are full or empty? Is this specifically related to replication agents? One way to accomplish this is to build your own service (servlet) that returns the information you need in the desired...

Hi,   I have noted this behavior before, and my opinion is that this functionality is intentionally broken because you are not supposed to overlay a node directly in AEMaaCS through CRX/DE. Since the AEM SDK is designed to mimic the cloud as closely as possible, there are certain aspects that may no...

Hi,   You need to wrap those dependencies as part of your bundle so they are deployed and available at runtime. Please check these threads: https://aemconcepts.com/aem-osgi/use-3rd-party-api-or-jar-or-dependency-in-aem/  https://medium.com/aem-architect-developer-business-practitioner/understanding-...

Ah! You are right; the issue is that the "jcr:created" property is technically not part of the metadata but part of the assets themselves, which is why this tool is not exporting it. This will reduce your options. You could try relying on another metadata property instead of the "jcr:created" proper...

Hi,   I believe the options you outlined are the most viable for this scenario. I'm leaning towards the AEM Assets Post-Processing approach. Are you encountering any specific issues with any of these options?

Hi,   This seems really challenging to accomplish without coding options. Eventually, you’ll need to check each asset one by one without any custom code. Here’s how I think you could do it purely through the UI: Use the Metadata Export option (https://experienceleague.adobe.com/en/docs/experience-m...

You can't do that. The recommended approach in this situation is to combine multiple users or groups into a super group and then use that super group as a wrapper. This way you use the ootb workflow steps (dynamic step or participant step).