Friday, 28 April 2017

Validating Adobe Experience Manager Classic UI dialog values

You can validate fields in an Adobe Experience Manager classic UI dialog with custom JavaScript logic. You can validate fields before saving the data in nodes for any dialog using the Experience Manager classic UI. In this development article, you will learn how to apply custom validations to dialog fields in the classic UI by using JavaScript.

Note: This article discusses how to access and validate dialog fields by using JavaScript. You can apply similar JavaScript logic to your own dialog fields to address your project's business requirements.


Likewise, you can validate email fields, as shown in the following illustration.




Adobe Digital Marketing Community


Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  

Thursday, 27 April 2017

Adobe Experience Manager 6.3 is Live

Adobe Experience Manager 6.3 is now live.

Here are some good resources to check out:

Adobe Experience Manager 6.3 documentation

What’s New with Experience Manager 6.3

AEM 6.3 Feature Video Landing Page

Creating your First Adobe Experience Manager 6.3 website

Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  

Wednesday, 12 April 2017

Creating an Adobe Experience Manager project using Lazybones

You can create an Adobe Experience Manager 6.3 project by using Lazybones, which is a templating language that you can use to setup an Experience Manager project. For more information, see Lazybones.
This development article walks you through an efficient path to create a new Experience Manager project. This article covers the following tasks:
  • Create an Experience Manager project by using Lazybone.
  • Setup the project using the Eclipse plug-in.
  • How to use the Experience Manager Template Editor.
  • How to use the new Experience Manager Core Components. 
  • How to overlay Core Components. 
  • Create an advanced Experience Manager component that  renders markup with HTL (Sightly) and work with the underlying logic with Sling models.


This article will be released sometime in May 2017. 

Wednesday, 5 April 2017

Creating a custom action for an Adobe Experience Manager Form component

You can create an Adobe Experience Manager (AEM) form using various form components located in the Forms Category and submit the data to a custom form action. The custom form action can send the data to an Experience Manager service that can process the data using Java application logic to meet your business requirements. For example, you can store the data in the AEM JCR, in a relational database or send the data within an email message (as a few examples). However, to keep this article simple, the custom AEM service writes the posted data to the AEM log file.

An Experience Manager form can be consumed in a mobile device or a web browser running on a desktop. For example, consider a desktop user filling out the following form.



You can build a custom form action that is invoked when an end user fills out the form and clicks the submit button. In this article, the custom form action named customFormAction is created, as shown in the following illustration.



This article steps you through how to build a custom form action that sends data to an Experience Manager service build using Java APIs. To read this development article, click https://helpx.adobe.com/experience-manager/using/form_component_customaction.html.

Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  


Tuesday, 28 March 2017

Adobe Experience Manager Additional Community Content

This blog entry lists additional content that the community will find useful.

White Papers


Community Blogs

CQ Ops (Tumblr)
AEM CQ5 Tutorials(Community Member's AEM Blog)
Adobe CQ/Adobe AEM (Community Member's AEM Blog)
Ryan Lunka's Blog (Author of AEM in a Classroom)
Daniel Klco CQ/AEM Blog(Community Member's AEM Blog)
Himanshu Jain CQ/AEM Blog(Community Member's AEM Blog)
Adobe CQ/AEM Club Blog(Community Member's AEM Blog)
CQ5 AEM TRICKS OF TRADE(Community Member's AEM Blog)


Popular Articles

   
   
   
   
   
   
           
           

Monday, 27 March 2017

Creating your First Adobe Experience Manager 6.3 website

You can develop an enterprise scale website using Adobe Experience Manager 6.3 that contains different sections, based on existing HTML, such as:

  • header
  • body
  • menu
  • footer

In this development article, you will learn the process of building AEM 6.3 templates and components and adding HTML and CSS to build a site. You will also learn how to perform these tasks:
  • modularizing the page-rendering components 
  • defining local supertypes 
  • making use of AEM supertypes

The following illustration shows the website that is build by following the steps in this article.





Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020  


Thursday, 9 March 2017

Managing multiple instances of the same Adobe Experience Manager OSGi service

When developing custom services for Adobe Experience Manager, you can define a service that can be configured using the Felix Configuration screen.


You define configuration fields that show up in the Felix configuration screen by using a @Property annotations. For example: 

@Property(description="adress to whom email is sent",value=DEFAULT_ADDRESS)
    private static final String ADDRESS = "mailservice.address";
    private String address;

You can configure your AEM service to use different configuration values. For example, you can configure 1 to many different instances of the same service. 

Assume you want to develop a custom email service that contain the following configuration values. 
  • the email address to which an email is sent
  • the email address from which the email is sent
You can configure the custom email service so that each service instance has a different value for these configuration settings. You can enter an AEM configuration value into an AEM configuration dialog, as shown here. 


In this configuration dialog, the to and from email addresses are configurable. You can configure additional configuration settings for the same service.  

When you use the custom Service within AEM, you can create a reference to the exact configuration service that you want to reference. To do this, you use the @Reference annotation and additional metadata such as: 


 @Reference(target = "(mailservice.label=InternetA)")
     MailService mailServiceA; 
     
     @Reference(target = "(mailservice.label=InternetB)")
     MailService mailServiceB;      


In the above dialog, there is a additional field named emailservice.label. You can reference the value in this field with the target value when using the @Reference annotation. 

This development article guides you through how to create an OSGi service where there are multiple configured services and how to use the  @Reference(target = "(mailservice.label=InternetA)") annotation properly.  


Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner



I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 18 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.


TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

TwitterFollow me on Twitter @smac2020