Versions Compared

Version Old Version 32 New Version Current
Changes made by

Daniël Loriaux

Daniël Loriaux

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

v3.

...

6

Install Filenize v3.6 for Production or Sandbox

Note

The version name for this release is incorrectly listed as 'Winter '21.' This will be corrected in the next release. This discrepancy does not affect the functionality of the package. The correct label should be 'Summer '24.'

  • Fixed an issue with uploading files that contained certain special characters.

  • Resolved a permissions issue that occurred when deleting old logs.

  • Added an alert to notify users about a credentials reset when changing the authentication provider.

  • Introduced a new "Data" tab in the Filenize Config. This page enables Filenize admins to clear Filenize Logs, with more features planned for future updates.

  • Reduced overhead in the initial Filenize automated action call, resulting in a slight performance improvement.

v3.5

  • Fixed an issue with the ‘Type__c' field on 'Field_Column__c' that lacked the new picklist value 'Choice.'. (the value still needs to be added manually to support Choice columns, but won’t result in an error anymore. You can review the 3.4 note below on how to add the picklist value)

  • Fixed an issue wherein the Filenize invocable actions would stop due to a 'Tunnel through proxy' error, specifically identified as error 503. Similar to standard 503 errors, these are now automatically retried after a brief delay.

  • Fixed an issue where Filenize configuration would break when an unsupported Auth Provider was selected.

  • Fixed an issue with the polling mechanism which would not stop properly on location change.

  • Added a new path format that would wrap on path level instead of spaces. In addition, the last level is now bold.

v3.4

Note

Salesforce does not update picklist fields with new Managed Package updates. If you have Filenize installed below version v3.4 and if you are utilizing Choice columns in SharePoint and encountering difficulties with the "Sync with SharePoint" button on the Metadata page, consider applying the following workaround:

  1. Navigate to Setup.

  2. Go to Object Manager.

  3. Locate and select the object "Field Column."

  4. Navigate to Fields and Relationships.

  5. Find the field "Type" and select it.

  6. Add the picklist value "Choice" within the Values section.

This issue will be resolved in the upcoming update. If you do not utilize Choice columns, this will not affect you. We apologize for any inconvenience this may have caused.

  • Fixed an issue where the "Skip if no user is found" flag was being ignored when the underlying user exists, but its Active Directory (AD) counterpart changed its internal email.

  • Fixed an issue where the “Load More” button was not shown on certain folders.

  • Fixed an issue where the Last Modified Date was not shown properly.

  • Fixed an issue where some features were not activated without the service user.

  • Added an advanced search prompt to help search on indexed columns to prevent the 5000+ items SharePoint error (https://support.microsoft.com/en-us/office/manage-large-lists-and-libraries-b8588dae-9387-48c2-9248-c24122f07c59?redirectsourcepath=%252fen-us%252farticle%252fmanage-large-lists-and-libraries-in-office-365-b4038448-ec0e-49b7-b853-679d3d8fb784).

    • To support indexed columns, we now show a key icon to indicate that the column is indexed.

  • Added the functionality to load folders using other values from the record than its Id. This for example allows you to show object-wide folders and folders per lead/opportunity/case status. Options are limitless in combination with formula fields.

  • Show a pinning icon to indicate that the current folder is pinned. It also shows the pinning value when hovering over the icon.

  • Added support for Choice type column fields.

    • Shows all possible values in the Metadata configuration.

    • Shows a picklist with all options when creating new folders/files (and the column is set as editable).

...

v3.3

  • Minor UI bug fixes.

  • Minor performance/caching fixes.

  • Added support for coloring folders through a new invocable action

    • This does not currently color the folders in Filenize; it only affects Sharepoint Online. Microsoft has not yet released the updated icons in their styling framework. We will monitor this change and apply the update to Filenize once it is available.

...

v3.2 (AppExchange Ready Patch)

  • The update permission for Filenize objects has been added to the Filenize User permission set.

  • Additional FLS checks applied and added more asserts to unittests (AppExchange ready!)

v3.1

Note

Due to certain packaging conflicts, the UPDATE permission for the Filenize Action, Filenize Action Run, and Filenize Action Group objects is currently not included in the Filenize User permission set. As a temporary workaround, please grant these permissions in an alternative permission set. The permissions are included in the new 3.2 release, which is coming soon. We apologize for any inconvenience this may cause.

  • Added the option to disable folder and file edits in the UI.

  • Added a filter to the header showing the current running action and flow diagnose to only show actions that are triggered by the same SharePoint instance.

    • Added the Provider Instance field to the Filenize Action object.

  • Automated the deletion of old log records after 30 days.

  • Fixed an issue that shows the parent folder even though the option is disabled.

  • Fixed an issue showing an error about nodes when “No folder related to this Salesforce record was found in SharePoint.“.

  • Fixed an issue not showing all metadata values during search.

  • Fixed an issue that did not show a file icon if the file type was unknown.

  • Fixed an issue where some special characters were not being filtered.

  • Fixed spelling errors.

v3.0 Digital Experience

Install Filenize for: Production or Sandbox

  •  Config Changes

    • Reordererd Reordered configuration steps in a more logical way.

    • Added the functionality to directly assign the Filenize Admin permission set to the current user if no assignments has have been made yet.

    • Added more filters in the user status screen.

    • Added the option to assign/remove licenses and permission sets directly in the user status screen.

    • Added the option to export the current user status list to CSV.

    • Added a direct link to the Authentication Settings for an External Sysem System in the user status screen.

    • Updated the new SharePoint Instance prompt to present clickable links to all sites, subsites, document libraries and improved the search tool.

    • Fixed an issue with the open and close indicator for certain sections.

    • Fixed an issue when an error in a selector would not indicate an error on the section itself.

    • Fixed an issue that was triggering the permission check to many times per SharePoint instance.

  • UI Changes

    • Added the posibility possibility to hide the Filenize browser section.

    • Added the possibility to hide the Filenize search bar.

    • Added a label to the Filenize, Filenize config and Filenize Actions component.

  • Filenize Actions

    • Added a Filenize Logger object which stores crucial information needed for diagnosing certain processes, these are automaticly automatically added to Filenize Action Runs.

    • Added the Filenize Action Group, Filenize Action, and Filenize Action Runs objects to facilitate automated actions runs..

    • A group is a collection of actions and can be dependant on other groups, allowing the group to wait to start certain automations.

    • An action is a collection of runs and stores the invocable action that is used in Salesforce Flow.

    • A run is the execution of the parent action and stores information about the executions lifetime. An action can be retried which results in a new run.

    • Committing and running Filenize Actions now checks if the user has access to Filenize.

    • Changed the way Filenize Actions are presented in the Flow Diagnose prompt. In addition these visuals are also added to the configuration screen with different views.

    • Each Filenize Action now does a proper 403 check per callout to quickly find out underlying issues with permissions.

    • Filenize also tracks the Apex Job automaticly automatically to detect if any non-catching exceptions occurred in the past.

     

  • New Named Credentials

    • Added a Auth Provider selector and guideline steps in the configuration screen to assist with the new named credential process.

    • Added the functionality to create the neccesary necessary Named Credentials and External Credentials for each role (Standard, Service, and Portal user).

    • Added named credential guideline steps to help the user to configure the named credentials for Filenize to work.

    • Added a step that shows the login link for Filenize Admins to copy and distribute to their team.

    • Added a portal user named principle option in Filenize setup for delegating Filenize actions on the portal through a known SharePoint user.

     

  • Digital Experience Support

     

  • QOL

    • Updated all versions to 59.0.

    • Fixed an issue that was displaying a null error message on some SharePoint responses.

    • The code of Filenize received an overhaul to improve performances, traceability, reusability and modularity.

    • The error component now also shows all information from the FilenizeLogger object that was constructed in the transaction.

    • Changed the way 403 (permission) errors are diagnosed and presented.

     

  • Deprecated

    • FilenizeActionable

    • FilenizeController

    • FilenizeInterface

    • FilenizeProcessable

    • FilenizeQueueableChain (now we only use FilenizeQueueable)

    • SharepointAPIConsumer

    • SharepointController

    • SharepointObject 

...

  • Added a waiting mechanism for background running actions if SharePoint returns a 503 (Service Unavailable) or 429 (To Many Requests) error code.

  • Fixed an issue with the 400 characters folder/file limit check.

  • Fixed an issue uploading files bigger than the Salesforce limitation.

v2.10

  • Added a folder check for existence before creating a subfolder, avoiding a 500 server error if a folder is not found (https://bitbucket.org/7dots_eu/bf-filenize/issues/3/creating-a-subfolder-in-a-nonexisting ).

  • Added an option to the Lightning Component to enable/disable folder creation.

  • Added an option to the Lightning Component to enable/disable folder pinning.

  • Added an option to the Lightning Component to enable/disable file uploads.

  • Added an option to the Lightning Component to enable/disable global searching.

  • Added an option to the Lightning Component to show a screen if no matching SharePoint folder is found by the Salesforce record.

  • Added the option to show/hide a button to show the root folder as a fallback.

  • Added the option to show a custom message to the end-user.

...

  • Added server and client URL validation to prevent a server relative URL greater than 400 characters (SharePoint limitation).

  • Added a new invocable action to rename files and folders.

  • Added a new invocable action to copy files.

  • Added a new invocable action to move files and folders.

  • Fixed an issue where some actions were failing if the given path was not explicit.

  • Fixed an issue that caused too many ConnectAPI calls to query the new Named Credential.

  • Some changes to improve performance.

  • Some minor bug fixes.

v2.9

  • Removed the need for a callout to get domain information for every UI to server interaction

    • Fixes the “Connect API’s hourly request limit“ that is relevant now with the support of External Credentials

    • Improves UI loading performance

  • Fixed an issue with the flow diagnose UI polling and the queueable server polling that would cause DML conflicts and the server to wait endlessly. This issue started after 2.8.

...