Wednesday, 25 March 2015

Using Adobe Experience Manager Workflows

Workflows enable you to automate Experience Manager activities. Workflows consist of a series of steps that are executed in a specific order. Each step performs a distinct activity such as activating a page or sending an email message. Workflows can interact with assets in the repository, user accounts, and Experience Manager services. Therefore, workflows can coordinate complicated activities that involve any aspect of Experience Manager.

For example, a key application of Experience Manager is Web Content Management (WCM), which enables you to generate and publish pages to your website. This functionality is often subject to organizational processes, including steps such as approval and sign-off by various participants. These processes can be represented as workflows, which in turn can be defined within Experience Manager, then applied to the appropriate content pages.

Many useful workflow models are provided with Experience Manager. In addition, any number of custom workflow models, tailored to the specific needs of your project, can be defined using the Workflow console. A workflow is made of steps. Automated steps, also called process steps, can be defined by using either an ECMA script or a service (a Java class in a bundle). For information about creating a custom workflow step by using a Java service, see Creating custom AEM workflow steps that send email messages.


This article covers the following subjects:


  • Create an AEM workflow that activate AEM pages.
  • How to invoke the AEM workflow.
  • How to check if the workflow is successful.
  • How to invoke a workflow using workflow Launcher.
  • Workflow sessions.
  • Managing data in your workflow.
  • Monitor performance of workflows.
  • Managing workflow throughput.
To read this community article, click https://helpx.adobe.com/experience-manager/using/Workflows.html.


Adobe Digital Marketing Community

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

About the Author

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 16 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.

2 comments:

  1. Scott, how does this workflow compared to LiveCycle-defined processes?

    ReplyDelete
    Replies
    1. Similar in that you drag components from a UI and route them. AEM workflows do not have features like playback and record. However - AEM workflows support custom steps - like how LC processes support custom DSCs.
      I wote all the LC custom steps (DSC) content many years ago.

      Delete