Availability Calculation only occurring when Outage record is closed

Ryan Workman
Tera Contributor

I was recently working with a Vancouver instance, both in my company's sandbox and in a personal development instance so I could confirm out of the box functionality vs any customization or configuration that may be in place.  In both cases, I was testing out Availability with com.snc.availability.v2 turned on (turned it on in our sandbox, was turned on by default in the developer instance).  The behavior I expected and experienced was that when an outage record was opened the availability would be updated in real time.

 

However, now that we have upgraded to Xanadu, I cannot get the same behavior to occur.

 

Steps that I have taken:

1) Ensured that com.snc.availability.v2 is turned on

2) Created a Business Service with a Service Offering

3) Created an availability commitment with schedule 24x7 and 99.5 target and mapped it to the service offering

4) Created an Incident

5) Created an Outage with the primary CI being the created service offering and an outage start time that defaulted to present time.

 

Checked the availability results and they were not updated.

 

I have confirmed that if I close the outage record the availability results are updated instantly.

 

This occurs both in my sandbox and also a fresh developer instance.  I must be missing something.  Does anything come to mind?

1 REPLY 1

Rushikesh M
ServiceNow Employee

That is the difference of the availability calculation between v1 & v2. The outage duration will be considered only for closed outages in v2.

Watch here: https://www.youtube.com/watch?v=GizZ36ysEsA&t=2745s