For more information about Ticket Rules, see Using Ticket Rules.
Many of the more complex Ticket Rules, such as modifying the behavior of email notifications, are published on the Quest Support site, https://support.quest.com/contact-support.
You can configure the K1000 to receive email from POP3 servers.
• |
• |
You can create and configure POP3 email accounts for use by the Service Desk users and staff.
• |
• |
1. |
2. |
Configure DefaultTicketOwners@mydomain.com as the Service Desk staff email alias, and add all of your Service Desk staff email addresses to it. This is the general-purpose email alias that your Service Desk staff uses to communicate with each other. |
3. |
◦ |
If the Organization component is not enabled on the appliance, log in to the K1000 Administrator Console, http://K1000_hostname/admin, then click Settings. |
◦ |
If the Organization component is enabled on the appliance, log in to the K1000 System Administration Console, http://K1000_hostname/system, or select System in the drop-down list in the top-right corner of the page, then click Settings. |
4. |
5. |
Specify the hostname or IP address of an external SMTP server, such as smtp.gmail.com. External SMTP servers must allow anonymous (non-authenticated) outbound email transport. Ensure that your network policies allow the appliance to contact the SMTP server directly. In addition, the mail server must be configured to allow the relaying of email from the appliance without authentication. | |
Enter the username of an account that has access to the external SMTP server, such as your_account_name@gmail.com. | |
Select this check box to use POP3 for Service Desk ticket email. |
6. |
7. |
a. |
Log in to the K1000 Administrator Console, http://K1000_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
8. |
NOTE: POP3 options are available only if Service Desk POP3 Server is enabled in the appliance Network Settings. See Changing appliance network settings. |
10. |
The Email on Events section determines which actions trigger an email to the various K1000 Management Appliance users. Email templates determine the content of the messages.
The following email events trigger the K1000 to send email immediately:
• |
Comment: The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent. |
• |
Ticket Closed: If the Satisfaction Survey is enabled, an email that describes the Satisfaction Survey is sent immediately when tickets are closed. |
1. |
a. |
Log in to the K1000 Administrator Console, http://K1000_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
2. |
In the Email on Events section, select the options for sending email when the specified events occur. Each column represents a type of Service Desk user (role) and each row represents a ticket event. |
The person who can approve or reject the ticket for processing. | |
One or more email addresses that are stored in the CC field of the ticket. | |
One or more email addresses that are stored in the CC List of the Category Value of the ticket. See Configure CC lists for ticket categories. |
When a ticket event occurs, email is sent to the selected roles or users. For example, if you select the Any Change box in the Owner column, email is sent to the ticket owner whenever the ticket is changed. For the Comment and Ticket Closed triggers, email is sent immediately. For other ticket changes, however, email is sent every few minutes to prevent email overload.
The ticket's Owner field is changed. | |
The ticket's Status field is changed. | |
Information, attachments, or screenshots are added to the ticket's Comments section. The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent. | |
The ticket has not been resolved within the escalation time defined by the ticket priority. | |
The ticket's Status field is changed to Closed. This event is used to present a Satisfaction Survey to submitters. See Using the Satisfaction Survey. | |
A user sends an email message to the Service Desk and a ticket is created. |
3. |
1. |
a. |
Log in to the K1000 Administrator Console, http://K1000_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
2. |
In the Email on Events section, click Customize Emails to display the Service Desk Email Notifications page. |
Used to send periodic notifications according to the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. |
||||
|
||||
None. Configurable on the Queue Detail page |
Used to notify senders that the ticket could not be created for reasons other than unknown email address. |
||
The name of the Service Desk queue. This name is configured on the Queue Detail page. | |
A link to the User Console. Access to the User Console requires login credentials. |
The type of the process. In a default installation, only the Service Desk process type is included. You can create new process types, as required. For example, you can create a process type for accessing a specific application, or a group of applications. For more information, see Define process types. | |||
The email address of the ticket approver. Having this address is especially useful for Comments email notifications. | |||
The name of the ticket approver. | |||
The label and value used for a custom field, where X represents the index number of the custom field. For example, if a queue has a ticket field labeled, CUSTOM_5, and that field is configured with the label Location Name, the system replaces $ticket_custom_5_label with the text, Location Name. The token, $ticket_custom_5_value is replaced with the ticket value that was saved for the Location Name field, such as, Topeka or Albuquerque. | |||
The time, in minutes, between periodic notifications. This time is determined by the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. This token is typically used in the Ticket Escalated email template, to inform recipients of the frequency of email notifications. | |||
Include all the ticket fields that are visible for the user who is forwarding the ticket by email.
| |||
The complete history of the ticket.
| |||
A specified number of records in the ticket history. X indicates the number of records to include, beginning with the most recent. | |||
A formatted version of the ticket ID. This version begins with TICK followed by a minimum of five digits. For example, a ticket with ID 4321 is displayed as TICK:04321. This format is especially useful in email Subject lines to make sure that email replies link to the correct tickets. | |||
The email address of the Service Desk administrator assigned to the ticket. | |||
The name of the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
The priority assigned to the ticket. Default values include High, Medium, and Low. | |||
Information about what was done to resolve the ticket as described in the ticket’s Resolution field. | |||
| |||
The title of the ticket as it appears on the Ticket Detail page. | |||
A link to the ticket in the User Console. Access to the User Console requires login credentials. | |||
A link to the ticket in the User Console. This format is used for backward compatibility on older systems. Access to the User Console requires login credentials. | |||
A secure link to the ticket in the User Console. Use this token if SSL is enabled on your appliance. This ensures that links sent through email work correctly. | |||
A link to the home page of the User Console. Access to the User Console requires login credentials. |
Used to identify a problem processing the submitted tokens. This error appears when: | |
NOTE: Tokens that are invalid are ignored and they are not replaced in email messages. For example, if you add an unknown token such as $today, it is ignored, and it appears in the email message as $today. |
4. |
5. |
For instructions on how to configure the appliance to use SMTP email, see Configuring SMTP email servers.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy