Combined Public Sector Digital Services release notes for upgrades from Vancouver to Washington DC
Consolidated page of all release notes for Public Sector Digital Services from Vancouver to Washington DC.
How to use this page
To help you prepare for your upgrade, we have combined the cross-family Public Sector Digital Services release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Vancouver to Washington DC.
Important information for upgrading Public Sector Digital Services to Washington DC
Before you upgrade to Washington DC, review these pre- and post-upgrade tasks and complete the tasks as needed.
| Release | Release notes |
|---|---|
Vancouver |
Before you upgrade to Public Sector Digital Services v8.0, you must create custom service definitions for data in the Services Offered table, data in the Services Received table, and all other data affected by the conversion of the Services Offered table to the Service Definition table (Performance Analytics dashboard data, constituent or business report data, and so on). Any custom Services Offered and Services Received data created in previous releases will not be automatically migrated to the new release, and, after upgrade, will not be accessible within the application until the data is migrated from the legacy entities to the Service Definition table. For details, see Services Offered and Services Received Migration Guidance and Configure a service definition for Playbooks in Public Sector Digital Services. After the upgrade, certain public sector menus and menu items in the CSM Configurable Workspace revert to their original CSM label names. You can relabel these items for public sector use by updating the UX List Categories for Customer and Service Organizations. For details, see Relabel items for public sector use after upgrade. |
Washington DC |
After the upgrade, certain public sector menus and menu items in the CSM Configurable Workspace revert to their original CSM label names. You can relabel these items for public sector use by updating the UX List Categories for Customer and Service Organizations. For more details on relabeling, navigate to , and select . |
New features
Between your current release family and Washington DC, new features were introduced for Public Sector Digital Services.
| Release | Release notes |
|---|---|
Vancouver |
|
Washington DC |
|
Changes
Between your current release family and Washington DC, some changes were made to existing Public Sector Digital Services features.
| Release | Release notes |
|---|---|
Vancouver |
|
Washington DC |
No updates for this release. |
Removed
Between your current release family and Washington DC, some Public Sector Digital Services features or functionality were removed.
| Release | Release notes |
|---|---|
Vancouver |
No updates for this release. |
Washington DC |
No updates for this release. |
Deprecations
Between your current release family and Washington DC, some Public Sector Digital Services features or functionality were deprecated.
| Release | Release notes |
|---|---|
Vancouver |
Important: Upon upgrade, the Services Offered and Services Received tables will be deprecated and replaced by the Service Definition table. Service
Offered, which is an extension of Product Model, will no longer be used to model government services. Services Received, which is an extension of Sold Product, will no longer be used to model the government services that have been
granted or delivered to constituents. The Service Definition table, which is extended from Service Model [cmdb_service_product_model], is now used to model all public services that are offered by agencies. For more information, see Configure a service definition for Playbooks in Public Sector Digital Services.Any data in the Services Offered and Services Received tables need to be manually migrated into the Service Definition table. You can do so by creating a Service Definition for each entry in the Services Offered
table. For more information, see Services Offered and Services Received Migration Guidance. |
Washington DC |
No updates for this release. |
Activation information
Review information on how to activate Public Sector Digital Services.
| Release | Release notes |
|---|---|
Vancouver |
Install Public Sector Digital Services applications by requesting them from the ServiceNow Store. For details on installing the applications, see Configuring Public Sector Digital Services. Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes. |
Washington DC |
Install Public Sector Digital Services applications by requesting them from the ServiceNow Store. For details on installing the applications, see Configuring Public Sector Digital Services. Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes. |
Additional requirements
If any additional requirements were introduced or changed for Public Sector Digital Services we have noted them here.
| Release | Release notes |
|---|---|
Vancouver |
No updates for this release. |
Washington DC |
No updates for this release. |
Browser requirements
If any specific browser requirements were introduced or changed for Public Sector Digital Services we have noted them here.
| Release | Release notes |
|---|---|
Vancouver |
No updates for this release. |
Washington DC |
No updates for this release. |
Accessibility information
Review details on accessibility information for Public Sector Digital Services, such as specific requirements or compliance levels.
| Release | Release notes |
|---|---|
Vancouver |
No updates for this release. |
Washington DC |
No updates for this release. |
Localization information
If there are specific localization considerations for Public Sector Digital Services we have noted them here.
| Release | Release notes |
|---|---|
Vancouver |
No updates for this release. |
Washington DC |
No updates for this release. |
Highlight information
If there are specific highlight considerations for Public Sector Digital Services we have noted them here.
| Release | Release notes |
|---|---|
Vancouver |
See Public Sector Digital Services for more information. |
Washington DC |
See Public Sector Digital Services for more information. |