Du visar hjälpinnehåll för version:

The following processes are related the collaboration (social communities) features of AEM.


Pings search engines to notify them that there is a new post to a blog.

Java class: com.day.cq.collab.blog.search.process.BlogSearchPingProcess.java

Payload: A JCR path to a blog entry.

Arguments: None.

Timeout: Respected.

Approve Comment

A process step that sets the approved property of a node to true or false. This step is used to approve user-generated comments. If the node does not have an approved property, the property is created. 

ECMAScript: /etc/workflow/scripts/collab/set_approved.ecma

Payload: A JCR path that resolves to a node.


  • Approve: Select this option to set the value of the payload's approved property to true. When unselected, the approved property is set to false

Timeout: Respected

Approve Comment Step

This step creates a work item for a participant. This step extends the Participant step, however the workflow payload is a user-generated comment.

Payload: A JCR path that resolves to a node that has a sling:resourceType of collab/commons/components/comments/comment.

Arguments: The step arguments are the same as those of the Participant step.

Timeout: Respected


Checks if a comment should be considered spam. Posts without an IP or from localhost are considered non-spam. Other posts are sent to the Akismet service for analysis. If an entry is considered spam, the process marks the resource with the propety isSpam.

Java class: com.day.cq.collab.blog.antispam.process.CheckSpamProcess.java

Payload: A JCR path to a node with resource type collab/blog/components/trackbacks or collab/commons/components/comments/comment.

Arguments: None.

Timeout: Respected.


Handles the subscription of a calendar to an event. If executed with the unsubscribe as argument, the calendar in the payload will be unsubscribed, in any other cases it will be subscribed.

Java class: com.day.cq.collab.calendar.impl.workflow.CalendarSubscriptionProcess.java

Payload: A JCR path to a calendar resource.

Arguments: optional: unsubscribe, to unsubscribe the payload calendar.

Timeout: Respected.

Flush (Replicate) Page

Calls a Dispatcher Flush replication agent to invalidate a page in the Dispatcher cache. For information about replication between publish and author instances, see Replication Agents.

ECMAScript: /etc/workflow/scripts/collab/flush_page.ecma

Payload: A JCR path that resolves to a page.


  • Agent Name: The name of the replication agent to use.

Timeout: Respected

Forum Subscription

Subscribes or unsubscribes a user for a forum topic. The user is obtained from the work item metadata. This process step is used in conjunction with the User State Toggle feature.

Java class: com.day.cq.collab.forum.impl.ForumSubscribeProcess

Payload: A forum topic.


  • Subscribe: Select this option to subscribe the user to the payload topic.
  • Unsubscribe: Select this option to unsubscribe the user from the payload topic.

Timeout: Respected.

Send Email

Sends an email message that is based on a template. You can provide the template as a property value, or specify the path to a template that is stored in the repository. 

The message template must follow the Internet Message Format that the Engineering Internet Task Force (EITF) defines. The template text is comprised of header fields (such as to, from, and subject) and the message body. The text in a header field and any part of the body can be static or dynamic. To insert text at runtime, use variables that reference a property of the workflow payload (a JCR node) or a property of the workflow:

  • ${payload.propertyname
  • ${workflowproperty}

The following workflow properties are available:

  • data.startComment: The comment provided for the workflow instance.
  • data.workflowTitle: The title of the workflow.
  • initiator.familyName: The family name property of the initiatior's user profile.
  • initiator.home: The path to the node in the repository for the initiator user.
  • initiator.id: The user id of the initiator.
  • initiator.jcr:mixinTypes: The JCR mixin types of the initiator's user profile node.
  • initiator.jcr:primaryType: The JCR primary type of the initiator's user profile node.
  • initiator.name: The name of the workflow initiator.
  • initiator.sling.resourceType: The path to the component that provides the implementation for the user profile.
  • instance.data.startComment: The comment provided for the workflow instance.
  • instance.data.workflowTitle: The title provided for the workflow instance.
  • instance.id: The path of the node that stores the workflow instance.
  • instance.state: The state of the workflow instance.
  • item.id: The id of the step instance.
  • item.node.data.PROCESS: The name of the class that implements the Send Email step component. 
  • item.node.data.PROCESS_AUTO_ADVANCE: A boolean value that indicates whether the workflow automatically advances to the next step.
  • item.node.data.template: The template literal value.

For example, the following template includes values for the email, name, userid, and password properties of the node that is used as the workflow payload:

From: GeoMetrixx Outdoors <webadmin@geometrixxoutdoors.com> To: ${payload.email} Subject: Your new Geometrixx Outdoors user account Dear ${payload.name}, Here are the details about your new user account at http://www.geometrixxoutdoors.com/. You login name is: ${payload.userid}. Your password is: ${payload.password}. Regards, Geometrixx Outdoors

Another strategy for including dynamic text is to create the template at runtime:

  • Specify the path to the template in the Send Email properties (the Email Template Path argument).
  • In a previous step of the workflow, create the template text and save the template as a node at the pre-defined path.

Java class: com.day.cq.collab.commons.SendEmailProcess

Payload: A JCR path to a node.

Arguments: Specify a value for one of the followng arguments:

  • Email Template Path: The path to the template in the repository.
  • Email Template: The template (literal value)

Timeout: Not applicable.