--- title: "Lasernet Core 11.2 New Features" slug: "lasernet-core-11-2-new-features" description: "A description of the new features in Lasernet Core 11.2." tags: ["Lasernet Core", "New features and fixes"] updated: 2026-08-28T07:24:50Z published: 2026-08-28T07:24:50Z canonical: "kb.lasernetgroup.com/lasernet-core-11-2-new-features" --- > ## 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. # Lasernet Core 11.2 New Features **Release version:** **11.2** **Release date:** 28th August 2026 ## Introduction This page describes the new features in Lasernet Core 11.2. > [!NOTE] > Note > > [Release notes for this Lasernet Core release are available](/v1/docs/lasernet-core-11-2-release-notes). > [!WARNING] > Compatibility Warning > > The Lasernet Connectors for Microsoft Dynamics 365 are currently not compatible with Lasernet Core 11.2 and earlier releases of Lasernet Core 11. We are working towards launching these two products together, but until then, current customers and partners with the Dynamics 365 connectors should continue to use Lasernet Core 10. > [!NOTE] > Note > > Lasernet Core 11 delivers significant advancements in several key areas. > > > > Because of the underlying architectural changes in Lasernet Core 11, if you are considering upgrading from Lasernet Core 10, we recommend that you: > > - Thoroughly review the [release notes for this and previous Lasernet Core 11 releases](/v1/docs/lasernet-core-11-release-notes). > - Thoroughly review [Lasernet Core 11 documentation](/v1/docs/lasernet-core-guides). > - Fully test your configuration. > - Reach out to your technical team for support. > > > > This note does not apply to the Lasernet Connectors for Microsoft Dynamics 365, which must continue to use Lasernet Core 10. ## New Features Lasernet Core 11.2 includes the following significant changes and new features. ### Delegated User Authentication Removed From Some Modules From Lasernet Core 11.2, the following modules no longer support delegated user authentication (also known as user authentication): - Outlook Mail Input - Outlook Mail Output - SharePoint Output - OneDrive Input - OneDrive Output User authentication has been removed from the Outlook Mail Input, Outlook Mail Output, and SharePoint Output modules. However, these modules already supported application authentication, either from Lasernet Core 10 (SharePoint Output) or from Lasernet Core 11.0 (Outlook Mail Input and Outlook Mail Output). Application authentication becomes the sole authentication method for these modules. User authentication has been removed from the OneDrive Input and OneDrive Output modules. Application authentication has been added. > [!WARNING] > Important Upgrade Information > > If your Lasernet Core 10, Lasernet Core 11.0, or Lasernet Core 11.1 configuration includes one or more of these modules using user authentication, you must update them to use application authentication instead. > > > > The OneDrive and Outlook modules require additional configuration because they must identify the user whose OneDrive or mailbox they connect to. In earlier versions of Lasernet Core, they connected to the OneDrive or mailbox of the user that the module authenticated as. In Lasernet Core 11.2 and later, the module authenticates as an application; as a result, you must use the module’s **User Principal Name** property (OneDrive modules) or **Mailbox** property (Outlook modules) to identify the user. > > > > For module configuration instructions, refer to the following pages: > > - [Outlook Mail Input](/v1/docs/outlook-mail) > - [Outlook Mail Output](/v1/docs/outlook-mail-output) > - [SharePoint Output Module](/v1/docs/sharepoint-output-module) > - [OneDrive Input](/v1/docs/onedrive) > - [OneDrive Output](/v1/docs/onedrive-output) > > See also [Understand the Security Implications of Application Authentication for Outlook Mail, OneDrive, and SharePoint Modules](/v1/docs/security-implications-application-authentication-outlook-onedrive-sharepoint). This change is one of multiple functional changes to consider if migrating from Lasernet Core 10 to Lasernet Core 11. For information about other Lasernet Core 11 changes that explicitly affect Lasernet Core 10 configurations and workflows, see [Lasernet Core 11 Changes That Affect Existing Lasernet Core 10 Configurations and Workflows](/v1/docs/lasernet-11-changes-that-affect-existing-lasernet-configurations-and-workflows). ### Master Sheet Support for PDF/UA The master sheet feature is now compatible with PDF/UA sheets. A PDF/UA sheet can be a master sheet for any other EMF-based sheet. The form design in the PDF/UA sheet is provided to the receiving sheet. The master sheet for a PDF/UA sheet can be any other PDF/UA sheet. The crucial **Group order** and **Reading order** properties of rearranges, text labels, images, charts, barcodes, and subforms in the master sheet are included in the form items that it provides to the receiving sheet. > [!NOTE] > Note > > For more information about the Lasernet Core PDF/UA capability, about **Group order** and **Reading order**, and to learn how the **Group order** and **Reading order** of each form item affects the structure tree within a PDF/UA document, see [Configure PDF/UA Output](/v1/docs/configure-pdfua-output). > > > > For more information about the master sheet feature of Lasernet Form Editor, see the [Master Sheet](/v1/docs/sheet-options#master-sheet) section of the *Sheet Options* page of the Form Editor Guide. This section also includes specific information about [PDF/UA considerations for master sheet processing](/v1/docs/sheet-options#pdfua-considerations-for-master-sheet-processing). > > > > To learn how to convert forms that currently have an EMF master sheet and a PDF sheet to use PDF/UA instead, see [Convert EMF Print Master Sheet Setups to PDF/UA](/v1/docs/convert-print-master-sheets-setups-to-pdf-ua).