On our implementation (Cloud 2018.1), those fields aren't present within our Incident table. Are they custom fields?
I'd suggest first checking the business rules to see if these are populated on a certain event, failing that, I would have a look at the workflows - first on Incident then for frs_data_escalation_watch.
2 of 2 people found this helpful
We have had these fields in HEAT 7 as well and recreated them in Ivanti Service Manager (as they were not out-of-the-box anymore):
- Add a Before-Save Rule for isResolutionBreached:
$(ResolutionEscLink != null && ResolutionEscLink != "" &&
- Add a Before-Save Rule for isResponseBreached:
$(ResponseEscLink != null && ResponseEscLink != "" &&
- Add Initialization Rules with isReponseBreached & isResolutionBreached = false