This page is being moved to the alfresco documentation

Notification Overview

Sending notifications is an easy way to alert users or users in groups about a folder or document in an arbitrary fashion. There are no predefined events that send off a notification - when enabled, the user can click the Send Notification action at any time. The user selects the user to notify, an optional due date, and can write a message in a WYSIWYG editor. Separate notifications are created for each user, and an email is sent to each user containing a link to the document or folder and the message.

Users who have received a notification can either click the link in the email received to view the item or log in to OCMS to view all notifications by clicking the appropriate icon in the header of the application. They can then delete the notification.

Configuring Notifications

As of OCMS 3.4, notifications require an Ad-hoc form and workflow configurations. The following steps should be used to set up notifications:

1. Configure an Ad-Hoc Form for sending a notification. For example:
   • Form Name: sendNotification
   • Attrs:
     • bpm_assignees - User Assignees - Autocomplete, repeating
     • bpm_groupAssignee - Group Assignees - Autocomplete, repeating
     • bpm_workflowDueDate - Due Date - Date, single, optional
     • bpm_comment - Comments - Textarea (with wysiwyg option checked if desired), single, optional
   • Additionally any other attributes can be added in an ad-hoc manner. Example: notification_type, etc
2. In the Workflow section, set the workflow form created in the previous step as the Start Form for the HPI Notification workflow.
3. When configuring the Send Notification action, choose the form created in step 1 in the action config.

Note - currently only one sendNotification form is supported. Future releases may enable trac-specific overrides.