Skip to main content

Configuration Change Management

This article describes how the Brinqa Platform tracks changes to Configuration Items — such as Flows, Views, Dashboards, Navigation Menus, User Defined Libraries, and Mail Templates — so you can see who changed what, compare versions, and restore a previous version if needed.

Why version Configuration Items?​

Configuration Items represent the customizations you build in your Brinqa instance — Flows, Views, Dashboards, Navigation Menus, User Defined Libraries, and Mail Templates. Without a record of changes, it can be difficult to answer who changed this, when, and what did it look like before — especially after an unwanted change or an app/connector upgrade that touches shared configuration.

To address this, the Brinqa Platform automatically keeps a version history of every Configuration Item and gives administrators tools to review, compare, and restore previous versions.

Automatic version history​

Every time a Configuration Item is created, updated, or deleted, the platform records a snapshot of that change. Updates that don't actually change any business-relevant field (for example, a save with no real edits) are skipped, so the history isn't cluttered with no-op entries.

The platform automatically retains the most recent 50 versions of each Configuration Item, pruning older versions in a daily maintenance job. If you need a longer retention window for compliance or audit purposes, contact Brinqa Support.

Reviewing history on a Configuration Item​

Flows, Views, Dashboards, Navigation Menus, User Defined Libraries, and Mail Templates each have a History button available from their editor. Clicking it opens a version history panel for that item, showing:

  • Timestamp — when the change was made.
  • Action — Created, Updated, or Deleted.
  • Changed by — the user who made the change.

Select two versions and click Compare selected to open a diff viewer showing exactly what changed between them, with:

  • Side-by-side or unified diff views.
  • Light and dark theme toggles.
  • A fullscreen mode for reviewing larger configurations.
  • A property-level view that highlights only the properties that changed, with the option to show or hide unchanged properties.

From the diff viewer you can select specific changes and apply them, or apply an entire previous version. If the item was deleted, the panel shows a banner letting you restore it. If you have unsaved edits in the current editor, Brinqa warns you before applying a version, since doing so replaces your unsaved changes.

Version Control (Global Change Control)​

For a platform-wide view of configuration changes, navigate to Administration > Settings > Version Control. This page lists every tracked change across all Configuration Items — not just the types that have an inline History button — with columns for Timestamp, Name, Type, Changed By, and Action.

Use the filters at the top of the page to narrow the list by name, timestamp, type, changed-by user, or action. Click the filter icon next to a row's name to quickly filter to just that item. As with the inline History panel, select two entries and click Compare selected to view their diff, or Clear selection to start over.

info

Access to the Version Control page requires the appropriate administrative permission for your account. Contact your Brinqa administrator if you don't see this option under Administration.

Comparing configuration files​

From the Version Control page, click Compare Config Files to compare a configuration export (a ZIP of configuration JSON files) against your platform's current state — useful for pre-upgrade impact analysis or comparing configuration across environments.

  1. Drop a settings ZIP file onto the upload area, or click to browse for one.
  2. Click Compare. This can take a couple of minutes for larger configuration sets.
  3. Review the results, grouped by category, each showing a count of detected changes. Use the search box and the All / Create / Update / Delete toggle to narrow the list.
  4. For each change, Brinqa shows the File Entry (from the uploaded file) alongside the Platform Entry (the current state on the platform, or a note that it doesn't exist yet). Choose to create the new entry or keep the existing version.

System (out-of-the-box) content is marked with an OOTB chip and can't be applied, since Brinqa manages that content directly.

Last updated on