Archer announces the General Availability of Document Governance Release May 27th, 2026

Summary

Archer announces the General Availability of Document Governance Release May 27th, 2026

Release Details

Two new capabilities ship in this release: reviewers can now route rejected documents to any prior workflow stage, and admins can map Doc Gov metadata fields to Archer directly from the UI without engineering involvement.

Send Rejected Documents to the Right Stage

Previously, rejecting a document always sent it back to the document owner within the same review stage, even when corrections needed to happen earlier in the workflow. Reviewers can now choose exactly which stage a rejected document returns to.

How it works:

• When rejecting a document, the reviewer selects a target stage from a dropdown showing all prior stages and the current stage.
• A rejection reason is required before the rejection can be submitted.
• If no stage is selected, the document returns to the current stage, consistent with existing behavior.
• When the document arrives at an edit stage, an edit draft is automatically created and opened.
• All stages from the returned point forward are reset and must be completed again before the document can advance.

What stays intact:

• All document content is fully preserved when a document is sent back.
• Review notes and tracked changes accumulate across every pass through the workflow, giving each reviewer complete context.
• The activity log reflects each rejection with the destination stage name for a clear audit trail.

Map Metadata Fields to Archer

Connecting Doc Gov metadata fields to Archer previously required an engineer to manually update a configuration file. Admins can now set up and manage these mappings directly in the Doc Gov UI.

How to map a field:

• Navigate to the global metadata table and click the menu icon on any eligible metadata field.
• Select "Settings" to open the mapping modal.
• Enter the Archer GUID for the field and click Validate. The system confirms the GUID against the Archer API and displays the matched field name and type.
• Click Save. The metadata table updates to show the field as mapped, with the last-updated date visible on hover.

For pick list fields:

• After GUID validation, each active value in the list is displayed with a dropdown to select its corresponding Archer value.
• All active values must be mapped before saving.

Additional controls:

• Admins can toggle whether individual document types sync to Archer at all, without any engineering changes.
• Once mapped, field data is automatically pushed to Archer when a document reaches the Publish stage.
• Mapping is restricted to admin users.

Link Changes Now Captured in the Activity Log

All additions and modifications to links within a document are now recorded in the activity log, ensuring a complete audit trail of link changes alongside other document edits. When redlines are enabled, URL changes appear with the original URL struck through and the updated URL shown as a greenline.

Release Window

We will be performing the upgrade on May 27th, 2026 between 9PM-12AM CT.

Originally posted on May 26, 2026 in the Archer Community.