Lasernet Release Version 10.1.4 Hotfix
Release date: 26th January 2022
Notes
Click here to download the installer for this latest version.
Click here to view or download the Release Notes PDF.
Maintenance Report
This section is an overview of the fixes and features included with this version.
Internal Ref. | External Ref. | Area | Details | Status |
---|---|---|---|---|
281276 |
Deskpro 23761 |
HTTP |
HTTP input module crashed when a job was read that could be null after introduction of JobInfo 'HTTPCookies' in Maintain Session feature |
Fixed |
281524 |
Deskpro 23720 |
JSON to XML |
JSON to XML modifier arrays were not working properly in all cases |
Fixed |
281563 |
Deskpro 23732, 23934 |
Lasernet Config |
Migrating LocalDB config to SQL database failed with an SA Exception |
Fixed |
282624 |
Deskpro 23890 |
Lasernet Developer |
The scrollbar was missing in some situations because the column was not resized to match content |
Fixed |
281295 |
- |
Lasernet Form Editor |
JobInfo "DataFormat" was logged twice when a form was set to XML Input and TIFF output |
Fixed |
280615 |
- |
Lasernet Form Editor |
Pad option for Rearranges could, in rare scenarios, add the wrong characters to the end of the output string |
Fixed |
274948 |
- |
Outlook Mail |
Outlook Mail incorrectly reported -1 unread mails. We implemented special handling for the incorrect value from Microsoft Graph API when reading number of unread mails from inbox |
Fixed |
283206 |
Deskpro 22988, 23855 |
PDF Engine |
Barcode label was clipped in PDF Engine/Modifier in custom Paper Format |
Fixed |
278051 |
Deskpro 23452 |
Printers and profiles |
Added support for setting PrintDocName and PrintAttachmentDocName in print queue for attachments |
Feature enhanced |
274949 |
- |
Scheduler Input |
Criteria column was incorrectly shown on Scheduler Input module |
Fixed |
277538 |
Deskpro 22939 |
SharePoint |
SharePoint 365 graph connection crashed when displayName was missing (using name instead in such case) |
Fixed |
280199 |
Deskpro 23010 |
Lasernet Client |
There was an error editing fields extracted via OCR Engine that were not JobInfos |
Fixed |
Add a comment
Please log in or register to submit a comment.