com.snc.sla.get_task_from_dbThe com.snc.sla.get_task_from_db property ensures that SLAs are processed using fresh data from the database rather than the potentially outdated 'current' GlideRecord object. Admins should care about this property to avoid issues with stale data affecting SLA calculations.
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | This property configures the SLA processing to fetch records directly from the database for specified Task tables, preventing the use of outdated information. |
|---|---|
| What area does it affect? | SLA Processing |
| What does the default mean? | The default value is "sc_req_item", which is the baseline setting used unless it is changed. |
| When should you review it? | Review this property when configuring SLA behavior or troubleshooting SLA-related data issues. |
Raw metadata from the property record.
| Property name | com.snc.sla.get_task_from_db |
|---|---|
| Sys ID | 04996bb573200010491d235f04f6a74c |
| Type | string |
| Application | Global |
| Default value | sc_req_item |
| Description | When processing SLAs any of the Task tables specified in this property, the "current" GlideRecord object will not be used. Instead, the record will be fetched from the database. This can be used to prevent SLAs from being processed with stale data in "current". |
| Updated | 2024-05-25 03:38:52 |