
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2023 08:55 AM
Hi all
I have the organizational requirement to group Business Services into organisational or functional 'Clusters'
- The records are used to maintain attributes/roles that are cascaded onto the Services and Service Offerings. The cascading logic itself shouldn’t be an issue.
- At the moment I’m planning on using the Taxonomy nodes for this - the PROS are:
- The taxonomy nodes can be renamed using the layer definitions
- It integrates nicely into the CSDM Model and the Digital portfolio manager workspace view.
- Future proof as depending on their org requirements, we simply add more layers.
- Is there another table that is better suited for this grouping? I’d rather not create a custom table if there is a baseline table we can use.
Many thanks for your input!
Cheers,
Tomas
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2023 09:45 AM
Yes Taxonomy Nodes are what you should be using for this. A couple of things you'll want to note: 1) with the "legacy" portfolios in Service Portfolio Magement, there is a strict taxonomy, meaning that once you define your nodes you can no longer define new layers. You would have to tear it down and start over if you wanted to add another layer. 2) with the "Standard Portfolios" used by DPM, layers aren't used at all; you can add new levels as needed per branch but you can only associate Services with the leaf nodes, so you would need to temporarily disconnect them from the existing nodes before adding new child nodes.
The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2023 09:45 AM
Yes Taxonomy Nodes are what you should be using for this. A couple of things you'll want to note: 1) with the "legacy" portfolios in Service Portfolio Magement, there is a strict taxonomy, meaning that once you define your nodes you can no longer define new layers. You would have to tear it down and start over if you wanted to add another layer. 2) with the "Standard Portfolios" used by DPM, layers aren't used at all; you can add new levels as needed per branch but you can only associate Services with the leaf nodes, so you would need to temporarily disconnect them from the existing nodes before adding new child nodes.
The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2023 08:35 AM - edited 05-11-2023 08:35 AM
Cheers Paul - i'll see if any other lost souls happen to stumble upon this post and have further input. Otherwise i'll mark your answer as solution 😀

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2023 06:35 AM
Thanks for the answer. Yes of course, that's something that we'll look at. The legacy portfolio layers are nice because you can name the layers and keep order, however as you mentioned it's strict and causes more work if and when a new layer is introduced later down the line.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2023 11:37 AM
I do wonder if you can use the Business Unit for this?
Business units are segments of an enterprise that are in charge of certain operations such as Finance, HR, IT. Each of these business units can have a strategy that aligns with the enterprise or with another business unit. https://www.servicenow.com/community/now-platform-forum/business-units-and-departments/m-p/1067797