The same field appears in different sections, with each section showing conditionally

Minaj_F
Tera Contributor

Hello!

 

We are currently investigating health scans with the finding "Same field twice on one form." There are fields appearing in different sections, but these sections are displayed conditionally due to UI policies. As a result, only one section with the particular field is shown on the form at any given time. Therefore, there are no duplicated fields on a form when viewing it. Is this use case valid?

 

Thank you

1 ACCEPTED SOLUTION

sunil maddheshi
Tera Guru

@Minaj_F 

The "Same field twice on one form" finding in health scans is a generic rule that flags fields appearing more than once, but it does not account for UI policies or conditional section visibility. If a field is only ever displayed once at a time due to UI policies, it does not create actual duplication from a user perspective.

However, here are a few things to consider:

  1. Health Scan Rule Behavior – ServiceNow health scan rules are designed for general best practices, but they don’t always account for dynamic UI behaviors. This rule might not distinguish between a real duplicate (both fields visible simultaneously) and a conditional one.

  2. Performance Impact – While UI policies control visibility, the field still exists in multiple sections of the form configuration. If a field appears in multiple places, it could impact maintainability (e.g., updates might require checking multiple sections).

  3. Validation with ServiceNow Best Practices – If this setup is necessary for your use case and does not impact functionality or user experience, you can document it as an exception. However, if there is an alternative way to achieve the same result (e.g., using a single field placement with dynamic content changes), it might be worth considering.

Please mark correct/helpful if this helps you!

View solution in original post

1 REPLY 1

sunil maddheshi
Tera Guru

@Minaj_F 

The "Same field twice on one form" finding in health scans is a generic rule that flags fields appearing more than once, but it does not account for UI policies or conditional section visibility. If a field is only ever displayed once at a time due to UI policies, it does not create actual duplication from a user perspective.

However, here are a few things to consider:

  1. Health Scan Rule Behavior – ServiceNow health scan rules are designed for general best practices, but they don’t always account for dynamic UI behaviors. This rule might not distinguish between a real duplicate (both fields visible simultaneously) and a conditional one.

  2. Performance Impact – While UI policies control visibility, the field still exists in multiple sections of the form configuration. If a field appears in multiple places, it could impact maintainability (e.g., updates might require checking multiple sections).

  3. Validation with ServiceNow Best Practices – If this setup is necessary for your use case and does not impact functionality or user experience, you can document it as an exception. However, if there is an alternative way to achieve the same result (e.g., using a single field placement with dynamic content changes), it might be worth considering.

Please mark correct/helpful if this helps you!