Understanding Task Notification Behavior

Task notifications are primarily intended to send e-mail messages to My webMethods users who are both assigned to a task and subscribed to a notification associated with that task. In this case, to receive and interact with task notifications, all of the following conditions must be true. The My webMethods user:

Must be assigned to the task, either directly or as a member of a user, group, or role, or have the task delegated to them.

Must be subscribed to a notification associated with the task, either as an individual user, or as a member of a group or role. If the user is to self-subscribe, the user must be granted the Subscribe to Task permission for the task application.

Must have a valid e-mail address defined as part of their My webMethods user profile.

In addition, the user must be granted, at a minimum, permission to view the task, otherwise the user will not be able to access the task even though a notification is received. If the user is to interact with the task, the user must also be granted those task application permissions.

Note:
You can remove the “assigned to” requirement for users. In this case, all subscribed users receive a notification regardless if they are assigned to the task or not. For more information, see Sending Task Notifications to Non-Assigned Users.

Notification e-mails are sent to all users who fulfill the notification conditions. For example, if three users are assigned to the task and are subscribed to a notification in the task, all three users will received notification e-mails.

When a task is delegated to another user, the delegation is equivalent to assignment for the purpose of task notification. The delegated user must fulfill all the other conditions to receive notifications. That is, the delegated user must be subscribed to the notification, have a valid e-mail address, and must be granted the permissions to view or interact with the task.

Important:
A special condition applies to My webMethods administrators, or any user who is assigned the Task Administration permission.

Any user who has the Task Administration permission and is subscribed to a task notification will always receive task notifications from the task, whether the user is assigned to the task or not.

The reason for this behavior is that it is possible to create and publish a task type that contains no assignments, which means that there will be no task assignees when the task is queued (started). Any notification event that is triggered while the task is unassigned (including the Queued event) will never generate a notification according to the default notification conditions.

To enable task administrators to be aware of event occurrences within these unassigned tasks, a task administrator can subscribe to the task’s notifications and receive notification e-mails without having to be assigned to the task.