Alfresco integration

When the app is configured against your Alfresco (same reverse proxy, same login session), you can compare versions of a stored document without downloading anything manually — and file the result straight back.

Looking for the wider integration story, including the REST API for any DMS/ECM? See Integrations.

The version-pick page

Open …/alfresco/{nodeRef} (typically via a link from Alfresco Share). The page shows the document's version history in two dropdowns — Original (pre-selected: oldest) and Revised (pre-selected: newest) — plus the same Output options as the main Compare page. Your existing Share session is used for every Alfresco call; nothing is stored. If the session expired you'll see a friendly "reload from Share" message.

A node with fewer than two versions, or an unsupported file type, gets a clear explanation page instead of the picker.

Comparing a draft against a stored version

Under each dropdown sits "use a file from my computer". Tick it and the dropdown becomes a drop tile — so you can compare, say, the approved v3.0 from Alfresco against a draft on your desktop before checking it in. Only one side can be a local file (two local files is what the main Compare page is for); ticking one side unticks the other automatically.

Compare, then Save to Alfresco

Compare works exactly like the main page — same outputs, same options, same ✔ Verified badge — and the result downloads to your browser. Then a Save to Alfresco button appears (bottom right). One click:

The exact file you just reviewed is sent back (byte-for-byte the download — the server never keeps a copy between the two steps).
The server first verifies it against the tamper-evidence embedded in the file — an altered or foreign file is refused, never filed.
It is stored as a new document (never a new version of the compared one) in the configured folder next to the source document — created automatically on first use; repeated saves get -1, -2 suffixes.
If your deployment maps filing metadata to Alfresco properties, the extracted values (company, state, form number, …) are stamped onto the node as searchable properties, and the output is linked to the document it redlines.
The button turns into Open in Alfresco — click it to land on the saved document's Share page. Saving the same output twice is blocked; a failed save re-enables the button for a retry.

Any note-worthy outcome ("metadata properties not applied: …", "not linked: …") appears in the warnings box — the save itself still succeeds.

Changing anything — a version, the local file, any output option — resets the button and clears the previous results: the Save/Open button can only ever act on an output produced by the current selections.