General

[RichaRoseM]

Hi Team,

I need to do an analysis. I need to make some fields in a table mandatory. I need to analyze whether it will impact any upstream or downstream systems in service now. I have taken the data completeness. But when i checking some fields like flows and all I am not able to find any tables in that. How can I start this? 

[Tanushree Maiti]

Hi @RichaRoseM 

Is it a CMDB CI table?

If yes, instead of making the field mandatory directly on the table, configure it as a Recommended Field in the CI Class Manager.

If it's not a CMDB CI table, you can use a UI Policy to make the field mandatory only under specific conditions, rather than making it mandatory directly at the table level.

[Ehab Pilloor]

Hi @RichaRoseM,

 There is no table field in Flow. Table is set on trigger condition, which is in a different related table for Flow. ServiceNow stores flow triggers primarily in the Process Flow Triggers [sys_hub_trigger_instance] table. This table manages the conditions, definitions, and execution instances for when a flow should fire.

You can also search by Name contains Incident on INC to see which all Flows are on tagged to Incident. 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.

Regards,

Ehab Pilloor

[RichaRoseM]

It is just a table for a location. I am making some of the fields in the location in mandatory via dictionary entry. So I need to check  whether any upstream or downstream systems are getting impacted. How can i do that in some cases in such as  flows?

[Tanushree Maiti]

Hi @RichaRoseM 

Before making the Location (cmn_location) field mandatory in ServiceNow, it's important to assess the impact across existing data, integrations, and dependent processes. A structured approach can help avoid data quality issues and service disruptions.

Key considerations include: (Upstream)

• Legacy records: Existing records with a blank field in cmn_location must be identified and back-populated using a defined data enrichment strategy before enforcing the mandatory constraint.
• Automated integrations: Review all inbound and outbound integrations, APIs, import sets, and data sources to ensure they populate the cmn_location field. Update and test integration mappings where necessary.
• External tools syncing to the CMDB must be updated to pass valid location IDs; otherwise, REST API payloads will be rejected.
• Inbound data integrations (e.g., LDAP or Active Directory user imports) will fail if location data isn't mapped, or they may accidentally create blank location records without parents

Downstream:

• Workflows and approvals that route based on location might  fail to proceed if the location  is malformed.
• Hardware Models or Configuration Items (CIs) without a location fail hierarchy mappings in dashboards, complicating structural tracking and reporting