The CreatorCon Call for Content is officially open! Get started here.

Close Incident button not present in sub-prod instance after Eureka Patch 9 HF 4 applied

jfrancione
Tera Contributor

In validating one of our sub-prod instances (stage) I have noticed that the Close Incident Button is no longer available after the upgrade (see attached) .   Prior to upgrade to Eureka Patch 9 HF 4, the instance was at Eureka Patch 3 HF 1.   I have tested Incidents in various states (ex. . Open, closed)   and nothing is failing.   So far, I am fine with the absence of the button, but would like to know if I am missing something in my testing/validation .   Better now in a sub-prod instance   🙂   I have gone through all of the Release notes and have not found anything that refers to this issue.   If there is something I need to check/confirm I would be most grateful for the assistance.  

thank you,

Jim Francione

1 ACCEPTED SOLUTION

Your button now only shows up on Resolved:



current.incident_state == 6


vs.


current.incident_state != 7


View solution in original post

5 REPLIES 5

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hi Jim,



Is the button not available in the list of UI Actions table too.


Pradeep,



Thank you for your quick response.   I've compared the prod instance and our other sub-prod instance (test) to the upgraded sub-prod instance (stage).   The attributes of the UI Action 'Close Incident' is different (see attached screen shots) .   I can certainly modify the stage instance that has been upgraded to match what our prod instance looks like, however, my concern is now what other UI actions   or other components might have changed that my testing hasn't uncovered.


Your button now only shows up on Resolved:



current.incident_state == 6


vs.


current.incident_state != 7


I would use the eye test to see if any more conditions have changed, check the last updated to be > the date of the upgrade, that sort of thing.