Hi everyone,
I'm trying to understand how source control works for UI Pages that are ultimately stored in ServiceNow as a single sys_ui_page record.
My goal is to determine whether changes can be tracked at the individual source-file level (for example React, TypeScript, CSS, utility files, etc.) or whether all modifications are ultimately represented as changes to a single ServiceNow artifact.
For example, if multiple developers are working on a UI Page:
- Developer A modifies one frontend component.
- Developer B modifies a different piece of logic.
- Both developers commit their changes through Git/Bitbucket.
What I'm unsure about is:
- Does Git/Bitbucket actually see those changes as separate files?
- When the application is linked to ServiceNow Source Control, are those files stored individually in the repository or are they bundled into a single UI Page artifact?
- If two developers modify different parts of the same UI Page, can Git perform normal file-level diffs and merges, or does ServiceNow ultimately treat everything as a change to the same sys_ui_page record?
- Has anyone worked with UI Pages, Now SDK, React-based experiences, or similar implementations where source control provided visibility into individual file changes instead of only record-level changes?
I'm mainly trying to understand what is actually stored in the repository and how granular the change tracking can be, rather than looking for workflow recommendations.
Thanks!
