You can hide a check box using a render condition and not make it read
only. Render conditions are evaluated server side by Granite UI
framework to show or hide a UI component. You can write a custom render
condition to hide the checkbox based on the resource type. For more
details see the following blog-
http://www.nateyolles.com/blog/2016/07/aem-granite-custom-render-conditions
You can use the Asset Ingestor or URL Asset Importer utility of ACS
commons package. More details can be found here -
https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp-tools/asset-ingestion/index.html
We tried moving the component design dialog stuff to /conf but it didn't
work. We have not yet migrated to editable templates yet and therefore
we will have to continue with the design dialogs. Also, if we keep the
design in /etc then how we can activate the design as there is no
miscadmin UI and I could not find any Touch UI equivalent.
You can configure the search forms of Assets Admin UI and add the
pattern for exclusion in excludepaths predicate property.
http://localhost:4502/libs/cq/core/content/tools/customsearch.html/libs/settings/dam/search/facets/assets/jcr:content
For more details refer this documentation -
https://experienceleague.adobe.com/docs/experience-manager-65/assets/administer/search-facets.html?lang=en#adding-an-options-predicate
I don't think it will work even if you enable the feature from UI after
customization. The backend implementation logic of Launches use
PageManager and MSM APIs so I don't think it will work on product data.
I would recommend you to do a content freeze while you are doing an
upgrade in production. When you move content or workflows from 6.4 to
upgraded instance then you basically bring in data which has not been in
place upgraded. The in place upgrade utility will make sure to update
any properties on the nodes which have changed in 6.5 version. So it
will not be a good practice to bring content from 6.4 instance after you
have done in place upgrade.
Yes it is indeed best practice to abstract this run mode concept and not
expose it in your front end logic. And for abstraction you can set a
data attribute in your HTML and the value of which can be set based on
an OSGI Configuration. The OSGI configs are read based on the runmodes
automatically by the system. So you just have to keep different values
of the data attribute in OSGI configuration for each run mode. The
system will return you the value based on the current AEM running mode
and the...
You should go with case #2 and access the stored data in subsequent
process steps using workflow history API- Example-List
historyItemList =
workflowSession.getHistory(workItem.getWorkflow());HistoryItem
currentItem = historyItemList.get(historyItemList.size() -
1);HistoryItem prevItem = currentItem.getPreviousHistoryItem();String
str = prevItem.getMetadataMap().get("watchEmails ");
Thanks guys. We got the same issue in our environment yesterday. One of
the publish instance went unresponsive and thread dumps point to
FELIX-6252. Adobe has provided the same hotfix to us. Please let us know
if you find any issues with the hotfix in your testing. It seems all AEM
installations are impacted with this and Adobe should update their 6.5.7
release page.
No you can not configure it to disable the replication. The best
solution in this case is to write custom expiry job and disable the out
of the box expiry job. One hack is to disable replicate permission of
"dynamic-media-replication" user but again it is not recommended as it
is an anti pattern to update system users which come out of the box from
AEM code.
I haven't tried myself but this might help in your use case -
https://experienceleague.adobe.com/docs/target/using/experiences/offers/about-remote-offers.html?lang=en#section_7718512D08E14121B6F6B8C38134F4BC
You need to check the workspace setup in Adobe Admin console. It seems
you have not defined any properties in the selected workspace or your
userId may not have permissions to create activities in that workspace.
For more details see this doc -
https://experienceleague.adobe.com/docs/target/using/administer/manage-users/enterprise/properties-overview.html?lang=en#section_B82EB409B67C4D9D9D20CE30E48DB1DC
1. You should connect 1D with 1P and have the sticky sessions configured
at load balancer level. This is a simple and recommended topology and it
will be easier for you to manage sticky configuration at one single
place. 2. For synchronizing content I will recommend you to use Sling
Content Distribution. However, it will be better if you can manage the
UGC outside AEM in an external storage to avoid any sync failures. But
if not possible then go with sling content distribution. [0]3. Along
with ...
You can set caching headers appropriately in apache to invalidate the
browser cache after the time to live (max-age) value expires. However,
It is not good for page performance to set low TTL values for browser
cache. Header set Cache-Control
"max-age=222" Header set Age 0
I have not verified but I guess the user should see the same offer if he
relaunches the app before the Target session times out.
https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-target#target-sessions
Could you please share more details what data you want to share with
Analytics ? If you are looking to export Marketo audiences/lists to
Analytics then you can refer to the following doc-
https://docs.marketo.com/display/public/DOCS/Send+a+List+to+Adobe+Experience+Cloud
Yes the request to servlet will be blocked as it is originated from an
external application with a different domain. To make this work you will
have to register the domain of the external application in AEM CORS OSGI
configuration and bind it to the servlet path. Once you configure CORS
then AEM will send appropriate response headers to the browser and the
browser will be allowed to make the request. Also, you will have to
enable caching of headers in dispatcher if you are caching the response
o...
I haven't tried it myself but I guess with delegation pattern also you
can just override the getExportedAllowedComponents as
getAllowedComponents is deprecated.
Javadoc-https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/reference-materials/javadoc/com/day/cq/wcm/foundation/model/responsivegrid/export/ResponsiveGridExporter.html#getExportedAllowedComponents--
Here is an example of extending the model using delegation pattern -
https://levelup.gitconnected.com/aem-extend-core-co...
Few things you can check to debug the issue- The permissions or ACLs are
appropriate for the new tag and the end user have read access to the
tags on publish instance. Use the query performance tool and click on
"Explain Query" function to find out if the query with new tag is using
the same index and have the same execution plan. Check the publisher
logs when you run the query and also when you publish the page with new
tags. You should not see any indexing errors or any errors while running
th...
You need to clear the cq:distribute property on author instance before
the PDF gets replicated back to publish instances. This is mentioned in
the documentation of reverse replication- Make sure that you clear the
cq:distribute value in your workflow, if you reactivate the content on
author to the publish, otherwise it goes in an endless loop !!!
https://helpx.adobe.com/in/experience-manager/kb/HowToUseReverseReplication.html
I will recommend you to use Sling Content distribution rather than
rev...
Instead of workflow you can write a filter to validate the file before
it gets uploaded in AEM. You can find a sample of that filter here -
http://experience-aem.blogspot.com/2018/11/aem-6420-file-decode-filter-virus-scan-to-decode-uploaded-files-for-create-asset-servlet.html
The user will see the message even before the asset is uploaded in AEM.
If you want to send event based data to Adobe Analytics you can use the
data insertion APIs. It is an alternate way of sending event data to AA
without using the javascript or client side beacons. The data insertion
APIs do not require creating any data source. You can refer to examples
here -
https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/data-insertion-api/sample_code/r_sample_http_post.md
And here is an example of data source API -
https://github.com/AdobeDocs/analytics-1.4-...
If you have enabled target extension in your app and enabled A4T in
Target then the mobile AEP SDK will track and forward the tracking data
to analytics internally. "The Analytics event in the Target extension is
AnalyticsForTarget. The SDK forwards Target's data to Analytics when A4T
is enabled in Target Services." You can find this info here -
https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-analytics/analytics-event-reference#internal-events-for-adobe-analytics
In this use case you can leverage AEM DAM as an podcast asset management
solution. You can use AEM DAM features like metadata, renditions,
taxonomy, search and filter on podcast asset objects. I would say if
there are many podcasts then it makes sense to use AEM DAM as using DAM
the business users will be able to manage and find their podcasts
easily. And think about creating a distribution workflow using which the
business users can review and approve the podcasts before they are
distributed to...
