Content Library Widget Guide

overview the content library widget in cloudfiles is designed to manage documents within a centralized content library page it is ideal for organizing shared documents in one central location, making it easy to access, categorize, and maintain files for teams across an organization the base widget appears as follows this guide walks you through the configuration options available for customizing the widget’s behavior creating widget configuration you can configure the widget as per your requirements by going to the cloudfiles app → document management → widget configuration → create new → content library widget once you select this widget type, you'll be guided through further settings to customize the widget the setup steps are as follows note since there is only one content library, you can create only one configuration of this type, which will be auto assigned key configuration fields 1\ widget config name this field is used to assign a name to the configuration for easy identification this name appears only in the “widget configuration” tab, and not on the content library page this field can be left blank and the default value will be “content library widget” 2\ widget config description this field is used to assign a short description to the configuration this description will also appear only in the “widget configuration” tab this field can be left blank and the default value is “widget used to manage documents on the content library page” 3\ configurations the control actions available in the widget can be toggled on or off here the 3 basic actions provided are create folder enables the “new folder” button to create a folder directly from the widget reduces context switching to go to the external storage for detailed instructions, refer to create folder https //help cloudfiles io/salesforce/internal record widget#6stwf folder upload enables users to upload entire folders directly to the external storage file upload enables users to upload individual files directly to the external storage for detailed instructions, refer to file and folder upload https //help cloudfiles io/salesforce/internal record widget#vr3 3 4\ widget columns this configuration controls what column names will appear on the content library page the available headers vary by external storage type — google drive, sharepoint, onedrive, etc only the headers moved to the right side of the configuration screen will appear in the widget if left blank, the widget defaults to displaying name, created by, and created on headers the selected headers will appear on the content library page as follows 5\ file click behaviour the action that will occur after the user clicks on a particular file can be defined using this setting preview in salesforce – opens a preview pop up window within the same page to view the file this is also the default option open within library in a new tab – redirects to a new tab and opens the file from within your shared drive none – disables file click actions, requiring users to manually download files to view them 6\ widget base path this is an advanced setting that lets users set a default document location to ensure organized content and restricted access by setting a base path, you can maintain the folder structure while only displaying relevant files situated at different levels in the folder hierarchy this helps present a cleaner view and restricts access to unauthorized content we recommend reaching out to the cloudfiles support team to get this configuration defined accurately for your use case 7\ resource actions this setting defines the list of actions that can be performed on a specific file or folder within the widget when a user clicks the dropdown next to a file or folder name, a list of default actions —such as view metadata, move, share, delete, etc — is displayed in addition to these, admins can define custom actions using salesforce flows these custom actions can be added to the same dropdown list and offer extended functionality based on business needs flows can either be autolaunched (running in the background without user input) or screen flows (which involve user interaction) for example, a custom action could allow users to attach a selected document directly to an email, triggered right from the widget the default and custom actions appear on clicking the dropdown beside the file name 8\ list actions list actions work like resource actions but apply to multiple selected files or folders only “move” option is provided as default, but other custom actions like “bulk delete” can be set up using user created flows