Skip to content

SLA rule reference

Overview

Use this reference to review SLA control methods, timing fields, event conditions, and compliance records. Available buttons, fields, scopes, and notification channels depend on permissions and configuration.

Rule terminology

TerminologyMeaningApplicability
ScopeDetermines which work orders or service requests enter the ruleApplies to both methods
Based on process nodesUse process node start and completion as timing boundariesSingle node or across nodes
Based on object fieldsUse object creation or field changes as timing boundariesObject creation, status or field changes
Start timingNode, field or condition for SLA record start timeBoth methods are applicable
End timingNode, field or condition of SLA record end timeProcess completion or field change
Standard processing timeThe upper limit of time used to determine whether the standard is metBoth methods are applicable
Early warning eventEarly reminder when the standard processing time is approachingThe end condition has not occurred and the timer has not ended
Timeout eventReminder or function execution after exceeding the standard processing timeThe end condition has not occurred yet

Timing and compliance rules

  • Meet the standard: end time - start time ≤ standard processing time.
  • Not up to standard: end time - start time > standard processing time.
  • After the countdown is enabled, the task node displays the remaining duration; after the standard duration is exceeded, the timeout duration is displayed.
  • Alerts and timeout events will not be triggered after the SLA timer has expired.
  • End conditions based on object fields can only be set to field changes.

Comparison of control methods

ProjectBased on process nodeBased on object field
Target AudienceWork Order or Service RequestWork Order or Service Request
Start conditionStart of process nodeCreate new object or change fields
End conditionProcess node completedField changes
Typical examplesAssignment starts to engineers receiving ordersWork orders are created until the status changes to work order service
Automatic backfilling of process fieldsYesNo, the original data does not specify automatic backfilling of process instance fields

SLA timeliness compliance status

The system presets the SLA timeliness compliance object to record each task that triggers SLA control. This object is applicable to work orders and service requests. It can be used to view the task handler, final task executor, start and end time, time consumption and compliance results. It can also be used as a data source for BI statistics.

The allowed time and compliance status in the SLA aging compliance status list

To show related records on a work order or service request, add General Related Component (What) to the detail layout. Set its related object to SLA Timeliness Compliance and bind Binding Data.

Add SLA compliance general related components in the work order details layout

Field descriptions

Field nameAPI NameField typeRemarks
Record numbernameIncrement numberStandard record number
Bind datarelated_objectDynamic associationAssociate work orders or service requests
SLA rule namesla_nameSingle line of text
SLA control methodsla_waySingle choiceProcess node or object field
SLA rule detail namesla_detail_nameSingle line text
Start timingstart_timeDate and timeStart timing time
End timingend_timeDate and timeEnd timing time
Standard processing timeremind_latencyNumberStandard time set by the rule
SLA timing durationdurationNumberActual timing duration
Timeout durationtimeout_timeNumberDuration exceeding the standard duration
Compliance statussla_resultSingle choiceResult of meeting the standard or not meeting the standard
The business process to which it belongsworkflow_instance_idSingle line of textAutomatically backfilled by the system only when it is based on process control
Process srcIdsource_workflow_idSingle line of textAutomatically backfilled by the system when only based on process control
Node instance IDactivity_instance_idSingle line textAutomatically backfilled by the system when only based on process control
Start timing node nameactivity_nameSingle line of textAutomatically backfilled by the system when only based on process control
End timing node namecompleted_activity_nameSingle line of textAutomatically backfilled by the system only when it is based on process control

Limitations and troubleshooting

PhenomenonCheck itemsProcessing direction
SLA entry not foundPlug-in activation status, administrator permissionsConfirm SLA plug-in and permissions in system settings
The record does not enter the SLATarget object, rule activation status, scope of applicationCheck whether the record meets the filtering conditions
Timing has not endedProcess end node or field change conditionsConfirm that the end condition actually occurs
Alert/timeout is not triggeredEvent time and SLA statusIt will not be triggered when the end condition has occurred or the timer has expired
No compliance records are visible on the details pageCommon associated components, associated objects and binding fieldsAssociate components to SLA timeliness compliance

The source material does not describe the complete rules for working time calendars, failure retries, batch catch-ups, and pause timings, and these behaviors should not be inferred from the field names.