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