Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Assessment trigger conditions

Log in to subscribe to topics and get notified when content changes.

Assessment trigger conditions

A trigger condition tells the system who to send a designated assessment to and when, based on specific conditions.

With trigger conditions, assessment administrators can configure the system to generate assessments each time a specific action occurs, such as when an incident or change request closes. The trigger condition sends the assessment to specified users who are related to the triggering record, such as incident callers or change request assignees. You can choose to send the assessment every time the condition is met, or set a probability for the system to send the assessment at random when the condition is met.

Table 1. Trigger condition configuration
Assessment Vendor
Table Incident [incident]
User field Assigned to
Repeat Interval 30 days
Active true
Trigger randomly false
Assessable Record Field Vendor
Related Field 1 Caller
Related Field 2 Vendor
Condition [State] [is] [Closed] and [Vendor] [is not empty]

Trigger condition example

Modesto Scroggie is the caller on an incident that is assigned to Boris Catino, a service desk technician. Boris contacts a vendor to resolve Modesto's issue and sets the Vendor field to Microsoft. When the incident closes, the system creates an assessment instance assigned to Boris so he can evaluate Microsoft as a vendor.

Because two related fields were selected as part of the trigger condition, the assessment instance stores the following information from the incident:
  • Related record 1: User: Modesto Scroggie
  • Related record 2: Company: Microsoft
Note: Even though the trigger condition is set to be triggered every time the conditions are met, the Repeat Interval setting ensures that Boris does not receive another assessment if another vendor incident assigned to him closes within 30 days of the first one.