- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
04-07-2025 09:13 PM - edited 04-07-2025 10:27 PM
SLA configuration can get a little complex when service based SLAs need to be configured, this scoped app is meant to simplify such configuration by making use of decision tables to map service to an SLA, below are specifics of the configuration.
SLA definition
Configure SLA definition filter condition with service.sys_id Is one of as condition and in the condition provide javascript that returns list of service sys_ids for which given SLA is applicable, below is sample condition script where 'a2a8e0158330a210b0abcfc0deaad37e' is sys_id of the SLA definition
javascript: new global.ServiceBasedSLAUtils().includedServicesForSLA('a2a8e0158330a210b0abcfc0deaad37e');
Decision table
A decision table is created with input as SLA sysid and output as list of sysids of services for which a given SLA is applicable.
Script Include
Script include contains required configuration to return sysids of services for a given SLA sysid based on decision table configuration.
Scoped app
All required configuration is packaged in a scoped app.
which is accessible here : anilvaranasi/ServiceBasedSLAManagement
Testing
Sample incident with service as SAP Materials Management (sys_id = 26e44e8a0a0a0bb40095ff953f9ee520)
Decision table
Decision entry with service sys_id as result
SLA is attached to the incident