Lasernet Keep Changes That Affect Existing Autoform DM Workflows

To enable us to deliver the changes and improvements in Lasernet Keep 11, we have removed some legacy features and systems from the application. As a result, these legacy systems are no longer available or supported.

Removing these legacy features:

• Helps us to deliver new functionality faster.

• Eliminates the testing, support, and maintenance overheads associated with them, enabling us to focus our resources elsewhere.

• Removes the requirement for thick-client installation as part of your system.

• Supports our goal of consolidating (into responsive web apps) and improving all the features that previously made Autoform DM the document storage archive of choice.

• Helps us deliver on our “secure by default” promise by reducing the number of possible avenues for attack and eliminating the use of older, legacy protocols.  

For more information and assistance with any of the changes described on this page, contact Lasernet Support.

Autoform DM Versions Supported for Upgrade to Lasernet Keep

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.

Removed or Deprecated Modules and Features

The following modules have either been removed from Lasernet Keep and are no longer available or supported, or have been deprecated.

Web Services V1

This web service has been removed from Lasernet Keep.

Affected Systems

• DM Client.

• Custom integrations that use Web Services V1.

Mitigation or Workaround

Update custom integrations to use the Keep REST API.

See DM Client and Client Applications for guidance on migrating away from client apps.

Web Services V2 (SOAP)

This web service is no longer supported in Lasernet Keep. This service has been deprecated and disabled, but not removed. It will be removed fully in a future version of Lasernet Keep.

If you need to upgrade to Keep but still rely significantly on Web Services V2, it is possible to re-enable it to extend the window for migrating to the REST API. Contact Lasernet Support for further information or assistance.

Affected Systems

• DM Client.

• Custom integrations that use Web Services V2. Specifically, the following service URLs:

  • <baseurl>/pdmwebsvc-v2/document

  • <baseurl>/pdmwebsvc-v2/search

  • <baseurl>/pdmwebsvc-v2/import

  • <baseurl>/pdmwebsvc-v2/email

  • <baseurl>/pdmwebsvc-v2.1/document

  • <baseurl>/pdmwebsvc-v2.1/search

  • <baseurl>/pdmwebsvc-v2.1/import

  • <baseurl>/pdmwebsvc-v2.1/email

Mitigation or Workaround

Update custom integrations to use the Keep REST API.

See DM Client and Client Applications for guidance on migrating away from client apps.

DM Client and Client Applications

The DM client is no longer supported with Lasernet Keep.

Affected Systems

Any client applications (either custom-written or native applications).

Mitigation or Workaround

Replace the current workflow with the built-in tools in Lasernet Keep (such as the new search feature and document upload feature).

Some apps’ functionality is not directly replicated in Keep, most notably:

• Photo capture app

• Signature capture app

If those apps are currently used, contact Lasernet Support to discuss your workflow, so we can help you to find a solution and discuss any blockers in upgrading that might require further development of Keep.

Batch Process Manager (BPM)

Lasernet Keep does not support BPM.

Affected Systems

BPM jobs, exports, and imports.

Mitigation or Workaround

The Keep Upload Module included in Lasernet provides a deeply customizable, adaptable, and powerful solution for any import or export requirements.

Alternatively, the Keep REST API can be used to retrieve documents in bulk for further processing.

If BPM is used and you require more information about these alternative solutions, contact Lasernet Support to discuss your workflow, so we can help you to find a solution and discuss any blockers in upgrading that might require further development of Keep.

Remote Document Search

The remote document search feature in Autoform DM has been replaced in Keep by a more flexible integration feature that:

• Enables third-party systems to launch search configurations and upload configurations.

• Provides a secure launch capability to protect supplied key values.

Affected Systems

Third-party systems that integrate with Autoform DM through its legacy remote document search feature.

Mitigation or Workaround

Update the third-party system to use Keep’s search integration feature. For more information, see Integrate Third-Party Software with an Upload or Search Configuration. For assistance with using the new integration feature, contact Lasernet Support.

SQL Searches

SQL Searches are deprecated in Keep and can be modified only through the REST API. The /sql-search REST API endpoint remains available but is not included in the Keep REST API documentation and will be removed in a future version.

For more information, contact Lasernet Support.

Breaking Changes

Some application behaviors have changed in Lasernet Keep in ways that might require you to implement workarounds to ensure that your system continues to operate after upgrading to Keep.

Removal of Search Columns for Notes

Note Status, Note Label, and Note Description can no longer be configured as search result keys.

Affected Systems

Search applications that use any of these keys as search result keys.

Mitigation or Workaround

Keep configurations (which were termed applications in Autoform DM) that use these keys as search result keys will continue to work, but those keys will be automatically filtered out.

When modifying or updating search configurations that use them, we recommend removing these keys from the result keys part of the search configuration.

Context Root Change and Deep Links

In line with the software’s name changing to Lasernet Keep, the context root has changed from /dm to /keep.

Affected Systems

Any URLs that contain /dm will no longer work, including already generated application launch URLs (for document import applications).

The list of affected URLs includes:

• Removed

  • <baseurl>/pdmwebsvc

  • <baseurl>/pdm/action/remoteSearchAction|remote.jsp (see Remote Document Search)

• Disabled

  • <baseurl>/pdmwebsvc-v2

  • Contact Lasernet Support for further advice about updating custom integrations to use the Keep REST API.

• Disabled by default

  • The following endpoints support legacy BrowserWeb integrations.

  • For security, they are disabled by default when they are not in use. To enable these endpoints, contact Lasernet Support.

    • <baseurl>/pdm/servlet/TemenosDocumentUploadServlet

    • <baseurl>/pdm/servlet/TemenosDocumentDownloadServlet

    • <baseurl>/pdm/servlet/NoFileServlet

    • <baseurl>/pdm/servlet/TemenosDocumentSearchServlet

• <baseurl>/dm (Keep equivalent is <baseurl>/keep)

• <baseurl>/dm/integrations/doc-import-launcher.js (Keep equivalent is {baseurl/keep/launcher.js)

Mitigation or Workaround

For further assistance and information, contact Lasernet Support.

Newly generated application launch URLs using doc-import-launcher.js will work and will go to the new path.

Note

doc-import-launcher.js is deprecated in this release. Although it still works in Lasernet Keep, you should update integrations to use /keep/launcher.js instead (which includes extra functionality to launch document searches).

REST API Changes

The Autoform DM REST API and Keep REST API have the following notable differences.

Deprecations

Although these Autoform DM endpoints still work in Keep, they are not included in the Keep REST API documentation and have preferred and documented alternatives in the Keep REST API (except for /sql-search).

Removals

The following endpoints have been removed. These are breaking changes for any integration that uses them:

• /client-apps

• /note-defs

  • Note definitions no longer exist and are not supported. However, document notes can be accessed through the /documents resource.

    • /documents/by-cuk/{cuk}/notes

    • /documents/by-id/{id}/notes

• /users/{name}/contacts

Model Changes

The document.def model used with /document-defs has changed. keyDefs becomes keyDefBindings and is now an array of objects rather than strings.

The key.def model used with /key-defs has changed. docDefs becomes docDefBindings and is now an array of objects rather than strings.

The new models are versioned as v3. You can continue to use the old models as v2.

These changes support the Systems Operations feature. For more information, see Asynchronous Processing of Keep System Operations.