CASC Change Overview

This epic improves how users identify, review, and process configuration changes managed through CASC. Instead of working primarily with technical YAML file differences, users get an object-based view that reflects the XDM configuration objects they know from the user interface. This helps teams understand what has changed, who changed it, and which changes should be exported, committed, restored, or synchronized.

Details
Epic
XEP-9 - CASC Change Overview
Status
Approved
Progress

2 Stories - 0 completed - 2 in progress

0% completed

Problem Statement

Today, XDM can load configuration from Git-based YAML files and recreate the corresponding objects in XDM. Users can also export XDM objects back into YAML. However, many users actively develop configuration changes in the XDM user interface before moving them into Git.

When multiple users or teams work in parallel, it becomes difficult to identify which objects have changed since the last CASC/Git state and which changes need to be exported or committed. Technical differences in YAML files can also be confusing, because users cannot easily understand which UI-level change caused which YAML-level change.

Customer Value

Customers gain a clearer and more reliable way to manage configuration changes across XDM and Git. They can identify relevant changes on the object level, reduce confusion caused by YAML-level differences, and better coordinate parallel work across multiple users or teams.

The feature helps customers:

  • quickly detect deviations from the CASC/Git state,

  • understand which XDM objects were changed,

  • reduce manual analysis of YAML files,

  • export or commit only relevant changes,

  • trace changes back to responsible users,

  • handle deletions more safely across environments,

  • better control synchronization behavior,

  • and manage permissions more consistently across test and production environments.

Scope

This epic covers an object-focused CASC change overview and related actions:

Object overview and navigation

  • Overview of all objects managed by CASC

  • Presentation based on the functional CASC object model rather than the technical YAML file structure

  • Navigation from the overview to the corresponding XDM object

  • Optional display of objects that are not managed by CASC

Change detection and status

  • Compare the current object state with the CASC/Git state

  • Supported statuses: , , ,

  • Manual refresh of the CASC state

  • Regular background comparison between current XDM objects and the known CASC/Git state

  • Handle deleted objects so deletions can be represented and applied in other environments

Export

  • Export changed objects in a CASC-compatible format

  • Create a ZIP export of changed objects

  • Optional export of permissions

Git integration and synchronization

  • Commit changed YAML files to the connected Git repository

  • Optional commit message

  • Stronger user reference in commits so Git history reflects the actual responsible user where possible

  • Administrator setting for automatic Git synchronization or read-only Git mode

Restore

  • Restore the complete environment to the current CASC/Git state

  • Restore selected objects to the current CASC/Git state

Change history and traceability

  • Improved change history for changes made by multiple users

  • Show which user changed which object property or option

  • Line-based change view for scripts and libraries, including user attribution

Permissions

  • Include permissions in CASC handling

  • Optional permission comparison

  • Export permissions

  • Enable or disable permission recipients depending on the environment

Stories
Story Title Release Status
XPU-1490 CASC Object Change Overview Approved
XPU-2697 Synchronize CASC configuration changes with Git Approved

UBS Hainer GmbH - generated from Jira at Tue, 3 Nov 2026 13:29:07 GMT