Unauthorised Change Request event : ci.change.unplanned

priyanshij
Kilo Guru

Does anybody know how or from where the event ci.change.unplanned is triggered in case any update is done on ci which is an application service without any change related to it ?

15 REPLIES 15

Michael Walsh
Tera Contributor

Know this is an old one, but do any of you happen to know if Service Mapping has to be enabled in order for the ci.change.unplanned event to be fired?  I too haven't been able to find any code that fires it, but i'm just trying to find out if I have to have Service Mapping for it.  Don't see any being fired with just Discovery running and the docs seem to imply you might need to have Service Mapping, but other pieces of it, like the event itself and the properties around it and the unauthorized change module are all there without SM...so...

Hi Michael,

                  I currently have a requirement to test this functionality - "Unauthorized change properties (servicenow.com)

Have you found if Service Mapping needs to enabled inorder to test this feature

Also are there other methods to test this feature without Service Mapping, like Manual update to CI records?

 

Thanks

Ashok 

I haven't.  It wasn't really a burning issue, just a question someone had asked me that i didn't know the answer to and was hoping someone else might 🙂

 

As for testing, it looks like Gabriel has responded to this thread a few weeks ago and provided a script you could use to manually generate the event.  You might try that.

Thanks for the response Michael, I will use Gabriel's script to test this event.

 

I am having the event fire when I convert a Business Service to an Application Service.  The Business Service table does not have a 'Severity' field, but when converting to Application Service, the 'Severity' field is now present and the value change from a "NULL" to a "Value" causes the rule to fire.

If I change the class of the Application Service back to Business Service and perform the function again (testing purposes), the event does not trigger again.

I have followed the Event Log to see what events are firing to understand what the process is for the event since I can't find and code to say the trigger.  I have only been able to get this to run by the Severity field going from Null to  a Value.