Tuesday, 17 July 2018

Extending Adobe Experience Manager Core Components

You can customize Adobe Experience Manager core components by extending them and modifying the Java logic. In this article, you are going to customize the Java object used by the Title component to add some static text to the end of the title. The way the Core Components are written, they reference back end Java objects, implemented using the Sling Models framework, by interface name. For example, the Title component’s HTML references an interface named com.adobe.cq.wcm.core.components.models.Title.

When the HTL script asks for an implementation of this interface, Sling Models uses the implementation class which is associated with the nearest resource type. So, to provide a custom backing Java object, you need to create a Sling Model class which uses a closer resource type than the default.

The following illustration shows the Title component that uses a custom Java class that extends the Title core component class.


NOTE - To see this content in a Guided Journey - see part 5 here: http://scottsdigitalcommunity.blogspot.com/2018/06/guided-journey-for-using-adobe.html

Join the Experience League

To become an Experience Business, you need more than just great tools and online help. You need a partner. Experience League is a new enablement program with guided learning to help you get the most out of Adobe Experience Cloud. With training materials, one-to-one expert support, and a thriving community of fellow professionals, Experience League is a comprehensive program designed to help you become your best.

Join the Adobe Experience League by clicking this banner.




I (Scott Macdonald) am a Senior Experience League Community Manager at Adobe Systems with 20 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 AEM or other end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.
YouTube: Subscribe to the AEM Community Channel. 


Thursday, 12 July 2018

Creating an Adaptive Form custom submit action that sends email messages

You can create an Adobe Experience Manager (AEM) 6.3 form and submit the data to a custom AEM service. The custom service uses the Java MAIL API to send an email message that contains the submitted form values. Although an Adaptive Form does contain an email submission action, by creating a custom service, you can fully control the submitted data by using Java logic prior to emailing the form data. For example, you can look up a value in a database and perform business logic on the data prior to sending the data in an email message.

The following form represents the form that is created in this article.


To read this development article, check back on Wed July 18. 2018. 

Wednesday, 11 July 2018

Getting Started with AEM Forms

See these helpful AEM Articles about using AEM Forms:


·        Style an adaptive form
·        Test and publish an adaptive form




Join the Experience League

To become an Experience Business, you need more than just great tools and online help. You need a partner. Experience League is a new enablement program with guided learning to help you get the most out of Adobe Experience Cloud. With training materials, one-to-one expert support, and a thriving community of fellow professionals, Experience League is a comprehensive program designed to help you become your best.

Join the Adobe Experience League by clicking this banner.




I (Scott Macdonald) am a Senior Experience League Community Manager at Adobe Systems with 20 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 AEM or other end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.
YouTube: Subscribe to the AEM Community Channel.

Monday, 9 July 2018

[Webinar | July ] Ask the AEM Community Experts: Adobe Experience Manager - Explore Assets and Tags by using AEM APIs

Join Lokesh Shivalingaiah (two time AEM Community member of the year) and us for a deep dive session to explore and understand the available APIs for Assets and Tags within AEM along with some use cases.


Date: Tuesday, 24th July 2018

Time: 8:00 am PDT | 11:00 am EST | 8:30 pm IST

Duration: 60 Minutes


Experience League


Join the Adobe Experience League by clicking this banner.




I (Scott Macdonald) am a Senior Experience League Community Manager at Adobe Systems with 20 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 AEM or other end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel.

Friday, 29 June 2018

Guided Journey for Using Adobe Experience Manager Core Components

This Experience Manager Guided Journey is intended to educate you on using Experience Manager Core Components. 

Part 1 - Introducing Core Components




Part 2 - Core Components Architecture


Part 3 - Installing Core Components




Part 4 - How to develop a Core Proxy Component


Part 5 - How to extend the Java class for a Core Component



Join the Experience League

To become an Experience Business, you need more than just great tools and online help. You need a partner. Experience League is a new enablement program with guided learning to help you get the most out of Adobe Experience Cloud. With training materials, one-to-one expert support, and a thriving community of fellow professionals, Experience League is a comprehensive program designed to help you become your best.

Join the Adobe Experience League by clicking this banner.




I (Scott Macdonald) am a Senior Experience League Community Manager at Adobe Systems with 20 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 AEM or other end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.
YouTube: Subscribe to the AEM Community Channel.

Wednesday, 27 June 2018

Guided Journey for Using Granite Resources Types in Experience Manager Components

This Experience Manager Guided Journey is intended to educate you on creating Experience Manager components that use Granite/Coral resource types.

Part 1 - Introduce Granite/Coral Resource types



Part 2 - Convert a classic UI dialog to a Touch UI dialog that uses granite resource types


Part 3 -  Adding granite resource types to a component dialog




Part 4 - Using granite types in Sling Models




Part 5 - Using resource types in a granite/coral multi-field





Friday, 22 June 2018

Invoking an Adobe Experience Manager Custom 6.4 Workflow from a web page

You can develop an Adobe Experience Manager workflow and invoke that workflow from an Experience Manager web page. That is, you can specify information required by the workflow such as the payload (for example, a digital asset) and invoke the workflow from a page within an Experience Manager site.

In this example, assume that the use case is as follows:
  • Invoke a Servlet from a web page by clicking a button 
  • Pass an asset location (payload) and email address 
  • Invoke the Workflow from an AEM Servlet by using the Workflow API 
  • The Workflow lets a user either approve or deny the asset
  • An OR Split step is used within the  workflow and routes to different branches
  • If approved, a property on the asset is modified and an email is sent to a email recipient. 
  • If not approved, the asset is not modified and a log messaged is created 
 The following illustration shows the workflow with the OR Split step that is required to approve an asset payload.



Join the Experience League

To become an Experience Business, you need more than just great tools and online help. You need a partner. Experience League is a new enablement program with guided learning to help you get the most out of Adobe Experience Cloud. With training materials, one-to-one expert support, and a thriving community of fellow professionals, Experience League is a comprehensive program designed to help you become your best.

Join the Adobe Experience League by clicking this banner.




I (Scott Macdonald) am a Senior Experience League Community Manager at Adobe Systems with 20 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 AEM or other end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.
YouTube: Subscribe to the AEM Community Channel.