Error handling now collects more data and tries to present the correct information and solution. In addition, on permission errors, a separate diagnosis is started to find the root cause of the lacking permission.
Filenize now supports External Credentials and shows a deprecated warning when using legacy Named Credentials. External Credentials comes with extra end-user functionality:
The authentication is directly started when using the Log In button. No more going through personal settings
After authentication, the user is redirected back to the configuration/record page instead of the Salesforce home page
Named Principle access is supported for the normal authentication (was only Per User Principle before). Allowing you to use Filenize with one specific SharePoint user. Do note that user-specific functions (sharing/unsharing) will always use the SharePoint user that did the authentication, not the running user.
IMPORTANT: Changed the behavior of the Filenize User permission set. The Filenize User permission set needs to be set to all users, including admins. The Filenize admin permission set is an addition. Recommended is to also use the Filenize User permission set for your External Credential mapping
Filenize will now sync the user when using the Lightning Component. Before this was only done so in the configuration page. The method call is asynchronous and does not impact loading.
User Status now shows filters for status Synced and Not Connected
User Status now shows the user avatars instead of a fixed icon
User Status now shows the User Principle identifier instead of the Id. As the Id can differ between sites, the User Principle stays static. In addition, the User Principle is useful for detecting if the authentication was done by the same person.
Flow Diagnose now shows transactions descending
Flow Diagnose now shows the completed date instead of the last modified date
Flow Diagnose errors are now only shown if not seen before
Invocable flows now conform to a new interface called FilenizeProcessable which supports the use of process record manipulation and additional logging. All Filenize invocables implemented this interface. FilenizeActionable is deprecated
Additional logging is stored on the Process records within the Log field
The Share and Unshare invocable now populated the target user if found, if not then this is stated in the logging field. The field can be used for reporting/notification purposes, which are out of scope of the Managed Package itself
The ordering of components within the Configuration screen has changed. The three new sections are “Authentication”, “Service User Authentication” (optional), and “Configuration”
Manage Access now also shows the access applied by inheritance, before only access rules were shown when inheritance was off
Fixed an issue with showing mulltiple loading overlays
Fixed an issue with showing Metadata fields when creating/editing folders that were configured as hidden
Fixed an issue with giving your own user folder permission if that user has permission due to inheritance
Header visuals changed and now support multiple screen sizes and lightning page regions
Fixed an issue with the metadata flow action where the value field was required. Effectively causing errors on computed null values.
Fixed a visual issue on row icons being compressed with multiple metadata columns
Fixed an issue where the new reset functionality for the Create Folder actions would show an error for some permissions
Added the Flow Diagnose UI to review any Filenize flow errors in the Lightning Component. In addition, it's now possible to retry any step that took place in the flow. By default, the error indication is only visible for Filenize admins
Added a small visual indicator that shows if the user is a Filenize admin
Added invocable action to unshare a folder using a Salesforce user-id
Added invocable action to reset a folder inheritance
Added an optional checkbox on the "create folder (and pin)" invocable action to also reset the inheritance
Added Queueable Groups which allows certain automation to wait for other automation that share a common identifier. Allowing independent flow actions to run in serial mode
Added invocable action to commit all actions under a Queueable Group
Changed create folder, edit node, and upload file prompt to hide the metadata view if no metadata is configurable
Removed an additional call when loading folders for pagination, now retrieved in the initial call
Fixed an issue where removing the delete functionality from the Lightning Component was not respected with files and folders selected
Fixed an issue where the Filenize component was not refreshed properly on record updates
Fixed an issue where some authentication errors were not presented correctly
Fixed an issue where the sharing invocable actions were not correctly checking the running user sharing permission. In addition, an optional checkbox is added to the sharing actions to skip the process if the user has no permission
Fixed an issue where the parent folder would show on the root folder for some permissions
Added functionality to load more files and folders if not visible. By default 25 files and/or folders are shown
Added the functionality to share the current folder
Added the option to disable sharing on the Lightning Component
Added leading zero's to the references in the Filenize Flow action logs
Fixed an issue where some batches would exceed the DML or SOQL limitation
Notice: API method getFolderByRelativeUrl(..) no longer returns subfolders and files. Please use getNodesByRelativeUrl(..) for that functionality
Fixed an issue where some folders would still trigger the heap size error
Fixed an issue where invocable sharing actions would not save the error message properly
Fixed an issue where the client-side delete permission was not working properly in the file/folder submenu
Fixed a heap size error when a folder contains more than hundreds of subfolders
Added an additional user check confirmation based on the service user, if applicable
Fixed an issue where multiline text information was not shown properly in the columns
Fixed an issue with currency empty values
Fixes
Fixed an issue where some users were not able to access folders with Read permission
Fixed an issue where an error on pinning folders was not presented correctly
Fixed an issue where the Filenize step-by-step configuration was showing as incomplete when completed
Fixed an issue where a flow error would still execute consecutive SharePoint actions
Fixed an issue where empty optional flow parameters would cause issues in some scenarios
Fixed an issue where the component would go back to its root after ending a search
Fixed some styling issues
Changes
Added the functionality to show and order metadata in the Filenize UI
Added the functionality to search within folder and file metadata
Added the functionality to manage which metadata is editable
Added the functionality to change folder metadata upon folder creation
Added the functionality to edit folder and file metadata
Added the functionality to change file metadata after uploading
Added the functionality to create Metadata Mappings, which populate folder or file metadata based on the Salesforce record
Added the functionality to search folders and files locally or globally, local as the new default
Changed the auto-deletion of logs from 1 day to 1 month old
Added a total summary under Filenize setup User Status UI
Added user search functionality under Filenize setup User Status UI
Added additional access information under each SharePoint instance. The information shows access to the Site/Subsite and Document Library for the current user
Added a possibility to search for a site and subsite when creating a SharePoint instance
Added permission check when creating the SalesforceId column when using the diagnose tool
Added a FileUpload apex helper that generates the FileUpload chunks needed for the upload API for you. supports [Attachments, Content Versions, Content Documents]
Added the upload file invocable action. supports [Attachments, Content Versions, Content Documents]
Added an option with the sharing flow action to continue consecutive actions if no Salesforce user has been found that is linked to SharePoint
Client-side bug fixes
Manage access user interface improved for handling many groups, users and non-users
Fixed an issue that prevented the removal of a permission role
Added additional diagnose capabilities for debugging API/Flow misconfigurations
New Configuration layout
Added a User Status page that gives an overview of all licensed users and their connection status
Fixed an issue that caused Domain Groups to not show properly in the UI