Release notes and tips for September 24 post-golive release

Changes included in this release

Notifications

  • Customers will now receive an automated email, acknowledging receipt, when they send an email to IT Support (this was disabled temporarily, during the stabilization phase).
  • When a customer clicks the Close Now link in a closing email, it will no longer create a new Ticket.
  • CI contacts will no longer receive Alerts twice.

Miscellaneous form changes

  • Incident Category and Subcategory will only be mandatory for WMS and Desktop Support services.
  • The Major Incident Manager field has been moved to the Incident form.
  • Ticket number has been added to a tab within the Request Item.

Tip: Creating a Request on behalf of someone else

Problem:

When creating a request on behalf of someone else, your name is put into the Requested For field of the REQ and RITM records. It should be changed to the real customer, but if you try to do it on the RITM record you will see that the Requested For field is locked.

Tip:

Go back to the REQ record and change it there. The new name then flows through to the RITM record and the real customer will receive all subsequent notifications through ServiceNow.

Note: Since the customer doesn’t receive the initial notification that the Request has been created, you should forward it to them and explain that you created it on their behalf.

ITSM 2.0 Celebration

The ITSM 2.0 release was celebrated last Thursday, Sept.13, at Thomson House. Daniel Letendre and Carla D’Alessandro thanked all contributors for their hard work and dedication to the project. Stuart Forman spoke about the good spirit he observed among the team and said we need to value that comradery and keep it going.

We ate, drank and even played a game — everyone seemed to enjoy the evening.

View the fun-facts slideshow presentation (PDF)

Here are some pics…

Blog authors are solely responsible for the content of the blogs listed in the directory. Neither the content of these blogs, nor the links to other web sites, are screened, approved, reviewed or endorsed by McGill University. The text and other material on these blogs are the opinion of the specific author and are not statements of advice, opinion, or information of McGill.