The Laserfiche 10.4 release includes a variety of new features, such as extension of Federated Search capabilities, improvements to the handling of Microsoft Office documents, the ability to assign a map location to a document, and more flexible records management options. In addition, the 10.4 release includes many bug fixes and performance enhancements.
New Features in Federated Search – Federated Search can now be configured to allow users to search across Windows network drives and Google Drive accounts. Also, in addition to respecting Laserfiche security settings, Federated Search now allows administrators to control access to external data sources, such as websites and network drives, as some users or departments may need greater access than others.
New Features for Office Documents – The web client installation now includes the Laserfiche Document Preview Service, which allows you to display Microsoft Office documents directly in the document viewer or the folder browser preview pane without needing an Office Online installation or account. This allows users to easily view their documents without needing to download them or use the Office Integration. In addition, users can now create Office documents directly in the repository without needing to first create them externally and import them.
Map Locations – Laserfiche 10.4 introduces the ability to associate a location on a map with a document or folder using Google Maps, Esri cloud maps, or Esri on-premises maps. Each location has both associated GPS coordinates and a location description; by default, the location description is the street address of the location. This location can be viewed in the details pane of the folder browser or document viewer, or used to perform a search.
Flexible Records Management – Laserfiche Records Management has been updated to enable greater organizational flexibility in how records are handled, while still enforcing security restrictions to help them meet their compliance needs. Cutoff and retention policies can now be assigned directly to any entry in the repository, without needing to be located within record series. In addition, holds (previously called freezes) can be placed on any entry in the repository, regardless of its folder structure or whether it is a record.