Vancouver / Service Portfolio Management and Taxonomy Nodes

[Debs McCann]

Has anyone upgraded to Vancouver and already had a Service Portfolio configured previously (SPM), where taxonomy nodes were required to be configured (its mandatory). I am expecting Vancouver not to require Nodes to be configured. Is this correct?

[Deb McDaniel]

My apologies for just getting back to this discussion. Thank you for the response. It was helpful. Do you have any guidance for converting an existing portfolio to the new standard portfolio released in Vancouver? We just upgraded to Vancouver a few weeks ago, and I was curious if there is any guidance on this.

[Liz Fassone · Accepted solution]

Hi @Debs McCann, 

Are you referring to this step at the end of this screen recording - note the 'Taxonomy layer' is a mandatory field. (So I think the answer it is still required...?). 

This is a screen recording from a fresh personal developer instance (Vancouver). 

Did you know you can 'opt-in' to the improved portfolio structure? 

See more here https://docs.servicenow.com/bundle/vancouver-it-service-management/page/product/service-portfolio-ma... 

[Debs McCann]

Yes that’s it, thank you, Liz. Wasn’t sure what to expect when we upgraded to Vancouver 

[Donna2]

Adding an update that ServiceNow has now an Upgrade to Standard Portfolio system property that helps you migrate away from the legacy Taxonomy Layer Definition tables and it's mandatory requirement within the SPM Service Portfolio hierarchy which after Utah you only need Service Portfolio > Taxonomy Node > then right to Business Services or Technology Management Services. 

From the Brazil docs

• Releases before Utah used the legacy structure. In it, nodes have to belong to a layer, and reporting relies on performance metrics, scores and weights in Service Owner Workspace.
• The standard structure removes layers. Nodes relate directly to each other, depths can vary within one portfolio, and reporting uses KPI groups in Digital Portfolio Management.
• Existing customers have to opt in to the standard structure:
  1. Use the portfolio_admin role.
  2. Go to All > Service Portfolio Management > Administration > Upgrade to Standard Portfolio. This menu only appears on instances that are still on the legacy structure.
  3. Select Yes and review the considerations in the dialog. The opt-in turns on the property standard_portfolio_construct.turn_on.
• The upgrade can’t be reversed. Portfolios carry over. Performance scores, weights and metrics are no longer available in Service Owner Workspace. The service_offering_metric_data table and the Average SLA, Customer Satisfaction, Availability and Request Activity indicators are deprecated. If the client uses the Vendor Management Workspace integration, it loses that metric data.