I am sure most of the organization would use the Tag Management tools to
handle these kind of requests. It is best to load these kind of requests
through Tag Management tools (Adobe Launch (DTM), GTM, Taleo..etc). You
can easily deploy without any code deployments and have more control
over. Thanks,Singaiah
The maven architype injects the http into the pom configs. You can
create a new profile with https. Please below discussion for more info:
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/deploying-packages-to-a-secure-https-server-with-content-package/qaq-p/285613
Thanks,Singaiah
@ramaem12 By default, acs-commons provides those ones only. You'll have
to create your own custom report which is not that hard. Once you you
create the report then you can manage your columns and lot of other
data. To start:1. Create a custom report2. Copy the components from the
existing report3. Make changes to the query4. Adjust columns based on
your requirement See below articles for more
info:https://adobe-consulting-services.github.io/acs-aem-commons/features/report-builder/index.html
htt...
Please see the below articles which talks about the same
issue:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/create-offer-request-failed-error-while-syncing-an-activity-from/qaq-p/359654https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/create-offer-request-failed-error-while-syncing-an-activity-from/qaq-p/370392
Thanks,Singaiah
You can leverga the ACS-COMMONS
tool:https://adobe-consulting-services.github.io/acs-aem-tools/features/csv-asset-importer/index.html
Just set the Binary to "NO" so this process just updates the meatadata.
Thanks,Singaiah
Leveraging Launch is the best option to reduce the customization. You
just need to create a one/BU specific group one time and you can use
that going forward to maintain the permissions. Otherwise, you'll have
to develop your own custom solution which requires a lot of dev effort
plus the maintenance cost. I would recommend using the Launch.
Thanks,Singaiah
If you're on latest version on AEM, you should not see this issue.Try
below approaches:1. Make sure Default encoding is set to: utf-8 on
Apache Sling Request Parameter Handling config. 2. Try below and see if
it works: String paramValue = "yourString"; byte[] bytes =
paramValue.getBytes(StandardCharsets.ISO_8859_1); paramValue = new
String(bytes, StandardCharsets.UTF_8); Let me know if it works or not.
Thanks,Singaiah
Yeah, you should be able to add the parsys and this is very commons
requirement. The new parsys is located at:
wcm/foundation/components/parsys/newpar Yes, you should manage this in
the code and here is the sample snippet how you can include parsys in
the component:
If you use CDN then just handle this at the CDN or use below on your
Apache for blank redirects: RewriteRule
^(?i)/content/we-retail/us/en/c/(.*)$ /content/we-retail/us/en/$1
[R=301,L] The above rewrite rule will remove "c" from the url.Let me
know if you have any questions. Thanks,Singaiah
There is a huge amount of documentation on this topic. The MSM provides
a functionality to re-use the content across different languages and
maintains the relationship to the source in the form of rollout configs.
So whenever there is a change to the source, all the targets would get
updated. See below links for more detailed
info:https://docs.adobe.com/content/help/en/experience-manager-learn/sites/translation/multi-site-manager-feature-video-use.html
https://docs.adobe.com/content/help/en/expe...
You have few options: 1. You'll have to leverage the ACS Commons
versioned clientlibs or 2. Flush these clientlibs from Dispatcher/Akami
(The user might or might not see the changes immediately) depends on the
expiry headers.
This looks like its related to client-side/browser caching. If you're
looking for browser side caching, I would strongly recommend to use
either Apache or CDN (this is recommended for easier maintenance) to
pass the expiration headers for your client libraries. If you can manage
these configurations at Apache/CDN then you have more control over the
expiration headers for other files i.e. images, documents as well. Let
me know whats your requirement? Thanks,Singaiah
I think you can ignore this error. I've got the same and compared the
results from results (~27,000) from both ACS and manual query and they
are both matching. You can look at the logs if you want to debug
further. Make sure you run these queries on pre-prod environments
preferably local. Thanks,Singaiah
You can download the Target Java SDK from here:
https://github.com/adobe/target-java-sdkRelease notes on this SDK:
https://docs.adobe.com/content/help/en/target/using/implement-target/server-side/releases-target-java-sdk.html
Thanks,Singaiah
AEM Connected DAM/Connected Assets: This is to bring the assets from one
AEM instance (for instance AEM instance A) to another AEM instance (AEM
Instance B). So you'll see all the assets including videos from instance
AEM Instance A in AEM Instance B and you can use the AEM Instance A
assets on AEM Instance B
pages.https://docs.adobe.com/content/help/en/experience-manager-65/assets/using/use-assets-across-connected-assets-instances.html
Adobe Assets with Adobe Stock: Generally, organizations buy...
Hi, For question 1: Yes, that's how you expose the assetsYou can use
Asset Selector to expose the assets as a service. Please see below urls
for more
info:https://helpx.adobe.com/experience-manager/6-3/assets/using/asset-selector.htmlhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-assets-as-a-service-for-3rd-party-applications/qaq-p/280386
I would recommend to look at the code in the acs-commons and see how
they're implementing just to get an
idea:https://adobe-cons...
Hi @Parvathy_C , There is a bunch docs on integrating AEM with
Salesforce.https://docs.adobe.com/content/help/en/experience-manager-65/administering/integration/salesforce.htmlhttps://www.blueacornici.com/blog/maximize-salesforce-integration-aem/
Generally, the idea of this integration is to sync the leads between the
two systems and import the data from Salesforce to AEM ClientContext for
personolization and for reporting purpose. Thanks,Singaiah
also, whats version of AEM are you on? You first make sure you get the
right input before passing that to QueryBuilder API? Also manually query
using the same string and see if you get results.
See this thread for info:
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/special-characters-search-using-querybuilder/qaq-p/277605.
It depends on the requirement (Are you looking to leverage UUID/GUIDs?).
If you want to pre-populate the page-name in the dialog wizard, you can
do that using JS. 1. Define a clientlib - the JS (Assumping you want to
use GUID/UUID or some other IDs which can easily generated on client
side) file should inject a value into the AEM Page Name field. See
dialog validations based on jQuery if you need more info on how to do
this2. Go to your page template component (if you're using OOTB one then
over...
The QueryBuilder works on the given predicates. If you're using
non-english words and searching in those specific locales, it should
work. For example: searching "español" in /content/yourproject/es/*.
What problem are you facing or whats the requirement? Thanks,Singaiah
It depends on type of the CDN you would use. There is definitely a way
to use but you'll have to make few changes on top of SDI/SSI.For
example, you can use ESI in Akamai:
https://www.akamai.com/us/en/multimedia/documents/technical-publication/akamai-esi-faq-technical-publication.pdf
Thanks,Singaiah
