Language availability

   

Track-It! 2022 Release 01 online technical documentation is also available in the following languages:

  • French
  • German
  • Portuguese (Brazil)
  • Spanish
  • Spanish (XL)

The displayed language depends on your browser language. However, you can change languages from the Language menu.

Configuring Business Rules

Business Rules automate actions that the application performs when certain conditions are met. You can create rules based on a combination of various conditions and actions.

You can create Business Rules that can add and modify data for records that belong to a few modules in Track-It!. You can automate actions, such as sending email notifications when a record is created, updated, or deleted based on field updates.

The following figure shows the process to configure a Business Rule:

This topic contains the following information:

Overview of Business Rules

The following video (10:20) provides an overview of Business Rules in Track-It!:



https://youtu.be/iIAqX_ev2Rw?list=PLibAMtD70sYGYdao7TNnEiuvoHy_z8t4V

Components of a Business Rule

Together, following components form a Business Rule:

ComponentDescription
Conditions

Determines the criteria after which a Business Rule is triggered.

Actions

Defines the configured actions that the application performs after the Business Rule is triggered.

Actions ScheduleDefines when the selected action must be performed.

Key features and considerations

Note the following key features and considerations:

  • Track-It! provides 20 out-of-the-box Business Rules. By default, these Business Rules, as well as any ones that you create, are inactive. You can activate a Business Rule by clearing the Inactive check box.
    By default, a new Business Rule is inactive. You must clear the Inactive check box to activate a Business Rule.
  • While configuring an action, if you enter an incorrect or invalid expression, the notification content after the expression is truncated when an email notification is sent to users. Ensure that you use valid expressions in actions.
  • If you configure multiple conditions, for a Business Rule with a combination of Created, Updated, and Deleted check boxes, the Business Rule is not executed when a record is deleted. However, if you configure multiple conditions for a Business Rule with only the Deleted checkbox selected, the Business Rule is executed as expected.
  • Although the comparison conditions are available for a text type field, BMC recommends that you do not use these conditions to configure a condition for a text type field.
  • You can enter a custom value for the Select/Enter a Value list. The Select/Enter a Value list also supports expressions and already created records for the field selected in the Select a Field list.
  • You can schedule a Business Rule to run immediately or at a later time. If a Business Rule is scheduled to run at a later time, you can specify the date and time expression to run the rule. You can also schedule a Business Rule to run repeatedly and you can define the number of repetitions that the rule must be run.
  • Use the curly brackets ({) in a text field type fields, such as Email body, to access the list of available expressions for conditions and actions.
  • When a Business Rule with the create/update action is executed, a system note is added to the record.
    For example, if a Business Rule is executed on a ticket to update the Priority field, a system note named BR_businessruleName is added to the ticket notes.
  • You can copy paste the rich text field (RTF) content to the email notification editor.
  • If you restart the IIS server, the job monitor and the email services for Business Rules stop. You must restart these services manually.
  • If you configure a Business Rule to update a ticket by updating or creating a new ticket, ensure that you configure the appropriate conditions so the Business Rule does not run into an infinite loop.

  • Attachments with file name exceeding 150 characters will not be attached through Business Rules configured for Incoming emails.

  • (2021 Release 02) If you configure a Business Rule to create a ticket via email, and select New Email - Cc Address as the Requestor Email Address in the Select a Field dialog box in the Define Actions section, make sure that your mail has only one email address in CC so that it is correctly displayed in the Requestor Email Address field and the corresponding requestor's details are displayed on the ticket.
  • If there is more than one email address in CC, all the email addresses are displayed in the Alternate Email Address field, the Requestor Email Address field is blank, and the requestor's details are not displayed on the ticket.
    If the email address in CC is not linked to any requestor, it is displayed in the Alternate Email Address field, the Requestor Email Address field is blank, and the requestor's details are not displayed on the ticket.
  • (2021 Release 02) If you configure a Business Rule to update a ticket or assignment via email, and select New Email - Cc Address as the Requestor Email Address in the Select a Field dialog box in the Define Actions section, make sure that your mail has only one email address in CC so that it is correctly displayed in the Requestor Email Address field and the corresponding requestor's details are displayed on the ticket or assignment. If there is more than one email address in CC or if the email address in CC is not linked to any requestor, the Requestor Email Address field is blank.
  • (2022 Release 01) You can format the Business Rule and SLA Send Notification message text by using the different rich text formatting options provided in the Notification details dialog box. You can also insert or directly paste inline screenshots in the notification message field. However, inserting high resolution or heavy images might lead to errors or delays in saving the Business Rule or SLA. 

Types of actions

The following actions are available for configuring Business Rules:

ActionRecord type

Send Notifications with details

New Email Received

Create a Linked Record

Important

To complete this action, you must specify the Ticket ID in the expression. An assignment is created that is linked to the Ticket ID.

Tickets
Send Notification
  • Requestors
  • Ticket Notes
  • Ticket
  • Assignment Notes
  • Assignment
  • Announcement
  • New Email Received
  • Solution
  • Asset
  • Change Request
  • Purchase Order

Create Record

Important

If you configure a Business Rule to create a ticket via email, the Requestor Email Address field mapping is displayed, by default, in the Select a Field dialog box in the Define Actions section.

  • Requestors
  • Tickets
  • Assignments
  • Announcements
  • Solutions
  • Ticket Notes
  • Assignment Notes

Update Record

Important

  • To complete this action, you must specify the record ID in the expression.
  • If you configure a Business Rule to update a ticket or assignment via email, the Requestor Email Address field mapping is displayed, by default, in the Select a Field dialog box in the Define Actions section.
  • Requestors
  • Tickets
  • Assignments
  • Announcements
  • Solutions
  • Ticket Notes
  • Assignment Notes

Supported expressions for configuring conditions and actions

You can use expressions to configure conditions and actions for Business Rules. The following table provides information about the supported expressions for configuring actions:

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

ExpressionDescription
{Blank}

Validates the condition or executes an action with NULL values.

For example, you can configure a Business Rule to create a ticket without an assigned technician and notify the system administrators with the details.

{APPSERVER}

Provides the application server name.

This expression is useful if technicians want to send an out a notification with the name of the application server.

{EVENTMETHOD}

Includes the event that triggered the notification if multiple events are selected in a condition.

{EVENTMODULE}

Identifies the module which triggers the Business Rule.

For example, you have two Business Rules for sending notifications: one for Ticket module and one for email conversation. When used in the email notification this expression identifies which Business Rule triggered the notification.

{TIVERSION}

Identifies the current Track-It! version.

{LOGGEDINTECH}

Check any of the existing Business Rule for the usage of this expression:

  • Notify technician on ticket Close
  • Notify technician on ticket Status update
  • Notify technician on ticket update by another technician
{LOGGEDINGROUP}

Identifies the group to which {LOGGEDINTECH} belongs.

If the ticket is created or updated by a technician who is not assigned to the current group, the system sends out the notification to this specific group.

{TIME}

Displays the current time of the Application server.

Use this expression to send out a notification or while updating the additional information or summary of ticket or assignment.

{TIMEZONE}

Displays the current time zone of Application server.

Use this expression to send out a notification or while updating the additional information or summary of ticket or assignment.

{VIRTUALDIR}

Displays the name of the Application server virtual directory.

Use this expression to send out a notification or while updating the additional information or summary of ticket or assignment.

{DATE}

Displays the current date of the application server.

Use this expression to send out a notification or while updating the additional information or summary of ticket or assignment.

{DATEDIFF,<Date1>,<Date2>}

Displays the difference in seconds between two database dates.

If a ticket is created with an expected due date and the time is not blank, this expression sends the notification to technician with message – “Ticket with ID {Ticket – Ticket ID} has been created and is due in next {DATEDIFF,{Ticket - Open Date & Time},{Ticket - Expected Due Date & Time}}.

{EXTRACT, <Delimiters>,<Text>}Displays the text contained by “Delimiters” in the “Text”.
For example, you can use {Extract,(),{TR,Subject}} to extract 123 from Update Call (123) in an incoming email message subject.
{SUBSTR,<Start>,<Length>,<Text>}

Truncates the string starting with a character <Start> for <n> number of characters <Length>, which is from a source string <Text>.

To place the first 500 characters of an email message into a Ticket Summary, map the expression {SUBSTR,1,500,{New Email - Message}} against Ticket Summary field on the Select a field dialog box while creating a Business Rule. This expression places the first 500 characters in Ticket Summary field and truncates the rest of the message.

{ACTIONRESULT,<Action Number>}

Allows access to the sequences of records that have been created or updated by actions in a Business Rule. The information about the sequence of operations is obtained from the {ACTIONRESULT, (# of Action)} value.

To create a ticket and also create a linked assignment to that ticket, you must know the Ticket ID of the ticket that you created to link to it with the assignment that you are creating.

{HELPDESKLINK}

Allows you to retrieve the Response URL from the email monitor settings. This expression does not require any parameters and it is not displayed in the expression list while you are configuring actions and conditions for Business Rule.

{SSLINK}Allows you to retrieve the Self Service Response URL from the from the email monitor settings. This expression does not require any parameters and it is not displayed in the expression list while you are configuring conditions for Business Rule. It is displayed while configuring actions for Business Rule.
{TRACKITMAILBOX}Translates to the outgoing email address configuration of Track-It!
{TICKETLASTNOTE}

Displays the most recent Public Ticket Note added to the ticket.

This expression is specific to Ticket and Ticket notes.

{TICKETRESOLUTIONNOTE}

Displays the most recent Resolution Note added to the Ticket.

This expression is specific to Ticket and Ticket notes.

{TICKETALLNOTES}

Displays all Public Ticket Notes added to the Ticket.

This expression is specific to Ticket and Ticket notes.

{APPROVERSWITHPENDINGDECISION}

Displays emails of all Approvers having corresponding approval records with status 'Pending Approval' and 'Pending Information'.

This expression is specific to Change Request.

{APPROVERSWITHOUTDECISION}

Displays emails of all Approvers having corresponding approval records with status 'Pending Prior Approval'.

This expression is specific to Change Request.

{APPROVERSWITHDECISION}

Displays emails of all Approvers having corresponding approval records with status 'Approved', 'Rejected' and 'No Action Required'.

This expression is specific to Change Request.

{ALLAPPROVERS}

Displays emails of all active Approvers.

This expression is specific to Change Request.

Out-of-the-box Business Rules

The following table provides information about the out-of-the-box Business Rules in Track-It!:

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Rule nameDescriptionRecord typeEnabled by default
Create a ticket when software licenses have expired (2022 Release 01)This rule creates a new ticket when the status of a software license changes to Expired.Software license created or updatedYes
Create a ticket when software licenses have reached critical level(more licenses are needed) (2022 Release 01)This rule creates a new ticket when the status of a software title changes to Approaching Critical Level Usage.

Software title created or updated

Yes
Create a ticket when software licenses are about to expire (2022 Release 01)

This rule creates a new ticket when the Expiration date and time are within 30 days of the current date for a created or updated software license.

Software license created or updatedYes
Create a ticket when software licenses are Over Utilized (under licensed) (2022 Release 01)This rule creates a new ticket when the status of a software title is changed to Over Usage (under licensed), that is, when the number of licenses installed exceeds the number of licenses owned under a software title.Software title created or updatedYes
Approve change approval via email

Approvers can approve the change approval with an email. The inbound email subject line should contain the phrase Approve Change Approval followed by the change approval number in double quotation marks. For example, Approve Change Approval "356".

New email receivedNo
Close Assignment via email (Releases earlier than 2020 Release 01)This rule allows users to close an Assignment via email. When the email subject line contains the phrase Close Assignment followed by the Assignment number in double quotation marks (for example, Close Assignment "356"), the Assignment is marked closed.New email receivedNo
Close Ticket via email (Releases earlier than 2020 Release 01)This rule allows users to close a ticket via email. When the email subject line contains the phrase Close Ticket followed by the ticket number in double quotation marks (for example, Close Ticket "356"), the ticket is marked closed.New email receivedNo
Create new ticket via email with any subject

This rule creates a new ticket for all incoming email messages that do not match an email policy or belong to an existing email conversation.

Important

We recommend that the subject line of emails that you send to the Track-It! Incoming Mailbox not exceed 150 characters.

New email receivedYes
Create new Ticket via email with subject "Open Ticket" (Releases earlier than 2020 Release 01) This rule creates a new ticket whenever an email subject starts with the phrase Open Ticket. The rest of the email subject will be used for the ticket summary.New email receivedNo
Get Ticket information via email (Releases earlier than 2020 Release 01)If an inbound email subject line contains the phrase Ticket Status followed by the ticket number in double quotation marks (for example, Ticket Status "123"), the system sends back an email message with the current status and other information about that ticket.New email receivedNo
Notify approver on change approval create

When a change approval becomes active, an email is sent to the approver.

Change Approval created or updatedYes
Notify requestor on asset ownership (Releases earlier than 2020 Release 01)When asset ownership is assigned to a requestor, an email is sent to that requestor.Asset created or updatedNo
Notify requestor on ticket close

When a help desk ticket is closed, an email is sent to the requestor of that ticket.

Ticket updatedYes

Notify requestor on ticket create

When a help desk ticket is created, an email is sent to the requestor of that ticket.

Ticket createdYes
Notify requestor on ticket updateWhen a help desk ticket is modified, an email is sent to the requestor of that ticket.Ticket updatedYes
Notify the approver on change approval assignmentWhen a change approval is assigned to an approver, an email is sent to that approver.Change Approval updatedYes
Notify the requestor on ticket status update

When the Status of a help desk ticket is modified, an email is sent to the requestor of that ticket.

Ticket updatedYes
Notify technicians and approvers on change request final decision

When a final decision is made on the change approval, an email with the final decision is sent to the technicians and approvers.

Change Request updatedYes
Notify technician and approvers when change request is overdue

When the due date of an active change request has passed with an impending decision, an email is sent to the assigned technician and approvers.

Change Request createdYes
Notify technician on ticket assignment

When a help desk ticket is assigned to a help desk Technician, an email is sent to that Technician to notify them.

Ticket created or updatedYes
Notify the technician on ticket close (Releases earlier than 2020 Release 01)When a ticket is closed by a Technician other than the assigned Technician, an email is sent to the assigned Technician to inform them that the ticket has been closed.Ticket updatedNo
Notify the technician when the ticket's due date is approachingWhen the date and time are within 2 hours of the Due Date for a ticket, a warning email is sent to the assigned technician.Ticket created or updatedNo
Notify the technician when the ticket's due date is overdue

When the Due Date for a ticket passes and the ticket is not completed, an email is sent to the assigned technician and the ticket is reassigned to the technician specified as the Escalate to Technician.

Ticket created or updatedNo
Notify the technician when the ticket's expected fix date is approaching

When the date and time are within 2 hours of the Expected Fix Date for a ticket, an email is sent to the assigned technician to warn them.

Ticket created or updatedNo
Notify the technician when the ticket's expected response date is approaching

When the date and time are within 2 hours of the Expected Response Date for a ticket and no response has been made, an email is sent to the assigned technician to inform them.

Ticket created or updatedNo
Notify Technician on Ticket Status update (Releases earlier than 2020 Release 01)When the status of a help desk ticket is updated, an email is sent to the assigned technician to notify them.Ticket updatedNo
Notify the technician on ticket update by other technician

When a help desk ticket is updated by a technician other than the technician assigned to that ticket, an email is sent to that technician to notify them.

Ticket updatedYes
Notify the technician when the ticket's expected fix date is overdueWhen the Expected Fix Date for a ticket has passed, an email is sent to the assigned technicians to inform them.Ticket created or updatedNo
Notify the technician when the ticket's expected response date is overdue

When the Response Date for a ticket passes and there has been no response entered by the technician, an email is sent to the assigned technician and the ticket is reassigned to the technician specified as the Escalate to Technician.

Ticket created or updatedNo
Reject change approval via email

Approvers can reject the change approval with an email. The incoming email subject line should contain the phrase Reject Change Approval followed by the change approval number in double quotation marks. For example, Reject Change Approval "356".

New email receivedNo
Update Ticket via email (Releases earlier than 2020 Release 01)When an incoming email contains the phrase Update Ticket followed by the ticket number in double quotation marks (for example, Update Ticket "123"), the content of the email body is recorded as a new note in the specified ticket.New email receivedNo

Defining a Business Rule

Perform the following steps to define a Business Rule:

  1. On the header bar, expand the hamburger menu  and select Configuration.
  2. Click SLAs and Business Rules and then click Business Rules.
  3. On the Business Rules page, click New.
  4. In the Add Business Rule dialog box, in the Business Rule Name field, enter a name.
  5. To activate the Business Rule, clear the Inactive check box.
  6. In the Business Rule Description field, enter a brief description about the Business Rule.
  7. In the Define Conditions section, perform these steps:

    1. From the When list, select an appropriate option, such as Ticket.
    2. Based on the Business Rule that you want to configure, select one or more of the following check boxes:
      • Created
      • Updated
      • Deleted

        Important

        You cannot select multiple options with Deleted. Deleting a record must be a stand-alone condition.

    3. From the Select a Field list, select a field that you want to use to configure the Business Rule, such as Status.

      Important

      • If you configure a Business Rule to close a ticket and if this ticket has open linked assignments, then only the ticket is closed and the linked assignments are not closed.
      • If you configure a Business Rule to close a Parent ticket and if this Parent ticket has open Child tickets, then the Child tickets are also closed.
    4. From the Select a Condition list, select a required condition.
    5. Based on the condition that you select, from the Select/Enter a Value list, select or enter a field value.
      You can enter a custom value; use { to access the list of expressions, or select an already created value from the list.
    6. (Optional) To add another condition, click and repeat step 7.a through step 7.e.
    7. (Optional) To delete a condition, click .
  8. Click the Define Actions section and perform these steps:

    1. From the Select an Action list, select an appropriate action that the Business Rule must perform, such as Create Record.
    2. From the Select Record Type list, select an appropriate value, such as Asset.
    3. Click Select/Edit Fields to select or edit a field value based on the action and record type that you selected.
      Select and edit values in the following dialog box:

      Select appropriate values from the Select a Field, the Select a value from, and the Select/Enter a Value list to configure the action that the Business Rule must complete.
      • (2021 Release 02) While defining an action, if you select the record type as Ticket from the Select Record Type list, then the following dialog box is displayed when you click Select/Edit Fields:

        From the Select a Field list, select an appropriate value from the following options:
        • [Use a Template]

          If you select [Use a Template], the Select a value from list is disabled. 
          The Select/Enter a Value list displays all the active ticket template names only. Select the appropriate template to pre-populate fields within the ticket record when the Business Rule is applied. All the records linked to the selected template, such as assignments, notes, or attachments, are created and linked to the ticket.

          Important

          • All active ticket templates are visible to all users, even those without access to those templates.
          • Any manually added field value takes precedence over the predefined template value.
          • The selected template is applied to a ticket irrespective of template group permissions.
          • When you use a Business Rule to apply template values to a ticket record, additional logs are displayed in the TemplateLinks_yyyy-mm-dd.log file.
          • If a template contains any inactive field values, then applying a Business Rule populates the ticket record with those inactive values.
          • If a template contains any deleted field values, then applying a Business Rule does not create a ticket record.
        • Any other value from the Select a Field list
          If you select a value other than [Use a Template] from the Select a Field list, the Select a value from list is enabled and the Select/Enter a Value field lists all the available values. You can configure the action that the Business Rule must complete.
      • While defining an action, if you select the action as Update Record in the Select an Action list and select the record type as Update Ticket Values from the Select Record Type list, then the following dialog box is displayed when you click Select/Edit Fields:

        From the Select a Field list, select an appropriate value from the following options:
        • [Use a Template]

          If you select [Use a Template], the Use a value or an expression list is disabled. 
          The Select/Enter a Value list displays all the active ticket template names only. Select the appropriate template to update the fields within the ticket record when the Business Rule is applied. All the records linked to the selected template, such as assignments, notes, or attachments, are created and linked to the ticket.

          Important

          • All active ticket templates are visible to all users, even those without access to those templates.
          • Any manually added field value takes precedence over the predefined template value.
          • The selected template is applied to a ticket irrespective of template group permissions.
          • When you use a Business Rule to apply template values to a ticket record, additional logs are displayed in the TemplateLinks_yyyy-mm-dd.log file.
          • If the Business Rules updating the ticket has the same template as the ticket, then linked records are not created again. So any linked records added to the template later are also not created.
          • If a template contains any inactive field values, then applying a Business Rule updates the ticket record with those inactive values.
          • If a template contains any deleted field values, then applying a Business Rule does not update the ticket record.
        • Any other value from the Select a Field list
          If you select a value other than [Use a Template] from the Select a Field list, the Use a value or an expression list is enabled and the Select/Enter a Value field lists all the available values. You can configure the action that the Business Rule must complete.
    4. To add configured action, click .

    5. (Optional) To add multiple actions, repeat step 8.a through step 8.d.
    6. (Optional) To delete an action, click .
  9. Click the Define Actions Schedule section, perform these steps:

    1. For the When to perform the actions setting, select one of the following options: 
      • Immediately
      • At a later time
    2. If you select the At a later time option, perform these steps:
      1. Set the time at which you want to run the Business Rule.
        For example, 2 hours After the Open Date.
      2. To set a recurrence for the Business Rule, in the Repeat field, enter a value and set the duration.
    3. From the Time Zone list, select a preferred time zone in which you want to run the Business Rule.
    4. From the Work Schedule list, select a work schedule.
  10. Click Save.

Prerequisites for executing a Business Rule

To ensure that the defined Business Rules are executed, the following prerequisites must be met:

  • Ensure that the Job Monitor service is running.
  • Configure the Email settings. For more information, see Configuring emails.
  • If you are using the SMTP protocol, ensure that the SMTP service is running.
  • To execute the Business Rules with the send notification with details action, the email service must be running.

Configuring advanced Business Rules

The following video (16:22) provides information about configuring advanced Business Rules in Track-It!:



https://youtu.be/66xI1Smq9m8?list=PLibAMtD70sYGYdao7TNnEiuvoHy_z8t4V

Scenario: Define a Business Rule to update the priority of a ticket when the ticket is assigned to John Smith

To define a business rule to update the priority of a ticket when it is assigned:

  1. On the header bar, expand the hamburger menu  and select Configuration.
  2. Click SLAs and Business Rules and then click Business Rules.
  3. On the Business Rules page, click New.
  4. In the Add Business Rule dialog box, in the Business Rule Name field, enter Assign and send notification to John Smith when a ticket with critical priority is created.
  5. Clear the Inactive check box.
  6. In the Business Rule Description field, enter When the defined conditions are met, assign the matching tickets and send email notification to technician John Smith.
  7. In the Define Conditions section, perform these steps:

    1. From the When list, select Ticket and then select the Created check box.
    2. From the Select a Field list, select Priority.
    3. From the Select a Condition list, select equals.
    4. From the Select/Enter a Value list, select 1 - Critical.
    5. Click .
  8. Click the Define Actions section and perform these steps:


    1. From the Select an Action list, select Update Record.
    2. From the Select Record Type list, Select Update Ticket Values.
    3. Click the Select/Edit fields.
    4. In the Select a Field dialog box, from the Select a Field list, select Ticket ID.
    5. From the Select a Value from list, select Use a value from current record.
    6. From the Select/Enter a Value list, select {Ticket - Ticket ID}.
    7. Click .
    8. In the Select a Field dialog box, from the Select a Field list, select Assigned To Technician.
    9. From the Select a Value from list, select Use a value or an expression.
    10. From the Select/Enter a Value list, select John.
    11. Click Apply.
  9. Click the Define Actions Schedule section and perform these steps:

    1. For the When to perform the action(s) setting, select the At a later time option.
    2. In the Hour(s) field, enter 1.
    3. Select the After option and from the next list, select Last Modified.
    4. In the Repeat field, enter 1.
    5. In the Hour(s) field next to the Repeat field, enter 1.
    6. From the Time Zone list, select (GMT-06:00) Central Time (US & Canada).
    7. From the Work Schedule list, select 40-hour work week.
  10. Click Save.

Scenario: Define a Business Rule to send a notification to all technicians in a group

To define a business rule to send a notification to all technicians in a group, follow these steps:

  1. On the header bar, expand the hamburger menu  and select Configuration.
  2. Click SLAs and Business Rules and then click Business Rules.
  3. On the Business Rules page, click New.
  4. In the Add Business Rule dialog box, in the Business Rule Name field, enter Notify technicians about a ticket creation or an update with multiple conditions.
  5. Clear the Inactive check box.
  6. In the Business Rule Description field, enter Notify technician that ticket is created or updated with multiple conditions with Critical priority and Operating Systems.
  7. In the Define Conditions section, perform these steps:

    1. From the When list, select Ticket and then select the Created and Updated check boxes.
    2. From the Select a Field list, select Category.
    3. From the Select a Condition list, select equals.
    4. From the Select/Enter a Value list, select Operating System.
    5. Click .
    6. To add the next condition, from the Select a Field list, select Priority.
    7. From the Select a Condition list, select equals.
    8. From the Select/Enter a Value list, select 1 - Critical.
    9. Click .
    10. To add the next condition, from the Select a Field list, select Ticket Summary.
    11. From the Select a Condition list, select is not blank.
    12. Click if you want to add another condition.
  8. Click the Define Actions section and perform these steps:
     
    1. From the Select an Action list, select Send Notification.
    2. Click Notification Details.
      The Notification Details dialog box is displayed as shown in the following figure:

    3. In the Recipient Details section, perform these steps:
      1. From the To list, select {Ticket - Technician} from the list.
      2. From the Select Groups list, select {Ticket - Group}.
      3. (Optional) In the CC field, select {Ticket - Cc} or enter email addresses.
      4. (Optional) In the BCC field, select {Ticket - Bcc} or enter email addresses.
    4. (2021 Release 01) (Optional) In the Attachment(s) section, select the Include attachment(s) from recordType check box to include the attachments associated with the record type in the notification email. This check box is not selected by default. 

      Important

      • The following considerations apply to the Attachment(s) section:
        • It is displayed when you select Send Notification for one of the following record types from the When list in the Define Conditions section:
          • Ticket
          • Assignment
          • Solution
          • Asset
          • Change Request
          • Purchase Order
        • It is also displayed when you select Send Notification with details for one of the following record types from the Select Record Type list in the Define Actions section:
          • Ticket

          • Assignment

          • Asset

          • Change Request

          Send Notification with details is available in the Select an Action list only when you select New Email Received from the When list in the Define Conditions section.

      • If the record type consists of attachments that have local files and URLs, then only the local files are included in the notification email. The URLs in the attachments are not included in the notification email.

      • The email message and the attachments associated with the record type must not exceed the size limit of the notification email that is configured on the email server. If they exceed the size limit, then the notification email is not sent.
    5. In the Message Details section, enter Ticket with {Ticket -Ticket ID} - {Ticket - Ticket Summary} has been created in the Subject field.

      Important

      You must enter the data in the particular fields of the Notification Details dialog box, depending on the recipient of the Business Rule notification. The recipients could either be an individual technician, a group of technicians, all system administrators, or any technician who is available.

    6. In the notification message field, enter any additional information related to the Business Rule. You can format the notification message text by using the different rich text formatting options provided. You can also insert or directly paste inline screenshots in the notification message field.
    7. Click Apply.

    8. Click  if you want to add another condition.
  9. In the Define Actions Schedule section, from the options in the When to perform the action(s) setting, select Immediately
  10. Click Save.

This section contains the following topics:


Was this page helpful? Yes No Submitting... Thank you

Comments