Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

gkkhatal
gkkhatal
Offline

Badges

Badges
13

Accepted Solutions

Accepted Solutions
2

Likes Received

Likes Received
6

Posts

Posts
19

Discussions

Discussions
4

Questions

Questions
15

Ideas

Ideas
0

Blog Posts

Blog Posts
1
Top badges earned by gkkhatal
Customize the badges you want to showcase on your profile
Re: OOTB privilege render condition not working to show/h... - Adobe Experience Manager 22-01-2021
Hello Arun So privilege rendercondition works fine on first load on particular path but does not work when user navigates in assets. That seems to be major drawback to the rendercondition feature. Do we have any workaround for this through any customization? Did not quite get your second part about denying access to /apps/dam/gui/content/assets/jcr:content/actions/selection/custom. Can you please elaborate? Thanks

Views

716

Likes

0

Replies

0
Re: Limitation of Metadata forms for custom MIME types - Adobe Experience Manager 13-08-2020
Hi @Vijayalakshmi_S Thanks, this worked fine for us. Thanks for the solution and the clarity. Appreciate it! ThanksGanesh

Views

445

Likes

0

Replies

0
Re: Limitation of Metadata forms for custom MIME types - Adobe Experience Manager 11-08-2020
Hi @Vijayalakshmi_S Thanks for the response. Below are the information you requested. While looking into it further, I feel the feature provided assumes that the any custom MIME types will need the inheritance and it "forces" these additional tabs and properties through inheritance. This is bit odd and it would have been nice to have a option to break the inheritance rather than having custom implementation 😞 Any ideas how we can achieve this through custom implementation. 1. I am using AEM 6.5...

Views

507

Like

1

Replies

2
Limitation of Metadata forms for custom MIME types - Adobe Experience Manager 11-08-2020
Hello All We want to create custom metadata forms for custom mimetypes. But as per current implementation, that has to be present inside "default" folder and which forces to add default tab via inheritance. Is there a way to create these forms without inheritance OR to create them outside of default folder for custom MIME type. Note that "Apply folder" will not work as we want the form based on MIME type of the asset and not based on the parent folder due to content organization of the business.

Views

550

Likes

0

Replies

4
Attaching Metadata Schema based on DITA Topics in XML Documentation Addon - Adobe Experience Manager Assets 30-06-2020
Hello All We are using XML Documentation plugin and there are company specific topics as part of specialization. We would want to attach metadata schema based on the topic and not by predefined path. How can we achieve this? Is this supported OOTB? Currently the metadata schema forms can be attached to predefined folder paths which becomes static. We want to attach different metadata schema forms based on the topic types instead of path. ThanksGanesh

Views

358

Likes

0

Replies

1
Re: Specifying arguments to UnarchiverProcess step - Adobe Experience Manager 31-05-2020
Hello @Vijayalakshmi_S, This finally worked. Thanks a lot for your time in this. Appreciate it! Just a curious question. Is there relevant documentation/info about it? Looks like I was heading a wrong direction as I was not able to find precise info. The previous approach was really extracting the zip archive so did not think of changing the appraoch, thinking there was issue in calling the arguments. Thanks again!Ganesh

Views

4.3K

Likes

0

Replies

0
Re: Specifying arguments to UnarchiverProcess step - Adobe Experience Manager 29-05-2020
Hi @Vijayalakshmi_S, I tried it. But the workflowMetadata will set the values at workflow level and not to the process step level. I tried it anyways and it shows correctly in /var/workflow/instances, but that does not work as expected and the workflow still takes default values. I tried to log the process level arguments(Set via process arguments in WF model) and this is how it shows. Note there are 2 items and the arguments are shown against PROCESS_ARGS:{PROCESS_ARGS=removeOriginal::true,upda...

Views

4.9K

Likes

0

Replies

0
Re: Specifying arguments to UnarchiverProcess step - Adobe Experience Manager 29-05-2020
29.05.2020 17:39:01.265 *INFO* [JobHandler: /var/workflow/instances/server0/2020-05-18/unzip-metadata-zip_565:/content/dam/ey/migration/Behavior.zip] com.day.cq.dam.core.process.UnarchiverProcess scan: scanning archive [/content/dam/ey/migration/Behavior.zip] and verifying configured limits 29.05.2020 17:39:01.265 *INFO* [JobHandler: /var/workflow/instances/server0/2020-05-18/unzip-metadata-zip_565:/content/dam/ey/migration/Behavior.zip] com.day.cq.dam.core.process.UnarchiverProcess scan: config...

Views

3.3K

Likes

0

Replies

0
Re: Specifying arguments to UnarchiverProcess step - Adobe Experience Manager 29-05-2020
No @hamidk92094312, there are no errors. The workflow works perfectly fine. The logs show it is taking default values. Below is the debug log:

Views

3.3K

Likes

0

Replies

0
Likes given to