AuthorRajesh ArchivesCategories |
Back to Blog
Change File Viewer For .Html On Mac10/20/2021
Below HTML Saving Options, choose a document type, a style setting for CSS, and an encoding. In the TextEdit app on your Mac, choose TextEdit > Preferences, then click Open and Save. Select Format on the menu bar and click Make Plain Text.Seclore for Microsoft Sensitivity Labels 1.0.0.0Set preferences that affect how HTML files are saved in TextEdit. Select File > New from the menu bar. Open the TextEdit application on your Mac. If you only occasionally work on HTML files, you can make the change to plain text for a single document.Don't lock files when in use. This issue was observed in Policy Server 3.10.1.0 (Seclore 3.16.1.0) to Policy Server 3.11.1.0 (Seclore 3.18.2.0).Added support in Mac with M1 processors for editing protected documents in Office applications.Added support for opening universal file formats (mp4, mp3, wma, dwg, etc.) in desktop applications from Microsoft Teams.Expected behavior: Some applications like Adobe Photoshop, Notepad, etc. Simply configure sensitivity labels with Seclore's protection policies and protect documents by selecting the configured labels.As soon as you select a sensitivity label that's mapped to Seclore's protection policies and close the document, it gets protected.This feature is available with Office 365 (with sensitivity labels) and Windows 10 only.Fixed the issue where protected files wouldn't open from SharePoint On-Premises in a certain scenario.Before the fix: To open a protected file, when users click on 'Open with Seclore' in SharePoint On-Premises and click 'Use a different account' in the Seclore authentication page, an error would show up.After the fix: This issue is now resolved.Fixed the issue where the name of the sender (Seclore Admin) wouldn't appear in the 'From' field in some system-generated emails.Before the fix: The 'From Email ID' would appear as the name of the sender in the 'From' field in some system-generated emails.Fixed the issue where some protected emails (.smail files) wouldn't open in a browser. STDU Viewer is the perfect viewer for technical.You can now use Microsoft sensitivity labels to protect Office 365 documents with Seclore.Pptx files when opened in Seclore Online. However, these files would show an error when opened in Seclore Online or in the desktop applications.Added support for opening files with universal protection (mp4, mp3, dwg, etc.) in desktop applications.Made changes to the product architecture to enable faster opening of files in desktop applications.Fixed the issue where animated GIFs wouldn't open in Seclore Online.Before the fix: HTML-wrapped animated GIF files wouldn't open in Seclore Online when dragged to a browser or opened from the Policy Server portal.Fixed the issue where graphs and charts wouldn't work in Seclore Online in certain rare scenarios.Before the fix: Graphs and charts wouldn't open or get inserted in. You may contact your customer success manager to deploy this feature.Fixed the issue where protected Office files wouldn't open in certain scenarios.Before the fix: Office files uploaded to IRM-enabled document libraries would get protected. It won't appear in the notifications pane.Fixed the issue where timestamps wouldn't appear correctly for protected files in a certain scenario.Before the fix: Files protected and HTML-wrapped manually with the Right-click > Seclore It option would show incorrect 'Created' and 'Modified' date and time.Added support for programmatically enabling Seclore IRM in SharePoint sites using applications token/scripts. Opening file on desktop', when they try to open a protected file from Teams in a desktop application.Expected behavior: It would appear as a slide-in notification at the bottom-right of the desktop. A local desktop copy would get created instead.Additionally, users would see a notification, 'Hang on.
Change File Viewer For .Html On Update Repository DetailsThis will prevent any issue that may occur if Seclore Identity Management is migrated to Active Directory.Fixed the issue where Repository details wouldn't get updated in a certain scenario.Before the fix: Users couldn't update repository details if the status of the repository is 'Not initialized'. This issue was observed in cloud setups only.After the fix:This issue is now resolved.Fixed the issue where multiple groups (domain level groups, repository level groups, and all users group) would appear in search results while assigning permissions to users.After the fix, users would see only one group in search results, that is, All Repository_name Users. The buffer file contains the enterprise's logo and a customized URL of a webpage that helps users with ways to open the protected file.To enable faster deployment of the Policy Server for new Seclore customers, we've removed the enterprise logo from the buffer file and added a generic URL of a file opening app that will help users open the protected file.Buffer files for existing Seclore customers will remain unaffected.Fixed the issue where timestamps would appear incorrectly for files in Hot Folders with HTML-wrapping enabled.Before the fix: Files protected and HTML-wrapped in hot folders would show an incorrect creation and modification date and time.Added support for Sample Apps to work with version 3 integration of Seclore Online.Fixed the issue where system-generated emails wouldn't get sent in a certain scenario.Before the fix: When the email address is changed in the 'From Email ID' field in the Policy Server configurations, some system-generated emails wouldn't get sent to users. This happened due to different time zones in the computers hosting the Policy Server and Seclore Online.Made changes to the buffer file for desktop applications.In some cases, users see the Seclore's buffer file when they open a protected file on their desktop.This issue was observed in Office 365 applications.Fixed the issue where PDF files wouldn't open correctly in Adobe Acrobat DC in certain rare scenarios.Protected PDF files opened in Adobe Acrobat DC would show the Seclore buffer file instead of the original content when 'Enable Protected mode at startup' is checked.Adobe Acrobat DC would shut down unexpectedly when unprotected files are opened with 'Enable Protected mode at startup' checked.These issues were observed in Adobe Acrobat DC 2021.001.20145.After the fix: These issues are now resolved.Fixed the issue where unprotected Excel and Word files wouldn't open correctly in certain rare scenarios.When a protected Excel or Word file is open, and an unprotected attachment is opened from the 'File > Home > Shared with me' section in protected view, the unprotected file would open with the Seclore buffer file instead of showing the original content. This issue was observed in Safari 14.1.x only.Installation Guide and Migration guide now contain steps to customize your logo in the Policy Server portal.Apache Tomcat upgraded to version 9.0.43.Fixed the issue where PDFs generated from protected Office files wouldn't open correctly.Before the fix: When an Office file (Word, Excel, PowerPoint) is converted to PDF using File > Export > Create Adobe PDF or Create PDF/XPS Document, the converted file would show the Seclore buffer file.In case of File > Export > Create Adobe PDF, the converted file would get exported and can be opened manually.In case of File > Export > Create PDF/XPS Document, the converted file opens as a protected file and shows the original content.Fixed the issue where Office applications would shut down unexpectedly in certain rare scenarios.Before the fix: Office applications would shut down when unprotected files are opened from the 'File > Home > Shared with me' section. Users would be able to update details for non-initialized repositories as well.Fixed a minor issue in the UI for assigning and changing permissions.
0 Comments
Read More
Leave a Reply. |