Combined ITOM Visibility release notes for upgrades from San Diego to Vancouver
- UpdatedApr 19, 2024
- 11 minutes to read
Consolidated page of all release notes for ITOM Visibility from San Diego to Vancouver.
How to use this page
To help you prepare for your upgrade, we have combined the cross-family ITOM Visibility release notes onto one page. Read this summary of the new features, changes, and updated information for your product from San Diego to Vancouver.
Important information for upgrading ITOM Visibility to Vancouver
Before you upgrade to Vancouver, review these pre- and post-upgrade tasks and complete the tasks as needed.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
ITOM Visibility report_view access control lists (ACLs) that govern who can see reports in dashboards and elsewhere are enabled by default in the Tokyo release. For more information, see Report_view access control. After upgrading to Tokyo, the install status is automatically set to “Installed” (“1”) for all discovered infrastructure CIs. If your organization uses the install status, test Tokyo on your test instance before upgrading the production instance. Use the CSDM lifecycle status for tracking life cycle stages and stage statuses for CIs. For more info, see:[Placeholder link text to key bundle-rn.bundle-platcap.csdm-life-cycle-standard-values] To resolve issues related to the install status after upgrading to Tokyo, see KB1213467 |
Utah |
No updates for this release. |
Vancouver |
|
New features
Between your current release family and Vancouver, new features were introduced for ITOM Visibility.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
|
Utah |
|
Vancouver |
|
Changes
Between your current release family and Vancouver, some changes were made to existing ITOM Visibility features.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
|
Utah |
|
Vancouver |
|
Removed
Between your current release family and Vancouver, some ITOM Visibility features or functionality were removed.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
No updates for this release. |
Utah |
No updates for this release. |
Vancouver |
No updates for this release. |
Deprecations
Between your current release family and Vancouver, some ITOM Visibility features or functionality were deprecated.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
No updates for this release. |
Utah |
No updates for this release. |
Vancouver |
Creating schedules for discovering cloud resources using classic Cloud Discovery is planned for deprecation. Consider moving to Cloud Operations Workspace. |
Activation information
Review information on how to activate ITOM Visibility.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
ITOM Visibility is available with activation of the Discovery (com.snc.discovery) plugin and the Service Mapping (com.snc.service-mapping) plugin, which require the ITOM Visibility subscription. For details, see Request Discovery and Request Service Mapping. For full ITOM Visibility functionality, install the latest ITOM Visibility out-of-band applications from the ServiceNow Store. For cumulative release note information for all released apps, see the ServiceNow Store version history release notes. |
Utah |
|
Vancouver |
ITOM Visibility is available with activation of the Discovery (com.snc.discovery) plugin and the Service Mapping (com.snc.service-mapping) plugin, which require the ITOM Visibility subscription. For details, see Request Discovery and Request Service Mapping. For full ITOM Visibility functionality, install the latest ITOM Visibility out-of-band applications from the ServiceNow Store. For cumulative release note information for all released apps, see the ServiceNow Store version history release notes. |
Additional requirements
If any additional requirements were introduced or changed for ITOM Visibility we have noted them here.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
No updates for this release. |
Utah |
No updates for this release. |
Vancouver |
No updates for this release. |
Browser requirements
If any specific browser requirements were introduced or changed for ITOM Visibility we have noted them here.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
No updates for this release. |
Utah |
No updates for this release. |
Vancouver |
No updates for this release. |
Accessibility information
Review details on accessibility information for ITOM Visibility, such as specific requirements or compliance levels.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
No updates for this release. |
Utah |
|
Vancouver |
No updates for this release. |
Localization information
If there are specific localization considerations for ITOM Visibility we have noted them here.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
No updates for this release. |
Utah |
No updates for this release. |
Vancouver |
No updates for this release. |
Highlight information
If there are specific highlight considerations for ITOM Visibility we have noted them here.
Filter by
Release | Release notes |
---|---|
San Diego |
No updates for this release. |
Tokyo |
See the ITOM Visibility landing page for more information. |
Utah |
See IT Operations Management for more information. |
Vancouver |
See IT Operations Management for more information. |