SPM - Data Segmentation Best Practices

[Scott Wallace1]

The recommendations in this article are legacy and not applicable from the Xanadu release.

Refer to the community article below for updated recommendations: 

Enterprise-wide Deployment recommendations and best practices

If you are looking for SPM Best Practices for the topic of Data Segmentation and the options to support the separation of data and configuration, the below information provides a detailed outline of the feature options being supported by SPM and the Platform.   See the attachment below for the full outline by use case, capabilities, limitations, and recommendations. 

 

 

 

[PaulaaO]

@Scott Wallace1  very useful post, thanks for this.

Quick question: our use case is that we have a custom field on pm_project form to identify whether a project is Confidential or not and we have created quite a bit of customisation to only allow certain personas and users access to Confidential projects. We're exploring now whether Data Filtration might help us achieve the same thing in order to decommission some of our customisation - is that the correct route to take? I have reviewed the attached PDF and plan to look into Data Separation as well, but what's your view on the best OOTB approach for this use case? Thank you 🙂

[Matt Rose1]

@Scott Wallace1  I have the exact same question as @PaulaaO, except that it is a current requirement for a client. They want two layers of segmentation: by portfolio (Data Separation) and then again by whether or not the project is marked as Confidential. 

[Luis Ataide]

Hi @PaulaaO and @Matt Rose1,

Thank you for your questions.

The Data separation is based on Lens structure, meaning it doesn't cover the use case based on project characteristic, in your case, project marked as confidential. 

For this case, you can leverage platform functionalities such as before query business rule and/or ACL.

Hope this response helps to clarify your question.

Let me know if you have additional questions.

Best regards,

Luis Ataide.

[Kartik23]

Hi @PaulaaO , @Matt Rose1 , based on your comments here I realise that you may benefit from the following resources:

1. Ability to mark projects as confidential is now available starting with Yokohama. You can find more details here.

2. We have documented in detail (KB1772519) how security data filters can be used to configure common data segmentation use cases. 

Please feel free to reach out to me (kartiknitin.dasani@servicenow.com) for any further questions or clarifications. 

[PaulaaO]

@Kartik23 that's amazing!! thank you very much for sharing those links, I'm quite keen to get the chance and see how the confidentiality functionality works in practice. 😍