Reminders

Any alert that is not triggered by the occurrence of a single, specific event is called a reminder or alarm.

Typically, this type of alert involves the relationship of an object (such as a task or project) to time, or to another object.

You configure how many days in advance to send different types of reminder notifications. For example, the notifyProjectAlarmMonitorScheduledStartCondition property sets how many days before the start date of a project to send start notifications to users, and the notifyProjectAlarmMonitorTaskOverdueCondition property sets how many days after the end date of a task to notify users that a task did not finish. Alternatively, you can indicate that you do not want any notifications to be sent for a reminder type by supplying -1.

You also configure how often the system iterates through the object instances to determine whether reminder notifications need to be sent. For example, you configure Marketing Operations to send a notification 1 day before every task is scheduled to start. To determine whether any of these notifications need to be sent, Marketing Operations:

  1. Determines the current date.
  2. Compares it to the scheduled start date of every workflow task.
  3. Finds the difference.
  4. Sends a reminder for every task that has a difference of 1 day or less.

You can configure different polling periods for different types of objects. Because this process uses more system resources than the check for event-triggered notifications, the default polling period for each one is 60 seconds. You configure these properties to change the default polling period:

  • notifyProjectAlarmMonitorPollPeriod
  • notifyApprovalAlarmMonitorPollPeriod
  • notifyAssetAlarmMonitorPollPeriod

To change the default values for these properties, click Settings > Configuration > Marketing Operations > umoConfiguration > Notifications.

For information about all of the configuration properties, see the HCL® Marketing Operations Installation Guide.