@aemdevn @Masoud_Rozati @sdouglasmc So this is what has changed and the
reason it is failing now, in AEM 6.3 the
'com.adobe.granite.xssprotection' bundle wraps the
'org.apache.sling.xss' bundle and exposes its API with two
versions:1.2.02.0.1In AEM 6.5 the decision by our R&D team was taken to
update the 'org.apache.sling.xss' API version to 2.0.1 only. Since now
the 'org.apache.sling.xss' bundle allows configuring from where the
AntiSamy policy is read, this essentially removes the need for the...
Hi Sunil,Per my understanding sorting only works for List view as of
now. The column and card views are not sortable.Overriding above paths
and adding those properties will only impact list view.
That path was for Assets only. [1] is the path for Forms&Documents. Add
property sling:hideResource and set its value to (String) true to hide
it from the Forms&Documents console[1]
/libs/fd/fm/gui/content/forms/jcr:content/views/list/columns/size
Seems working for meChange donePlease confirm if we are talking about
the same console, Assets List view in AEM or you are using some other
console in AEM Forms
[1] is the node to make the Name column sortable. To make the sorting
case insensitive, try using 'sortMode' as 'local' at [2] which is set as
'remote' by default. Refer [3] for more details[1]
/libs/dam/gui/content/commons/availablecolumns/name[2]
/libs/dam/gui/content/assets/jcr:content/views/list[3] Table — Granite
UI 1.0 documentation
The columns in Assets console are governed by [1]. To hide the Size
column change the property 'default' to 'false' at [1][1]
/libs/dam/gui/content/commons/availablecolumns/size
Hi All,The good news is, this behavior is fixed in the latest release
for AEM 6.4 which is AEM 6.4.5.0. I have validated the same at my end
and it is closing the console post saving the selected page properties.
Check 'Apache Sling Authentication Service' configuration in
/system/console/configMgr. There is means to exclude paths from
authentication using 'Authentication Requirements' field. For excluded
paths SSO login would not be triggered.
I guess you have modified your template already and [1] are resolving to
null. Try changing them to [2][1]
${item.data.workflowTitle}${item.data.startComment}[2]${model.title}${item.data.comment}
In addition to that check 'url mapping' field in 'Apache Sling Resource
Resolver Factory' configuration, there could be a mapping there leading
to the behavior. But it would impact all the urls, not just experience.
/Content will be stripped from all urls having /content. If it is
happening just for specific url check /etc/map
Please check the state of your index using [1]. In case invalid and
reindexing did not help, you might have to rebuild that index.[1] Adobe
Experience Manager Help | Using oak-run.jar to Manage Indexes in AEM
You can add the extra option to the Page Info Popover at [1]. And refer
[2] to create/trigger the workflow using the API from code, without the
need of workflow selector. I hope this helps.[1]
/libs/wcm/core/content/editor/jcr:content/content/items/content/header/items/headerbar/items/pageinfopopover/items/list/items[2]
Adobe Experience Manager Help | Invoking Adobe Experience Manager
Workflows using the AEM Java API
As per my understanding, content fragments would be good option to use
in case you wish to have global header n footer. A content fragment
could be managed from a single source and changes would be easily pushed
to all the pages without much effort.Refer:Adobe Experience Manager Help
| Using Content Fragments in AEM
Hello Everyone,As of now openJDK is not supported and yes regarding the
accessibility of Oracle JDK, Adobe is working to make them available to
all customers via a common platform.For the meanwhile, please raise a
daycare request and the Oracle JDK would be shared to you, which you can
use in your environments. Cheers
The logic to fetch or create data for TouchUI inbox is not at the front
end as in case of classicUI but at the Java side. below is the basic
flow:A request to '/aem/inbox' resolves to path
'/libs/cq/inbox/content/inbox'This renders data per [1] which creates
the html page per [2]At the same time [1] triggers a get request to
fetch the data for the inbox page [3] which is handled by a servlet [4]
and used by [2] to create the complete inbox pageFurther on logic goes
to [5] and [6] to fetch the da...
The logic to fetch or create data for TouchUI inbox is not at the front
end as in case of classicUI but at the Java side. below is the basic
flow:-A request to '/aem/inbox' resolves to path
'/libs/cq/inbox/content/inbox'-This renders data per [1] which creates
the html page per [2]-At the same time [1] triggers a get request to
fetch the data for the inbox page [3] which is handled by a servlet [4]
and used by [2] to create the complete inbox page-Further on logic goes
to [5] and [6] to fetch th...
Hi Karan,Resource Resolver Factory is the solution for your case; just
configure url mapping like [1] it will hide the configured content
hierarchy in both the cases, url and anchor tags. Check the url mapping
description in configuration for more details[1] /content/site/en/-/
In such a scenario the previous request is aborted and the error [1] is
logged depicting that the very same request is triggered again so
aborting the previous one.That being said, this should not cause any
issue to the functionality as the final/last request will succeed and
the result for the request would be displayed on the UI successfully. In
your scenario even if you trigger multiple different internal requests
on the same page, this would not be a concern as this happens only when
the ver...
Hi Nitin,In case you wish to fetch LDAP users in Java, below mentioned
few docs could be
referenced:https://coderanch.com/t/482378/engineering/list-user-groups-active-directory
http://www.nullskull.com/q/10118504/get-users-list-from-active-directory-using-java.aspx
Hi Nitin,Below are few pointers regarding the
functionality:com.day.cq.dam.core.impl.event.CommentNotificationSender.java
creates the task at
[2]com.day.cq.workflow.impl.email.TaskEMailNotificationService.java
reads the task/event and triggers the mail using the template [1]The
legacy root for the email templates was /etc/workflow/The email
templates are loaded at the bundle load/start, so any changes in the
template will only be picked and used post restart of bundle [3]As the
comments in this ...
