• If the type is Email then Not Applicable

• Both 'Effective' or 'Not Effective' Alert Definitions can be selected and added on a Workflow Rule, but only 'Effective' Definitions are triggered by the Workflow rule to send Alerts

• Name and Alternative Code must be unique.
• Mandatory Fields must be defined.
• 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 definitionsin the 'Active' Communication Definitions.
• If the type 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
  • in the 'Active' Communication Definitions.

• Use the Alert Tags related to the entity that is selected in the Main Information section of the Definition.
• Date Tags can be used regardless of the Type of the selected entity.
  

• Name and Alternative Code must be unique.
• Mandatory Fields must be defined.
• 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 definitionsin the 'Active' Communication Definitions.
• If the type 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

• • in the 'Active' Communication Definitions.

• Use the Alert Tags related to the entity that is selected in the Main Information section of the Alert Definition.
• Date Tags can be used regardless of the Type of entity selected.

• Definition can be deleted only if

• it is not added to a Workflow Rule

• Not Applicable

• Not Applicable

• If the Alert Definition is used in one or more 'Effective' Workflow Rule, then the System displays a warning that the Definition is used by Workflow Rules and confirmation is required before setting the Definition to 'Not Effective.'

 The name of the alert definition. The name is mandatory and uniqueAlert Definition.

The alternative code of the alert definition. The alternative code Alert Definition. It is mandatory and unique and generated automatically based on the alert definition name, if not specified manually unless otherwise specified, the Alternative Codes for new entries default to the Name initials in capital letters.

The description of the alert definitionAlert Definition.

The life cycle Life Cycle State of the alert definitionAlert Definition, which can be one of the followingeither:

• Not Effective
• Effective

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

• Email
• SMS

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

• Activities
• Jobs
• Service Requests
• Subscriptions
• Reward Offers

  Status
  colour Yellow title Available from CRM.COM R11.0.0

The subject of the alertAlert. This information is mandatory and applicable only if the alert type Alert Type is set to Email. Alert  

The Mandatory information on 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 tagsAlert. The following restrictions are applied while defining the content:

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

Icon

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: No Alerts will be logged.
• Log Rejected Alerts only: Only Alerts that were rejected will be logged (default).
• Log all Alerts: All the Alerts will be logged.

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

• Alert the Created by userUser
• Alert the Updated by userUser
• Alert the Assigned to user User (only if the entity is assignable. i.e. activities, jobsActivities, service requestsJobs, leadsService Requests)
• Alert all Users belonging to the Assigned to Unit (only if the entity is assignable. i.e. activities, jobsActivities, service requestsJobs, leadsService Requests)
• Alert specific UsersspecificUsers
• Alert Users belonging in to specific Units

• .

• 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 Workflow Rules that include the specific alert definition Alert Definition as one of their actions. This information is read Read-only.

Includes the standard log information