Trigger Condition form for surveys
- UpdatedAug 3, 2023
- 3 minutes to read
- Vancouver
- Service Administration
The Vancouver release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.
Description of the field values for the Trigger Condition form for surveys.
Field | Description |
---|---|
Assessment | Survey to send. |
Table | Table to run the trigger condition on. You can select only tables in the current application scope. For example, to send a survey whenever an incident closes, select the Incident [incident] table. |
User field | Field that stores the users you want to send the survey. You can select any
field, on the selected table or on a referenced table, that references the User
[sys_user] table. Use the tree picker to select a field. Note: To avoid requiring users
to log in to take a survey with a trigger condition, set the survey to
Public. |
Repeat interval | Minimum period that must pass before the trigger condition can resend the survey
to the same user. For example, assume the repeat interval is set to 30 days. Even if
the same user qualifies for multiple surveys from this trigger condition, the system
can send only one survey every 30 days. Note:
|
Application | [Admin only] Application is set to Core. |
Active | Check box that determines whether this trigger condition is active (selected). |
Business rule | [Admin only] Business rule the system creates to monitor the selected table. When the condition is met, the business rule sends the survey to the correct user. No configuration is necessary for this business rule. |
Trigger randomly | Check box that determines whether to send the survey to the appropriate user every time the condition is met (cleared) or only a percentage of the time (selected). |
Probability (%) | Approximate probability that the survey is sent each time the condition is met. For example, if the probability is set to 50, the system sends the survey approximately 50% of the time the conditions are met. There are no repeat interval restrictions is assumed. This field is visible and required only when Trigger randomly is selected. |
Related Field 1- 4 | Field that contains a value you want to store for reporting purposes. You can
pick any reference field on the selected table. When the trigger condition generates a
survey instance, the system stores the value from the triggering record. Specify up to
four fields. For example, select the Incident table, Assigned to and Problem as related fields. The system stores the assigned user and problem associated with the incident as Related record 1 and Related record 2 in the survey instance record. To view the fields, configure the form for any survey instance. Note: You cannot use a related field for the
ticket number because you cannot select the Number column. You can, however, use the
trigger_id column of the table. |
Description | Summary information to identify the trigger condition. Note: For a triggered
record, the table title is used for the survey description. |
Condition | Condition builder that defines the criteria that must be true to send the survey.
For example, to send a survey whenever an incident closes, create the condition
[State] [is] [Closed]. Note: When defining conditions like
case sensitivity or null values, see APIGlideFilter - Scoped,
Global. |
Related Content
- Configure a trigger condition for a survey
Configure trigger conditions to specify when to send a particular survey and the persons to send it to.