--- title: "Notable Lasernet Keep and Autoform DM Versions" slug: "notable-keep-autoform-dm-versions" description: "This page lists specific versions of Keep or Autoform DM where notable features have been added, changes have been made, or specific upgrade requirements have been introduced." tags: ["Autoform DM", "Keep", "Upgrade"] updated: 2026-03-16T14:28:27Z published: 2026-03-16T14:28:27Z canonical: "kb.lasernetgroup.com/notable-keep-autoform-dm-versions" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt > Use this file to discover all available pages before exploring further. # Notable Lasernet Keep and Autoform DM Versions ## Overview Historically, particular versions of Autoform DM (which preceded Lasernet Keep) have added notable features, included other notable software changes, or introduced specific upgrade requirements. This page provides a high-level description of these software versions to help you prepare an upgrade from Autoform DM to Lasernet Keep; in particular, in situations where the upgrade spans multiple notable versions. As this document contains high-level summaries, it is not a replacement for the release notes or new features document for a specific Keep or Autoform DM version, or for the Autoform DM compatibility matrices. ## Forced Upgrade Path Particular Autoform DM software versions impose a forced upgrade path, meaning the software must be sequentially upgraded through the following versions in the specified order, before eventually upgrading to the latest version of Lasernet Keep. These are: - 6.842 – Last Borland (BES) version for staging the migration - 6.905 – First JBoss version for BES migrations - 6.912 – First documented and officially maintained version - 7.0.5 – v4 Migration Agent – required for v4 migrations only - 7.3.0 – Key Migration process - 9.2.2 – Additional Keys Support > [!WARNING] > Important > > The only Autoform DM versions that are supported for upgrade to Lasernet Keep are Autoform DM 10.0 and later. > > To upgrade an earlier version of Autoform DM to Lasernet Keep, you must first upgrade to Autoform DM 10. Then, you can upgrade to Lasernet Keep. We recommend contacting [Lasernet Support](https://support.lasernetgroup.com/new-ticket) if you are unsure of the upgrade process, particularly when upgrading from significantly older versions. ## Notable Versions This section details each notable version, oldest to newest. When upgrading, ensure you review every version between and including your from/to versions. For example, if you were upgrading from version `d` to `g`, you should review notes for `d`, `e`, `f` and `g` as they will all apply. Items mentioned here fall into the following categories: - **Introduces**: Something new that was introduced to the version, which is of significance in the context of an upgrade. - **Requires**: Something that is specifically required or enforced to proceed past this version. - **Removes**: A feature that was removed from the software and is no longer supported. ### 7.1.0 **Removes** - Support for the `onLogin`, `onDocumentCreate` and `onDocumentUpdate` serverscript functions. ### 7.2.0 **Requires** - Use of new `/dm` context path for front end. Existing integrations are still available on `/pdm`. - Various items including users, document definitions, searches, imports, and groups must all have unique names (labels). Database updates will fail for any duplicates and need to be manually resolved ### 7.3.0 **Introduces** - The key migration feature with support for more than 55 keys, a requirement for progressing to any future versions. ### 8.0.0 **Removes** - The ability to use a single key column for multiple types of data across document definitions (meaning a 55 key definition global limit). **Requires** - The key migration process to have been completed for upgrades from previous versions. - A link between all records in `tblDocumentHistory` to `tblDocuments`. Database updates will fail for any orphaned records. ### 8.1.0 **Removes** - Support for serverscripts. ### 8.3.0 **Requires** - A new licence to be generated. ### 8.4.0 **Requires** - All name values must pass validation, preventing previously allowed names such as `name-`, `-name` and `name–name`. Any violations will cause database update failures. An auto-fix option is available in this update from 9.2.0 onwards, see logs for details. ### 9.0.0 **Removes** - Java applet support from default installs. - Ability to execute SQL over webservices v1. - Support for JFinder connecting via HTTPS (SSLv2 Hello). **Introduces** - Generation of the `installation-record.properties` to make future upgrades easier. > [!NOTE] > Note > > Large databases may experience longer database upgrade times; the transaction timeout was raised to facilitate this. ### 9.2.0 **Removes** - The ability to store `NKEY` values of more than 19 digits and 2 decimals. Attempts to store documents violating this will fail. This validation can be disabled using a system property - The ability to specify a revision number greater than the current document revision when using `PUT /documents` in the REST **Document Resource**. For example, if you specify a document with revision `2` in the update, and the current revision is `1`, it will now fail as intended. **Requires** - (Oracle DB only) `SELECT` permission to the view `DBA_IND_COLUMNS`. If the update `920003 `fails, ensure this permission is set. - ddl permissions (for example `db_ddladmin`) in the database at runtime. Used by the additional key feature in order to DROP and CREATE columns on demand. - A link between all records in `tblKeyData` and `tblKeyDefinitions`. Will fail update `920007` for any orphaned rows. - All entries in `tblKeyDefinitions` to have a valid 'system identifier', for example `NULL`, `SKEY1-25`, `NKEY1-15` or `DKEY1-15`. Invalid entries will cause database update `920009` to fail. - A link between all records in `tblDocuments` / `tblDocumentHistory` and `tblUsers` (ownerId to userId). It will fail updates `920010` / `920011` for any orphaned documents. An auto-fix option is available in this update, see logs for details. **Introduces** - Support for “additional keys” outside of the 55 key limit, paired with the 7.3.0 release - Optional “document encryption” feature. Any upgrades *after* this point will need to be aware that documents may be encrypted, and the keystore will be a crucial part of the process ### 9.2.1 **Requires** Any columns specified in new SQL searches from now on must be escaped, for example, instead of `WHERE my_key_name =` , on MS SQL it should be `WHERE [my-key-name] =`. This is dependant on the database provider used. ### 10.0.0 **Removes** - The ability to pass MD5 hashes across for login (such as in the remote search linking functionality). - Support for any Java applets, such as the PC Doc Import and Multiple Printing. Notably, this also has the following impact: - Configuration packs containing `document-import` entries will fail to validate. - Existing import applications will be deleted on upgrade (with details included in the `legacy-import-data.log` log file). - The Multiple Printing feature has not been replaced. - The PC Doc Import feature has been replaced by the new v2 document import applications. **Requires** - Passwords in configuration packs must be hashed (it is now possible to export these). **Introduces** - The API Key for authenticating REST API integrations. We recommend using this for any integrations going forward. ### 10.1.0 **Removes** - Support for deprecated TLS protocols (TLSv1, TLSv1.1). Therefore, not compatible with earlier versions of the DM client (such as 10.1.1 and earlier). **Introduces** - A settings change so that all audit events in the following categories are switched on by default: login, groups, users, passwords, settings, documents, definitions, execution. ### 10.3.0 **Removes** - `docname` column from `tbldocuments` and `tblDocumentHistory`. **Introduces** - A change to default remote search behaviour – the results table will now be shown by default, even if there is only one record. It is possible to revert to the previous behaviour, if preferred. See Remote Search. ### Keep 11.0.0 **Removes** - The Autoform DM user interface (previously accessible through the `.../dm` context path). - Webservices v1. - Autoform DM Client. - Centralised application resource (replaced by search and upload specific resources). **Introduces** - Completely new user interface for Keep. - New `.../keep` context path to access Keep. ### Keep 11.1.0 **Removes** - `Formpipe Software` from Keep’s default installation path (`C:\Program Files\Formpipe Software\Lasernet Keep\...`) and replaces it with `Lasernet Group` (`C:\Program Files\Lasernet\Lasernet Keep\...`). **Introduces** - Lasernet Group branding to the user interface for Keep. - Lasernet Group branding to the Keep installer, along with new default alias and password values for generated HTTPS certificates.