Difference between revisions of "Event Rules"
imported>Aeric |
imported>Aeric |
||
(11 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
< | <noinclude>'''[[File:GearIcon.png]] > Case Automation > Business Rules > Event Rules'''<br> | ||
'''[[File:GearIcon.png]] > Objects > {object} > Business Rules > Event Rules''' | |||
</noinclude> | </noinclude> | ||
Specify Rules to execute when any of the following actions are taken, and specify the order in which they execute, if there is more than one. They are typically used for [[Cases | Specify Rules to execute when any of the following actions are taken, and specify the order in which they execute, if there is more than one. They are typically used for [[Cases object]], but can be used for other objects, as well. | ||
As a simple example, suppose that you want to send someone an email whenever a case comes in for a particular customer. It's possible to do that by setting up an Event Rule--an if-condition-then-action that is triggered whenever a particular event occurs in the lifecycle of a Case. (For example, when a case is created. | As a simple example, suppose that you want to send someone an email whenever a case comes in for a particular customer. It's possible to do that by setting up an Event Rule--an if-condition-then-action that is triggered whenever a particular event occurs in the lifecycle of a Case. (For example, when a case is created. | ||
Line 8: | Line 9: | ||
'''To create such a rule:''' | '''To create such a rule:''' | ||
# Go to '''[[File:GearIcon.png]] > Case Automation > Business Rules''' | # Go to '''[[File:GearIcon.png]] > Case Automation > Business Rules > Event Rules'''<br> or '''[[File:GearIcon.png]] > Objects > {object} > Business Rules > Event Rules''' | ||
#: | #: | ||
# | # Select the Case '''Created''' event, and click '''[New Event Rule]''' | ||
#: [[File:CaseEventRuleCreate.png]] | #: [[File:CaseEventRuleCreate.png]] | ||
#: | #: | ||
Line 16: | Line 17: | ||
#::* '''Case (or Record) Created -''' A new record is created. | #::* '''Case (or Record) Created -''' A new record is created. | ||
#::* '''Case (or Record) Updated -'''Record data is modified. | #::* '''Case (or Record) Updated -'''Record data is modified. | ||
#::: | #::*: ''Note:''' Record-updated events do ''not'' occur when: | ||
#::*::* A related record is modified (unless that change causes a [[Rollup Summary Field]] to be updated). | |||
#::*::* An email is sent or a private note is added. (The change is to the [[History object]], which does not trigger rules.) | |||
#::*::* A file is uploaded. (The change is to an internal system object where attachments are stored, on which rules cannot be specified.) | |||
#::* '''Case (or Record) Deleted -''' A record is deleted. | #::* '''Case (or Record) Deleted -''' A record is deleted. | ||
#::* '''Case Closed -''' Applies only to the [[Cases object]]. | #::* '''Case Closed -''' Applies only to the [[Cases object]]. | ||
#::* '''Case Reopened -''' Applies only to the Cases object. | #::* '''Case Reopened -''' Applies only to the Cases object. | ||
#::* '''Process Start -''' The designated process has been initiated. | #::* '''Process Start -''' The designated process has been initiated. For information about the actions performed when a rule condition is satisfied, see [[Rule Actions]]. | ||
#::* '''Process Complete''' - The designated process has been finished. | #::* '''Process Complete''' - The designated process has been finished. | ||
#::* '''Case (or Record) Owner Changed -''' Someone new becomes responsible for the record. | #::* '''Case (or Record) Owner Changed -''' Someone new becomes responsible for the record. | ||
#::* '''Import -''' A record is about to be imported into this object | #::* '''Pre-Import -''' A record is about to be imported into this object | ||
#::* '''Post-Import -''' A record has just been imported into this object | |||
#::* '''Batch Import -''' An import process is about to begin importing records into this object. | #::* '''Batch Import -''' An import process is about to begin importing records into this object. | ||
#::* '''In-Mail -''' Applies only to the [[Cases object]]. Occurs when an incoming message is added to a Case. | |||
#::: This event provides additional fields related to the message, for use in Rules: | |||
#::::* '''Email To''' (<tt>__email_to_</tt>) - To address | |||
#::::* '''Email From''' (<tt>__email_from_</tt>) - From address | |||
#::::* '''Email Cc''' (<tt>__email_cc_</tt>) - Comma-separated list of "carbon copy" addresses | |||
#::::* '''Email Subject''' (<tt>__email_subject_</tt>) - Message subject | |||
#::::* '''Email Body''' (<tt>__email_body_</tt>) - Message body | |||
#::::* '''Email Reply To''' (<tt>__email_reply_to_</tt>) - Reply-to address | |||
#::::* '''Email Size''' (<tt>__email_size_</tt>) - Size of the message body | |||
#: | #: | ||
# The default for such rules is to run always. In this example, you want to run when specified conditions are met, so you make that selection and then click "Add Condition". | # The default for such rules is to run always. In this example, you want to run when specified conditions are met, so you make that selection and then click "Add Condition". |
Latest revision as of 06:06, 1 February 2018
> Case Automation > Business Rules > Event Rules
> Objects > {object} > Business Rules > Event Rules
Specify Rules to execute when any of the following actions are taken, and specify the order in which they execute, if there is more than one. They are typically used for Cases object, but can be used for other objects, as well.
As a simple example, suppose that you want to send someone an email whenever a case comes in for a particular customer. It's possible to do that by setting up an Event Rule--an if-condition-then-action that is triggered whenever a particular event occurs in the lifecycle of a Case. (For example, when a case is created.
For example, the "if" condition could check for a particular customer account, while the action will be to send an email. (Rules can do quite a lot more. But here, we want to limit ourselves to something quick and easy.)
To create such a rule:
- Go to > Case Automation > Business Rules > Event Rules
or > Objects > {object} > Business Rules > Event Rules - Select the Case Created event, and click [New Event Rule]
- The available choices include:
- Case (or Record) Created - A new record is created.
- Case (or Record) Updated -Record data is modified.
- Note:' Record-updated events do not occur when:
- A related record is modified (unless that change causes a Rollup Summary Field to be updated).
- An email is sent or a private note is added. (The change is to the History object, which does not trigger rules.)
- A file is uploaded. (The change is to an internal system object where attachments are stored, on which rules cannot be specified.)
- Note:' Record-updated events do not occur when:
- Case (or Record) Deleted - A record is deleted.
- Case Closed - Applies only to the Cases object.
- Case Reopened - Applies only to the Cases object.
- Process Start - The designated process has been initiated. For information about the actions performed when a rule condition is satisfied, see Rule Actions.
- Process Complete - The designated process has been finished.
- Case (or Record) Owner Changed - Someone new becomes responsible for the record.
- Pre-Import - A record is about to be imported into this object
- Post-Import - A record has just been imported into this object
- Batch Import - An import process is about to begin importing records into this object.
- In-Mail - Applies only to the Cases object. Occurs when an incoming message is added to a Case.
- This event provides additional fields related to the message, for use in Rules:
- Email To (__email_to_) - To address
- Email From (__email_from_) - From address
- Email Cc (__email_cc_) - Comma-separated list of "carbon copy" addresses
- Email Subject (__email_subject_) - Message subject
- Email Body (__email_body_) - Message body
- Email Reply To (__email_reply_to_) - Reply-to address
- Email Size (__email_size_) - Size of the message body
- The default for such rules is to run always. In this example, you want to run when specified conditions are met, so you make that selection and then click "Add Condition".
- When you click [Add Condition], a field chooser appears. In this case, you select the Account record associated with the case. From that record you select the Account Name, and click [Insert Field] to insert the field into the condition statement:
- The condition statement now appears in the Execution Criteria section of the Rule. You can now select the kind of comparison you want, and specify the value to compare to. (For example: XYZ Corp.)
- When you're done specifying conditions, you'll specify the actions to execute when the conditions are met. In this case, you'll choose to send an email, using the same process you used when defining a Macro.
- When done, click [Save]