File Versions
The File Versions page browses every file managed in a NomaUBL environment (XSL, RTF, XML, configuration, scripts…), shows the version history of each file, and lets administrators edit text files, view PDFs, restore a previous version, or package files for transfer between environments.
The file repository is shared across all NomaUBL deployments — the page applies whether the source ERP is JD Edwards, SAP, NetSuite or a custom system. JDE-extracted artefacts coexist with hand-edited files; their origin is recorded in the version history (see Source badge below).
At a glance
Layout
The page is split into two columns:
| Column | Contents |
|---|---|
| Left sidebar | Search box + tree of every versioned file in the environment. Folders are collapsible and show their file count. |
| Main panel | Toolbar + content area whose mode depends on the current selection (live file + history, package selection, editor or PDF viewer). |
Sidebar — file tree
| Element | Description |
|---|---|
| Search box | Live filter on the file path (case-insensitive substring match). |
| Folder rows | One per directory. Click to expand / collapse. The badge on the right shows the total number of files contained recursively. |
| File rows | One per file with its short name and size (B / KB / MB). Click to select. |
| Select-all row (package mode only) | Toggles selection for every file currently filtered. |
When Package mode is active, every row also displays a checkbox; folder checkboxes show an indeterminate state when only some children are selected.
Single-file mode (default)
Selecting a file in the sidebar opens its version history in the main panel.
The toolbar shows the file path and a primary Upload new version action (file picker — uploading replaces the live file and snapshots the previous live file as a new historic version).
Version history table
| Column | Description |
|---|---|
| Version | live for the current file, v1, v2… for historic versions. |
| Date | When the version was created. |
| Source | How the version was produced — see source badges below. |
| Comment | Free-text comment captured at upload (e.g. Edited in browser). |
| Size | Stored size of the version. |
| Actions | Per-row buttons — see row actions below. |
Source badges
| Badge | Meaning |
|---|---|
upload (blue) | Manually uploaded from the toolbar or saved from the in-app editor. |
restore (orange) | Generated by restoring an older version (the previous live file is automatically snapshotted under this source). |
jde_bip (purple) | Extracted from JD Edwards BIP — JDE-specific source. |
| (other) | Any other origin recognised by the API. |
Row actions
| Icon | Available on | Description |
|---|---|---|
| 👁 View | Live row, PDF files | Opens the PDF inline in the main panel via an <iframe>. |
| ✏️ Edit | Live row, text files | Opens the file in the built-in Monaco editor. |
| ⇄ Compare with previous | Every row except the oldest, text files | Opens the side-by-side comparison of this version against the one just before it — see Compare mode below. |
| ⬇ Download | Every row | Downloads the file (live or historic). Historic downloads are named <filename>.v<n>. |
| 🔄 Restore | Historic rows only | Promotes the historic version to the new live file. A confirmation dialog appears first; the previous live file is snapshotted as a new restore version. |
Edit mode (text files)
Clicking the Edit icon on the live row of a text file opens the Monaco editor (the same engine VS Code uses) directly inside the main panel.
| Aspect | Behaviour |
|---|---|
| Languages auto-detected | .xml / .xsl / .xslt → XML; .json → JSON; .css → CSS; .js → JavaScript; .html / .htm → HTML; everything else → plain text. |
| Recognised text extensions | xml, xsl, xslt, json, txt, cfg, csv, html, htm, css, js, properties, md, log. |
| Save | Uploads the buffer as a new version with the comment Edited in browser. The previous live file is snapshotted automatically. |
| Cancel | Closes the editor without saving. |
| Editor options | Monospace font, minimap on, wordWrap: off, tab size 2, paste-formatting on, dark theme. |
Compare mode
For any text file (XSL, XML, JSON, SQL, properties, MD, CSS, JS, HTML, TXT, CSV, CFG, LOG…), two versions can be opened side-by-side — the same diff view VS Code shows, useful when reviewing what a template or configuration file picked up over time. The current live file is included in the picker, so you can also compare any historic snapshot against today's state.
Opening the comparison
Two ways to enter the comparison:
- One-click — compare with previous. Click the ⇄ icon on any row of the history. The selected version opens on the right, the version just before it on the left. This is the common case when you only want to see what that snapshot introduced.
- Compare two arbitrary versions. Turn on Compare in the toolbar, then click two rows in the history table — the order picked sets which side each version lands on. The toolbar caption shows the selected pair and offers a Confirm button to open the comparison.
The side-by-side view
| Aspect | Behaviour |
|---|---|
| Layout | Full-screen, older version on the left, newer on the right. The header bar shows the file path, the two version labels and the running count of changed lines. |
| Highlighting | Each row coloured by change — green for added, red for removed, both shades for modified. Unchanged regions can be folded. |
| Syntax colouring | The same Monaco-based engine used in Edit mode — language auto-detected from the file extension. |
| Scroll | Synchronised between both panes — scrolling either side moves the other in lockstep. |
| Close | Escape or the Close button in the header returns to the history table. |
Binary files (PDF, ZIP, images…) do not appear in the picker — comparison is only available on the text extensions listed under Edit mode.
PDF viewer
Clicking the View icon on the live row of a PDF opens the file inline in the main panel via a secured <iframe> (the auth token is forwarded as a query parameter when present). Click Close in the toolbar to return to the version history.
Package mode
Toggling Package mode in the toolbar switches the page from single-file actions to multi-file selection for transfer between environments.
| Action | Description |
|---|---|
| Export | Exports every selected file as a package to download. The toolbar caption shows the number of selected files and the total size. |
| Import | Imports a previously exported package (.zip). The status message reports the number of files imported. |
Selection helpers:
- Per-file checkboxes in the tree
- Per-folder checkbox — toggles every descendant file at once; shows an indeterminate state when partial.
- Select all row at the top — toggles every file in the current filter.
Quitting package mode (toggling the button off again) clears the selection.
Status messages
Inline feedback at the top of the main panel auto-clears after 4 seconds:
Upload success — version N createdRestore success — version N restoredExport success — N filesImport success — N files- API error message on failure.
Tips & best practices
- Use the editor for in-place tweaks, the upload for bulk replacements. The editor saves a new version with a clear
Edited in browsercomment, which is easy to spot in the history. - Restore is non-destructive. It snapshots the current live file before promoting the historic one, so an accidental restore can itself be rolled back.
- Package mode is the supported way to ship XSL / RTF templates between dev → recette → production. Avoid hand-copying files across environments — packaging preserves the version metadata.
- Skip JDE-extracted files (
jde_bipsource) when packaging unless the receiving environment also runs against the same JDE — they are typically environment-specific outputs, not portable assets. - Keep an eye on the file count badge per folder when working on large XSL trees — it's the quickest way to spot a mis-packaged subset.
- Download a historic version before restoring if you want to keep a local copy of both the current and the historic file outside NomaUBL.