Adobe Experience Manager Sites

We are setting up the integration between Experience Manager en Campaign Standard and would like to use editable templates as we do on our content pages. We are experiencing an issue when creating pages using the newly created template under /content/campaigns, the UI seems to display the classic UI even though we are asking for a touch ui based url: http://localhost:4502/editor.html/content/campaigns/brand/master/en_us/mail.htmlI also see the same issue when I allow + use one of the editable template we used for our regular site pages. How can we resolve this issue? NOTE: all of our editable templates have a core components page resourceSuperType: core/wcm/components/page/v2/page 

Hi,        I want to show same field on selection of more than one value in drop down.Suppose in dropdown, we have A,B,C,Dand i have one seperate node say 'title'I want to show this field when i select A and when i select B. As showhidetargetvalue is single valued property. i am not able to make it for multi value. I tried to make string[] for showhidetargetvalue, but it is working only for one value . please assist.

I have a client that is walking thru the setting up AEM as cloud service and it boots up and I can access Osgi, but when we try to get to the admin we get a http 500 error. They are running Java 11.  Has anyone else had an issue on running AEM as a cloud service locally?

I have trying to add the hero imagecomponent We have two options for this 1 - We can upload it from our system like this ;2 . we can drag and drop from Assets under Site Console like this:after I dragged this image I Should see it here but it does not show up here   and when I try to see the property of the component I see in  it I am not able to understand what can be the reason it is not showing on the webpage                

I've added the following dependencies to my pom file            <dependency>                <groupId>com.fasterxml.jackson.core</groupId>                <artifactId>jackson-core</artifactId>                <version>2.6.5</version>            </dependency>            <dependency>                <groupId>com.fasterxml.jackson.core</groupId>                <artifactId>jackson-annotations</artifactId>                <version>2.6.5</version>            </dependency>            <dependency>                <groupId>com.fasterxml.jackson.core</groupId>                <artifactId>jackson-databind</artifactId>                <version>2.6.5</version>            </dependency>When I start my AEM server, I constantly get the following error ..09.02.2016 11:41:55.297 *ERROR* [FelixStartLevel] ERROR: Error starting jcrinstall:/apps/ewcm/install/ewcm.global.cor

Hi All, We are facing an issue, where the images from DAM are giving 404 NOT FOUND error when accessed via Dispatcher (We are using AMS in our Project). We debugged and found that the issue is appearing as we have name of images as "abc.JPG" instead of "abc.jpg" in AEM. These images are being sent via Magento, thats the reason it has Largecase chars in the file extension (e.g. JPG).  Approach 1:We tried to make modification in "ams_publish_filters.any" file to allow an additional extension "JPG" in the "/content", but in AMS its being immutable file we are not able to modify it. Could any one suggest, how this can be overlayed and additional extension can be added in filter.any file. Approach 2:Also, I could think of an additional approach, where we modify DAM Update Asset workflow to smallcase the extension (e.g. jpg) upon upload of asset. Could anyone please suggest, which should be the preferred approach for this. Thanks..Regards,Aman 

AEM - Style System by Abstract The Style System allows a template author to define style classes in the content policy of a component so that a content author is able to select them when editing the component on a page. These styles can be alternative visual variations of a component, making the component more flexible. This eliminates the need to develop a custom component for each style or to customize the component dialog to enable such style functionality. It leads to more reusable components that can be quickly and easily adapted to the needs of content authors without any AEM back-end development. Use Case Template authors not only need the ability to configure how components function for the content authors, but also to configure a number of alternative visual variations of a component. Likewise, content authors not only need the ability to structure and arrange their content, but also to select how it is presented visually. Read Full Blog AEM - Style System Q&A Please

Creative Project and PIM Integration by Abstract If you are a marketer or creative professional, you can use Creative Project tools in Adobe Experience Manager (AEM) to manage eCommerce-related product photography and associated creative processes within your organization. In particular, you can use Creative Project to streamline the following tasks in your photo shoot workflow: Generating a photo shoot request Uploading a photo shoot Collaborating on a photo shoot Packaging approved assets Exploring Product Photo Shoot workflows Creative Project provides various project templates to meet diverse project requirements. The Product Photo Shoot Project template is available out of the box. This template includes photo shoot workflows that let you initiate and manage product photo shoot requests. It also includes a series of tasks that enable you to obtain digital images for products through appropriate review and approval processes. The template includes the following workflows: Pr

Applying Workflows to Pages by Abstract When authoring, you can invoke workflows to take action on your pages; it is also possible to apply more than one workflow. When you apply the workflow, you specify the following information: The workflow to apply. You can apply any workflow (that you have access to, as assigned by your AEM administrator). Optionally, a title that helps identify the workflow instance in a user’s Inbox. The workflow payload; this can be one or more pages. Workflows can be started from: the Sites console. when editing a page, from Page Information. Read Full Blog Applying Workflows to Pages Q&A Please use this thread to ask the related questions.

AEM - HTL Block Statements by Abstract HTML Template Language (HTL) block statements are custom data attributes added directly to existing HTML. This allows easy and unobtrusive annotation of a prototype static HTML page, converting it to a functioning dynamic template without breaking the validity of the HTML code. Block Overview HTL block plugins are defined by data-sly-* attributes set on HTML elements. Elements can have a closing tag or be self-closing. Attributes can have values (which can be static strings or expressions), or simply be boolean attributes (without a value). All evaluated data-sly-* attributes are removed from the generated markup. Identifiers A block statement can also be followed by an identifier: The identifier can be used by the block statement in various ways, here are some examples: ${navigation.title} ${isEditMode} ${child.properties.jcr:title} Hello World   Top top-level identifiers are case-insensitive (because they can be set

Access Rights Granted by Abstract User Identity Types As part of the on-boarding process, Adobe will create an Organization identifier for your company in the Adobe Identity Management System (IMS), where all your users and their permissions can be managed. Each user, who needs to be a member of this organization, and will be granted access to any of the Experience Cloud services, will need to have their own Adobe ID. To get started with an Adobe ID, please visit Manage Adobe Identity Types for detailed instructions on how to obtain an Adobe ID using one of the identity types available. Users and Roles Once Adobe has created an organization for your company, your designated administrator will be added as the first member to this organization. The administrator will be granted the administrator permissions by default, and assigned the AEM Managed Services Product, and one or more Cloud Manager Product Profiles. Please visit Add Users and Roles to learn more about how to configure an

Environments Provisioned by Abstract Environments Provisioned Provisioning During the customer on-boarding process, all the AEM cloud environments purchased by a customer will be automatically provisioned by Adobe, and linked back to their program in Cloud Manager. These AEM cloud Environments are included in every Adobe Managed Services subscription, and are usually comprised of at least one production environment, one stage environment, and optionally one or more development or test environments. Welcome Email Upon completion of the environment provisioning process, the designated customer administrator receives a welcome email with the confirmation they have been granted access to the Adobe Experience Cloud. The email contains detailed information on how to get started with the Experience Cloud services, the AEM Managed Services cloud environments, as well as the Cloud Manager self-service portal. Additionally, the email contains important information such as the Customer Success

Cloud Manager - First Time Login by Abstract Once you have setup the general configurations for Cloud Manager, you are ready to use the User Interface (UI) for Cloud Manager. NOTE Depending on the roles assigned in Cloud Manager and the state of the application, you will see different screens while using Cloud Manager UI. Logging in for the First Time Log in to the Adobe Experience Cloud and you will see the list of Programs. Select the program (for example, We.Retail Global). Once you see your program card on the landing page, select the … to see menu options available to you. Select Cloud Manager to navigate to the Cloud Manager’s Overview page. The Cloud Manager’s Overview page displays. Click Setup Program for setting the Program description and defining the Key Performance Indicators (KPIs). Read Full Blog Cloud Manager - First Time Login Q&A Please use this thread to ask the related questions.

Maven Project Version Handling by Abstract Understanding Maven Project Version Handling For stage and production deployments, Cloud Manager generates a unique, incrementing version. This version is seen on the pipeline execution details page as well as the activity page. When a build is run, the Maven project is updated to use this version and a tag is created in the git repository with that version as its name. If the original project version meets certain criteria, the updated Maven project version will merge both the original project version and the Cloud Manager generated version. The tag, however, always uses the generated version. For this merging to occur, the original project version must be formed with exactly three version segments, for example, 1.0.0 or 1.2.3, but not 1.0 or 1, and the original version must not end in -SNAPSHOT. Read Full Blog Maven Project Version Handling Q&A Please use this thread to ask the related questions.

Git Integration with Adobe Cloud Manager by Abstract For a complete overview, please review the Cloud Manager User Guide. The video series assumes a basic knowledge of git and source control management. See the additional resources below for more details on git. NOTE The steps and naming conventions outlined in this video series represent some best practices for working with a customer-managed git repository and Cloud Manager. It is expected that the conventions and workflows depicted would be adapted for individual development teams. Initial Sync First steps for synchronizing a customer-managed Git repository with Cloud Manager’s Git repository. Basic Branching Strategy Set up a basic branching strategy in order to take advantage of Cloud Manager’s production and non-production pipelines. Feature Branch Development Use a feature branch to isolate code changes in a customer-managed git repository and synchronize with Cloud Manager’s git repository in order to use a non-producti

Perficient and Adobe Insights on Manufacturing from Experience Makers Live by Abstract Earlier this month, Perficient was joined by Adobe at Experience Makers Live for an Ask the Experts session focused on manufacturing. For the conversation, we had an expert panel including Robert Sumner, Karie Daudt, and Justin Racine from Perficient accompanied by Jon Burdette and Neerav Bhansali from Adobe. With such vast experience, the panel discussed a variety of topics from strategic opinions on DTC, distributor partner relationships, personalizing experiences, transacting online, and so much more. Although the session isn’t available on-demand, we wanted to take you through some of the questions and answers provided by our panel. Q: I am considering a DTC play, what are the pros and cons of this strategic move? A: First, you need to consider whether you can handle it internally. There are a lot of considerations that need to happen in your organization as you look at it and how you are goi

How to successfully implement Adobe Target to personalize and refine your marketing by Krassimir Boyanov Abstract As a follow-up to a previous article that described four KBWEB Consult focus areas for 2021, this article will explore the third focus area, supporting integration with other Adobe Experience Cloud products. Specifically, it will discuss how Adobe Target overcomes the limitations of isolated testing, and personalize testing for every visitor to every channel. The marketing challenges that Adobe Target solves Adobe Target addresses three key marketing challenges. One challenge that marketers face is the need for personalization. Savvy customers access a firm’s marketing via multiple methods—and have high expectations. If your firm is providing the same static message on all marketing channels, customers will not respond. In other words, one size doesn’t fit all. Adobe Target provides marketers with the necessary tools to accomplish omnichannel personalization, in which e

AEM - Update Smart Crop Rect of Images in a DM Classic (Scene7 Account) by Sreekanth Choudry Nalabotu Abstract Goal This is Part-2 of Migrating the Smart Crop Settings of images in a DM Classic (Scene7) account to a different Scene7 account. Executing the standalone class apps.UpdateSmartCrops, smart crop settings of all assets in account are updated with the settings read from log all-smart-crops.csv Running the tool 1) Install Java JRE 8 2) Extract migrate-smart-crops.zip into a folder migrate-smart-crops 3) Set the following properties in migrate-smart-crops\apps\config.properties b. Set the dest scene7 account credentials in companyHandle/user/pass format (the company handle is available in AEM at location /conf/global/settings/cloudconfigs/dmscene7/jcr:content@companyHandle) eg. dest=c|1111111/user@company.com/NeverSharePassword 4) Running migrate-smart-crops/update.bat reads the smart crops from csv migrate-smart-crops/apps/all-smart-crops.csv and updates the dest Scene7

AEM - Generate Smart Crop Rect Log of Images in a DM Classic (Scene7 Account) by Sreekanth Choudry Nalabotu Abstract This is Part-1 of Migrating the Smart Crop Settings of images in a DM Classic (Scene7) account to a different Scene7 account. Executing the standalone class apps.GenerateSmartCropsLog, smart crop settings of all assets in the account (or a folder) are written to a log all-smart-crops.csv.. Running the tool 1) Install Java JRE 8 2) Extract migrate-smart-crops.zip into a folder migrate-smart-crops 3) Set the following properties in migrate-smart-crops\apps\config.properties a. when path is empty the entire account is traversed or set path to a Scene7 folder eg. EAEM/experience-aem b. Set the src scene7 account credentials in companyHandle/user/pass format (the company handle is available in AEM at location /conf/global/settings/cloudconfigs/dmscene7/jcr:content@companyHandle) eg. src=c|1111111/user@company.com/NeverSharePassword 4) Running migrate-smart-crops/fetc

Adobe Announces Major Milestone in the Adoption of AI-powered Capabilities in Adobe Experience Cloud by Ali Bohra Abstract Today, we’re excited to share that over 80% of Adobe Experience Cloud customers across our category-leading applications are now relying on AI-powered capabilities to drive their digital modernisation. Adobe Sensei, Adobe’s AI and ML technology, powers intelligent services that can easily be applied across the organisation to deliver great customer experiences. Adobe Sensei is uniquely focused on solving digital experience challenges by enhancing human creativity and intelligence to help brands create and design better content, accelerate business processes, and personalise customer experiences. Sensei-powered capabilities are built into Adobe’s enterprise applications as out-of-box functionality, while additional AI-as-a-service features can be accessed via the Adobe Experience Platform. Adobe’s turnkey solutions can be easily implemented by marketers, content s

If you have a zeal to solve problems, craft solutions, and are an expert on #AdobeExperienceManager with proficiency in core java concepts, We'd love to talk to you.Currently, open for #Bangalore and #Noida locations (INDIA).   Feel free to drop in your profiles using the link below:      Technical Product Consultant-AEM (myworkdayjobs.com)(Add source-Adobe.com)    

Hi All, I am trying to migrate the content from AEM6.0 (Oak 1.0.22) to AEM 6.5 (Oak 1.10.2). Here's what I did,install a fresh copy of AEM 6.5 (/apps/aem65/crx-quickstart/repository)get a copy of the current repository in version 6.0 (/apps/aem60/crx-quickstart/repository)Run the commandjava -Xmx4096m -jar crx2oak-1.8.10-all-in-one.jar segment-old:/apps/aem60/crx-quickstart/repository /apps/aem65/crx-quickstart/repository --datastore=/apps/aem65/crx-quickstart/repository/datastore > ~cms/aem-migration.txt &It was successful. The size is down from 62G to 54G, probably because of the different formats. Now trying to start up AEM 6.5 java -server -Xms1024m -Xmx2048m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=2048m -Djavax.net.ssl.trustStore=/apps/aem65/crx-quickstart/ssl/trusted.keystore -Djava.awt.headless=true -Xverify:none -noverify -Dsling.run.modes=author,crx3,crx3tar -jar crx-quickstart/app/cq-quickstart-6.5.0-standalone-quickstart.jar start -c crx-quickstart

CCMS: Supercharge long-form content for personalized and consistent experiencesAdobe has partnered with Forrester to evaluate content creation, management, and delivery challenges faced by organizations and found that traditional content management systems do not meet their business needs. That is why organizations are increasingly adopting a structured content management approach via a component content management system (CCMS) to address these strategic and operational gaps.This thought leadership study explores how a CCMS can offer significant benefits, lower content-related risks and provide organizations an edge in driving higher content ROI through more effective content management. Download the study here.

Advantages of AEM Assets as a Cloud Service by James Talbot Abstract Adobe Experience Manager Assets as a Cloud Service offers a cloud-native solution to manage large scale assets and handle Dynamic Media operations. In this blog post, we will look at the advantages of AEM Assets as a Cloud Service, and how Asset Microservices plays a unique role and greatly helps with performance and speed. First off, both AEM Assets as a Cloud Service and Asset Microservices are always current with the latest features. Adobe provides a daily update of the AEM Assets Base Image as well as daily hotfix releases for both AEM Assets and Asset Microservices. In addition, AEM Assets as a Cloud Service provides a monthly release of new features, while Asset Microservices provides a weekly release of new features. The architecture of AEM Assets as a Cloud Service is uniquely designed to improve Asset handling performance. A client, such as a web browser, sends an upload request to Adobe Experience Manager

In classis UI Siteadmin shows all hierarchy of files whereas in touch UI aem sites we can see only pages but not other files. How Do I enable other files? @14414417 @smacdonald