Skip to main content

GUI Settings

A set of behaviors and parameters of the user interface are configurable in the GUI Settings page.

GUI settings

  • Welcome message: a message displayed to all the users when they sign in
  • Preview window: percentage of the screen width occupied by the preview window
  • Preview timeout: max. time to render the preview
  • Thumbnail size: dimension of the thumbnails
  • Thumbnail quality: quality of the thumbnails (100 is the best quality)
  • Tile size: dimension of the tiles
  • Tile quality: quality of the tiles (100 is the best quality)
  • Thumbnail size for mobile: dimension of the thumbnails in the mobile app
  • Thumbnail quality for mobile: quality of the thumbnails in the mobile app (100 is the best quality)
  • Avatar size: pixels for the user's avatar
  • Upload max. size: maximum allowed size for a single upload
  • Disallowed ext.: list of file extensions that will not be accepted during the upload
  • Text ext.: list of file extensions that can be edited with the embedded text editor
  • Attribute text box width: size of the text boxes used to display and edit the extended attributes
  • Attribute text area width: size of the text areas used to display and edit the extended attributes with Text Area input mode
  • Attribute text area height: height of the text areas used to display and edit the extended attributes with Text Area input mode
  • On double-click: what happens when a user double-clicks on a file
  • Document Tab: what is the open tab when the user selects a file
  • Folders sorting: folders sorting policy
  • Folder pagination: if you want the folder's tree to handle pagination
  • Folder page size:number of elements per page (if folder pagination is active)
  • Show attributes of type Document as links: if the attributes that point to a document must appear as link
  • Max. histories: number of elements in the history panel
  • Security option: display the security options when a folder is created or copied
  • Security option default: default policy for the security option when a new folder is created or copied
  • Open folders tree: if the folders tree must be opened by default
  • Open preview panel: if the preview panel must be opened by default
  • Webstart mode: 'webstart' uses the client launcher, 'download' requires the user to download the .jar file manually
  • Search hits: default number of hits returned by the search
  • Web cont. Folders: list of folder ids that will be used by the web content editor to look for images and other contents
  • Save login: if the user has the option to save his credentials in the browser
  • Session timeout: if during this amount of minutes no interactions are received, the session will be closed
  • RPC timeout: maximum time that the user interface waits for a response from the server
  • Session heartbeat: frequency with which the interface attempts to contact the server
  • Popup timeout: seconds the pop-up stays and displays a new message received
  • Charset: default charset used to save some texts in the database (normally you use UTF-8 or US-ASCII)
  • React to remote events: if the interface should process the remote events
  • Show quota alerts in login: if you want to display an alert in the login screen when a quota has been reached
  • Show license alerts in login: if you want to display an alert in the login screen when the support or license expiration is about to be reached
  • Show update alerts in login: if you want to display an alert in the login screen when a new release is available
  • Show patch alerts in login: if you want to display an alert in the login screen when an important patch has been released
  • Alert server connection error: if you want to display an alert when the interface loses the connection to the server
  • Save Input: Enable autocompletion on the attribute values
  • Show language in login: if you want to display the language selector in the login screen
  • Note max size: maximum size of the text of an annotation
  • Email max size: maximum size of the body of an email
  • Workflow dashlet rows: maximum number of rows displayed in the workflow dashlets
  • Lock on editing: if the document must be immediately locked when the user starts to edit the metadata

Grids

In this section, you can configure the columns that will be displayed by default in the different grids of the interface. Each column represents an attribute of the document, and here you can choose the set of attributes you want and their order.

For each grid, you can also specify the maximum number of element displayed per page.

Dashlets

A dashlet is a small window that appears in the user's dashboard. The purpose of a dashlet is to show useful information about the user's activities inside the system. Read more.

Languages

LogicalDOC supports a huge set of localizations, and in the Languages tab you can configure what languages you want to make available for the user interface.

Dashlets

A dashlet is a small window that appears in the user's dashboard. The purpose of a dashlet is to show useful informations about the user's activities inside the system.

Each user can customize his dashboard by placing a set of dashlets made available by the system and configured in Administration > Settings > GUI Settings > Dashlets.

By default you find a set of default dashlets you cannot change but clicking on Add dashlet you can create a new custom one. Double click on a row to edit the dashlet:

  • Title: the title of the dashlet shown to the user
  • Type: type of content
  • Max: maximum number of displayed records(valid only if you specify a query)
  • Query: query for the data retrieval(not valid for custom content dashlets)
  • Content: dynamic content written using the automation syntax(valid only for custom content dashlets)
  • Columns: the list of metadata to show in the display grid
Edit
Columns

To confirm your changes click on Save

Different types of Dashlets

You can count on different types of dashlets:

  • documents: you must use a query to retrieve a list of documents(use the automation syntax to make the query dynamic)
  • document events: you must use a query to retrieve a list of events(use the automation syntax to make the query dynamic)
  • notes: you must use a query to retrieve a list of notes(use the automation syntax to make the query dynamic)
  • custom content: you must write an automation script

Inside the query or content specification your can count on the $user variable that specifies the currently logged in user.

Check here a list of sample dashlets.

Custom Actions

A custom action represents a new menu item that appears in the context menu of the document and folder. The purpose is to give you the opportunity to create new commands that can be chosen by your users to take actions specific to your way to work. By using the automation language you program what happens when a user clicks on a specific custom action.

Click on Add custom action to create a new item.

You can directly input your automation code or you may choose an existing automation procedure. In this latter case, if the procedure declares some input parameters, the user will be required to input them when the action is selected.

Security

Each custom action can be enabled / disabled at any time and in any case you can limit it's availability by assigning users and groups like any other menu.

Proxy

LogicalDOC needs to call external URLs for various reasons, ranging from internal tasks such as checking for updates, validating licenses, to integration with remote third-party tools.

In case you install into an isolated environment, and you do not count with Internet connection, you may still make LogicalDOC able to communicate with the outside by using a local proxy.

LogicalDOC supports HTTP proxies only, and you configure it in Administration > Settings > Proxy

Here you can enable/disable the proxy and test the connection parameters.

Automation

The Automation is a pervasive aspect of the LogicalDOC platform and represents the way you have to program things using a simple scripting language.

Warning

In order to write a correct automation script you need minimum programming capabilities. Please look at the Automation Manual to familiarize with the syntax. You may also look at the Automation Snippets.

Automation Routines

In this section you define reusable automation routines. These routines may be referenced and triggered when specific events happens in the platform.

Automation Triggers

An Automation Trigger allows you to specify when a routine must be automatically executed.

Automation Triggers
 

You may define event-driven triggers that react to events happening in the system and time-driven triggers that are fired at given points in time.

For event-driven triggers you just select the events you want to catch and optionally a folder to restrict the scope.

For time-driven triggers you can define an exact time or use a cron expression to execute them regularly. Please look at the tutorial to discover the syntax of cron expressions

In any case a trigger may define the Automation script directly or may reference one of the available routines.

Security Implications

The automation script bypasses all the security policies during it's execution, so make sure which users can write automation scripts or execute automation routines.

More Articles …