these are some of the features in the desktop client and not in the web client that I've noted and heard from our users about:

opening PDFs directly in Adobe to edit with seamless version generation upon closing (I just tested this to verify it still works)

being able to import files and access windows shell metadata such as windows creation date, etc

being able to import folders with files in them

being able to configure repository display options such as font size and font used

being able to drag items to emails in order to attach them (this is a big pain point for most of our new users)

being able to set custom keyboard shortcuts for different actions

being able to set permissions for a group of folders simultaneously instead of one at a time (ex select multiple folders, view access rights, and add a trustee plus set their rights)

If you need further details, let me know! I'm happy to give use cases for each and/or demonstrate what I'm talking about specifically over a follow-up call if you'd like.

Edit: one of our staff this morning was talking to me and reminded me that having the ability to access files through the windows interface (ex open file explorer and have Laserfiche show up as a pseudo network drive etc) would be very desirable too. Organizations that are used to being in a Windows environment and who transition to the Web Client will likely see a lot of issues purely because of how disjointed processes can become when working between a web-based and local Windows ecosystem.

Assessing end-user experience and feedback is crucial, yet it is important to recognize that users may not always fully understand the complexities of their requests. Some of the features you've identified as missing may be attributed to limitations inherent in the operating system, browser, or other technological constraints, rather than issues specific to Laserfiche. As a solution provider, not directly involved in product development, we can only offer assumptions about why certain features are implemented while others are not. For some feature requests, the trade-off between enhancing user experience and the potential impacts on performance, product branding, overarching objectives, and additional development costs may not align with Laserfiche's strategic priorities.

I have reviewed each item on your list to identify any known reasons or alternative solutions and have provided my findings based on that review. Should any representative from Laserfiche have a more official response, please feel free to correct or update my conclusions as needed.

opening PDFs directly in Adobe to edit with seamless version generation upon closing (I just tested this to verify it still works)

I believe this issue is primarily due to browser security restrictions. On Windows, users can specify which application is associated with a particular file type (e.g., setting Adobe Acrobat to open PDFs instead of Adobe Reader). This association is stored by the operating system; however, browsers do not have access to this information. The Windows Client, on the other hand, is not subject to these same limitations, allowing users to configure Laserfiche to open PDFs with their preferred application.

Additionally, Laserfiche may be constrained by Adobe's licensing terms regarding what can be integrated when deploying a web application. While Laserfiche may have more flexibility in integrating with the free Adobe Reader components, integration with the paid Adobe Acrobat components could be restricted. Laserfiche does have Snapshot which would allows PDFs created in Acrobat, and other filetypes created in other applications, to be saved to Laserfiche easily, similar to Print-to-PDF functionality as you are likely already familiar.  That said, it appears technically feasible for Laserfiche to develop a custom PDF integration, similar to the Office Plugin, potentially utilizing Laserfiche Web Tools. This component is designed to enhance interoperability between the web client and desktop applications. Furthermore, Adobe offers an SDK, which, in conjunction with the Laserfiche SDK, could be leveraged to build a more seamless integration.

being able to import files and access windows shell metadata such as windows creation date, etc

This is another instance of a browser limitation rather than an issue with the Laserfiche Web Client. The Laserfiche Windows client does support tokens such as %(FileCreated), which can also be utilized by tools like Import Agent, Workflow, and QuickFields. During document import, these tokens are replaced with the corresponding Windows file properties. However, the Laserfiche Web Client does not have access to the same tokens, as they are not exposed to the browser by the file system.

It is also important to note that these tokens can only be used to populate metadata fields and will not override the native "Created" and "CreatedBy" values in Laserfiche.

For further reference, please see: https://answers.laserfiche.com/questions/58502/Retrieving-original-document-properties#115756.

being able to import folders with files in them

This limitation arises from the security model implemented by modern browsers, which makes such functionality challenging to achieve, though not impossible. Similarly, dragging and dropping content from web access to the Windows file system faces comparable obstacles. Browsers do not allow web applications to directly access the host system, and web applications cannot receive information about drag events occurring outside the browser window.

As browsers evolve (with updates like HTML5 and newer versions), this functionality becomes more technically feasible, albeit with certain limitations. Initially, Chrome was the only browser to support folder drag-and-drop, and this capability was only available through WebKit extensions to the base browser functionality. However, modern browsers now offer broader support for folder drag-and-drop events, making it possible for Laserfiche to potentially implement this feature, provided there is sufficient user demand.

That said, Web Access drag-and-drop is generally designed for users interacting with a few files at a time rather than entire folders. If there is a need to import a folder's worth of content, this could be considered a bulk operation, for which there are other Laserfiche tools available, such as Import Agent and Workflow.

being able to configure repository display options such as font size and font used

The ability to select font style and size is also not available in the Laserfiche Windows client, unless you are referring to the display options for an entry’s OCR text. I believe the absence of user font customization in the web client is likely an intentional design choice to ensure a consistent user experience and branding across the Laserfiche platform. While this is an interesting feature request, it may be helpful to consider the underlying technical and strategic reasons.

Laserfiche Web Access operates on a client/server model, where content rendered in the browser is served from the web server. Any fonts that users could select would need to be available on both the server and the client system. This could introduce performance challenges, as determining each user’s font preferences might affect response times, potentially leading to a diminished user experience. Additionally, some fonts have licensing restrictions that prevent their inclusion in commercial software like Laserfiche.

In contrast, the Windows client allows users to select font styles for OCR text because it utilizes the fonts already installed on the client system.

being able to drag items to emails in order to attach them (this is a big pain point for most of our new users)

Browser security policies prevent web applications from directly accessing host systems. As a result, web applications are unable to send or receive information about drag events outside the confines of the browser window. This limitation also explains why drag-and-drop functionality from the web client to the desktop is not supported. Once a drag-and-drop action extends beyond the browser window, there is no event handler in place to facilitate writing to the host file system or to interact with other applications.  This is not a unique to Laserfiche issue either as you also can’t drag and drop from SharePoint directly to Outlook as an attachment.  Laserfiche does provide several excellent alternatives for sharing content that should be considered.

• The Office Plugin allows users to attach Repository entries to emails
• The Share functionality in Web Access can create an email (.msg file) with selected entries as attachments, or as links to the entries for those with access to the selected repository content.
• Direct Share allows  content to be shared externally with non-licensed users and includes the ability to revoke and fully audit access.

being able to set custom keyboard shortcuts for different actions

For your reference, Laserfiche does provide a set of non-customizable keyboard shortcuts, which can be found here: Laserfiche Keyboard Shortcuts. The absence of custom keyboard shortcuts is likely a deliberate design choice by Laserfiche. This approach ensures a consistent user experience across the entire product suite, simplifies documentation, and maintains uniformity in training materials.

being able to set permissions for a group of folders simultaneously instead of one at a time (ex select multiple folders, view access rights, and add a trustee plus set their rights)

The reason bulk modification functionality is not as readily available in the Web Client as it is in the Windows Client is not immediately clear, but I would surmise that it is related to performance considerations. Web applications must pass through additional communication checkpoints that the Windows Client does not encounter. While implementing this feature seems technically feasible, it is likely lower on the development priority list due to the relatively infrequent use of this particular functionality. If you find yourself frequently modifying access rights in bulk, there are workflow activities available that may better suit your needs.

one of our staff this morning was talking to me and reminded me that having the ability to access files through the windows interface (ex open file explorer and have Laserfiche show up as a pseudo network drive etc) would be very desirable too. Organizations that are used to being in a Windows environment and who transition to the Web Client will likely see a lot of issues purely because of how disjointed processes can become when working between a web-based and local Windows ecosystem.

What you are referring to is commonly known as WebDAV, a deprecated and outdated protocol extension. Many applications have phased out support for WebDAV due to various issues, including problems with caching, locking, session management, data loss, and the lack of modern TLS support in client implementations. Microsoft has deprecated the WebDAV redirector service component, which no longer starts by default in newer versions of Windows Server.

Even if WebDAV is forcibly enabled on a server and configured within Laserfiche, there are several other considerations to keep in mind:

• Enabling WebDAV would reserve port 80 exclusively for the Laserfiche Server service, preventing other web applications from coexisting on the same server without additional port configuration.
• WebDAV does not support Laserfiche versioning, meaning each entry saved would result in the creation of a new Laserfiche entry.
• WebDAV is also unaware of Laserfiche metadata, so modifications to metadata would still require the use of a Laserfiche client.

In my view, the reluctance of users to adopt new processes (such as using the Laserfiche client instead of Windows Explorer) is more of a change management challenge than a software issue. As an alternative, using Import Agent to monitor specific Windows Explorer folders may offer a viable interim solution.

If you have any questions, please reach out to your Laserfiche Solutions Provider for guidance.