Vancouver / Service Portfolio Management and Taxonomy Nodes

Debs McCann · ‎10-24-2023

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?

Liz Fassone · ‎12-13-2023

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...

View solution in original post

Tim Raymond · ‎12-12-2023

I am not deeply familiar with Service Portfolios, but I see in the docs an explanation of the legacy (Tokyo and earlier) and new (Utah and beyond) Portfolio structures. There is no mention of required v. optional nodes so I would imagine they may still be required? These docs may be helpful: Portfolio structures

Deb McDaniel · ‎12-13-2023

Is it possible to get someone from ServiceNow to review the Service Portfolios with us so we can understand how to move from legacy to the new standard portfolio structure? I'm also open to more in-depth resources for learning/understanding beyond the docs, as they aren't particularly helpful for those transitioning.

Deb McDaniel · ‎12-13-2023

I'm sorry if this appears twice. It didn't look like the original post posted.

Can we contact someone directly to learn more about the new taxonomy for standard portfolios? I didn't find the docs particularly helpful for transitioning from legacy to the new portfolio standard. I'm also willing to review other materials that may be more detailed if they are also available.

Debs McCann · ‎12-13-2023

Keen to hear how you go. We are in the same boat.