• If the type is Email then
  • Both the subject and the content are mandatory
  • The content length is validated against the email count limit, as specified on the active communication definitions
• If the type is SMS then
  • The content is mandatory
  • The subject is not applicable
  • The content length is validated against the SMS count limit, as specified on the active communication definitions

• If the type is Email then
  • Both the subject and the content are mandatory
  • The content length is validated against the email count limit, as specified on the active communication definitions
• If the type is SMS then
  • The content is mandatory
  • The subject is not applicable
  • The content length is validated against the SMS count limit, as specified on the active communication definitions

Definition can be deleted only if the alert definition is not used by any effective or not effective workflow rules

 The name of the alert definition. The name is mandatory and unique

The alternative code of the alert definition. The alternative code is mandatory and unique and generated automatically based on the alert definition name, if not specified manually 

The description of the alert definition

The life cycle of the alert definition, which can be one of the following:

• Not Effective
• Effective

On creating a new alert definition the life cycle state is automatically set to not effective. Only effective alert definitions can be triggered through workflow rules, although not effective alert definitions can be defined in a workflow rule

The type of the alert, that will determine the media that will be used to send the alert. The following options are supported:

• Email
• SMS

The entity that will be communicated through the alert. The available options are described in the Supported Entities section. More than one alert definition can be defined for each entity

The subject of the alert. This information is mandatory and applicable only if the alert type is set to Email. Alert tags can be used while defining this information. The auto complete feature is also available of alert tags.

The content of the alert. This information is mandatory. Alert tags can be used while defining this information. The auto complete feature is also available of alert tags. The following restrictions are applied while defining the content:

• The count limit, specified on the active communication definition is applied.
• If the type is Email then the count limit defined for email is applied
• If the type is SMS then the count limit defined for SMS is applied

Icon

The WYSIWYG editor will also be available for alert content, if the type is set to Email, after it is integrated with CRM.COM

Defines a list of users that will be receiving the alert. The users can be defined in the following way:

• Alert the Created by user
• Alert the Updated by user
• Alert the Assigned to user (only if the entity is assignable i.e. activities, jobs, service requests, leads)
• Alert all Users belonging to Assigned to Unit (only if the entity is assignable i.e. activities, jobs, service requests, leads)
• Alert specific Users
• Alert Users belonging in specific Units

Defines the method that will be used to log the alerts that will be created using this alert definitions. The supported options are the following:

• No logging: If selected then no alerts will be logged
• Log Rejected Alerts only: If selected then only alerts that were rejected will be logged. This should be the Default option.
• Log all Alerts: If selected then all the alerts will be logged

Displays a list of all the workflow rules that include the specific alert definition as one of their actions. This information is read only

Includes the standard log information