...
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 had permission due to inheritance
Fixed an issue with finding users that are in AD but not added yet to the configurated site
v2.7.1.0
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
...