Versioning / File History
Keep several versions of a file together with unified metadata. After you upload a new version, the file’s detail view shows a Versions section containing the current and earlier versions. The current version’s filename is highlighted in bold.
To add a new version of an existing file:
- Click on the file you want to add a new version of
- In details view click on the blue ‘Upload new version‘ button on the right side
- Drag a file to the upload area or left click it to browse for the file from your computer
The uploaded file becomes the current version. Earlier versions remain in the Versions list, where the available controls let you restore or download them. Deleting an individual version permanently removes that version.
You can send every current version to approval. So if your document was rejected by approvers before and you upload a new version of the file, you can send it for an independent approval again!
See which version a task belongs to
The Versions list displays task status beside the version the task applies to. For example, an active approval request appears beside the version submitted for approval.
If you upload a new version while that approval is active, the approval indicator remains beside the earlier version. The newly uploaded version is highlighted separately as the current version. An approval indicator on an earlier row therefore does not mean the current version has been sent for approval.
You can also configure any folder with toolbar button ‘Columns‘ to display ‘Updated at:’ field. This will add a column to the list view showing the date of document’s latest version.
Here’s a video overview of how the file history feature works in Folderit:
ASiC container versions
ASiC signature containers use the common file detail pages and support file version history. Open the container and review Versions to distinguish the current container from earlier versions and use the available download or restore controls.
An ASiC container’s contents may be processed in the background. Downloading and signing can be available while contents processing continues. Check the version and its contents when preparing a signing package.
Signed contents are protected. Complete the package before signing. If the documents change, prepare an unsigned package/version for the new signing process; do not treat signatures on an earlier version as signatures on the changed documents.
For Baltic eID credentials, container preparation, and signing steps, see eID Electronic Signatures. For international recipients without a supported Baltic eID, see Folderit eSign or DocuSign.