2023 Update Rollup 2

Fabasoft Folio 2023Permanent link for this heading

Find out more about new features and improvements of Fabasoft Folio 2023.

UsersPermanent link for this heading

As an end user, you can expect the following new features.

Redesigned Menu BarPermanent link for this heading

The status information of a list (e.g. number of entries, sorting) is no longer displayed in the title bar but in the menu bar. The status information is also no longer a control element. Instead, the “Sort” and “View” buttons are available.

Menu Bar

If the basic setting Show Menu Bar is enabled, the available menu commands are also displayed. If the window width is not sufficient for displaying the menu commands, they are hidden and can be reached via the “More” button, Depending on the context, additional buttons of important commands can be displayed if the window width allows this.

Fabasoft Folio Client Options DialogPermanent link for this heading

Only workstation-specific settings are displayed in the Fabasoft Folio Client options dialog. You can access the user-specific settings via the “More Options” button. Alternatively, you can open the settings directly in the web client (“account menu (your user name)” > “Advanced Settings” > “Fabasoft Folio Client”).

Collections for Templates and PresettingsPermanent link for this heading

To simplify the management of templates and presettings, templates, text modules, insight apps, forms, categories, processes and presettings can be managed together in a “Collection for Templates and Presettings”. Separate areas are available in the collection for this purpose.

Thus, templates and presettings of a use case can be combined and you only have to assign access rights once.

Users with the “Full Control” or “Change Access” roles are no longer implicitly offered the templates for use. In order to use the templates, the “User” role is also required.

Users with the “Read Access” role can only use templates and presettings if they are explicitly referenced, for example, in the context of an app room. Thus, templates can be centrally managed in the collection but they are not generally offered.

Multilingual Text ModulesPermanent link for this heading

Further text modules can be assigned to a text module as translations. To create a translation for a text module, the “Create Translation” action is available. If translations already exist, the "Translations" action can be used to navigate to the corresponding text modules or to create a new translation.

Translations receive, among other things, the text module category and settings for usage from the text module of the main language.

Each translation must be released before it can be used. When you release a text module with translations, a dialog will inform you about unreleased translations. You can release all translations at the same time.

General ImprovementsPermanent link for this heading

  • In lists, the “Refresh” button is displayed by default.
  • Objects in unsorted lists can be moved not only by drag-and-drop but also with the context menu commands “Move” > “Prepare for Moving” and "Move" > "Move Before" or "Move After". Thus, the move functionality can also be used via keyboard operation.
  • The column text filter also works with multi-line text properties.
  • If the “Open in New Window” context menu command is executed on a tab in the content view, the corresponding tab is displayed in the new window.
  • The width of the “Team” and “Time Travel” tools can be adjusted manually. On mobile devices, the resizing is not available due to the limited screen width.
  • When using the "Increase Contrast" accessibility setting, read-only cells are additionally marked with dashed boundary lines in the detail view when table editing is enabled.
  • Accessibility support is now available for pie, line, area, column, and bar charts included in the document view.
  • If an object is locked and you open the property editor in read-mode, you can find out if the object is still locked by clicking the “Show Locking Information” button.
  • The subject or title of workflow notification e-mails starts with “Fabasoft Folio Compliance:” and contains the name of the activity. In the context of solutions, the text may be adapted accordingly.
  • In the worklist, the fields of the “Process Statistics” tab of a process can be shown as columns.
  • For activities and activity definitions, the associated work items are displayed in the properties and in the info box. For each work item, the following additional information is displayed if it applies:
    • Multiple
    • Must Be Executed
    • Completes Activity
    • Conditionally Visible
    • With Precondition
    • Executed by (for activity instances)
    • Started or Completed (for activity instances; process administrators additionally see the time)
  • If, for example, an activity is prescribed to a group, the users who perform steps are included in the properties defined by the process (e.g., Users Participating in Workflow or Users Having Participated in Workflow).
  • When duplicating a search folder, the associated search form is also duplicated if the search form is assigned to the same Teamroom. If the search form is assigned to a template collection, it is not duplicated.
  • When Teamroom templates with a user-defined form are instantiated, the form properties are displayed directly.
  • In the settings of Teamrooms, on the “Content Settings” tab, in the Remove PDF Document Restrictions on Upload field, you can specify whether to remove the PDF document restrictions when uploading PDF documents. A possibly defined password to open the document will not be removed.
  • When you define a Teamroom as a template, the objects defined in the Teamroom's templates and presettings are copied to the Teamroom instance as shortcuts.
  • The background tasks of objects are displayed on the “Background Tasks” tab. Whether background tasks that have already been processed are displayed depends on the action. When defining background tasks you can override the default setting of the action using the Remove Processed Entries From the List of Background Tasks field.
  • In Teamrooms, thesauri for keywording can be defined under “Templates and Preferences”.
  • Notifications for “Templates and Presettings” and included collections are disabled by default.

Process and Form DesignersPermanent link for this heading

As a process or form designer, you can expect the following new features.

ProcessesPermanent link for this heading

  • If a follow-up activity (e.g. “Deny Approval”) is inserted programmatically for grouped activities, the follow-up activities are also grouped.
  • The new workflow activity “Forward for Review” (only available in BPMN processes) allows a document to be forwarded for review.
  • The keeporiginaldiagramversion process parameter can be used to specify whether the at the start of the process released versions of subprocesses are retained. This way, re-releasing subprocesses does not affect processes that are already running:
    process.SetProcessParameter("keeporiginaldiagramversion", true);
  • If an activity such as "Approve", "Release" or "Review" is denied, activities are not executed if they belong to the same multi-instance task. The default behavior can be changed by the process parameter keepactivitiesstarted: process.SetProcessParameter("keepactivitiesstarted", true);
  • The signdialogtitle, signdialogheading and signdialogdescription process parameters can be used to customize the texts of the sign dialog.
    For example: process.SetProcessParameter("signdialogtitle", "Sign");

FormsPermanent link for this heading

When you define a form, the following new options are available:


  • In the form metadata, on the “Advanced” tab, in the Available Processing States field, additional processing states can be selected to be available in the Processing State default property.
  • In the form metadata, on the “Advanced” tab, a prepare commit expression can be defined.
  • An existing, not released category can be converted into a form. Thus, no migration is necessary if the category is to be extended with user-defined fields.
  • In a template and presetting collection, forms from other collections can be inserted as a shortcut to be used in a form, for example, as a base form.

Fields of a Form

  • Fields of type “Password” can be defined.
  • The Multilingual Name property can be selected as a default property.
  • For fields, actions or app.ducx expressions for the following events can be defined on the “Advanced” tab:
    • Read Display String
    • Handle Copying of Field
    • Handle Construction of Field
    • Handle Destruction of Field
  • For fields, you can specify on the “Display” tab whether they should be displayed in a new row. Additionally, the width for fields displayed side by side can be defined.
  • Defined enumeration types (radio buttons or combo box) can be referenced in the Existing Enumeration Type field and thus reused.
  • In item lists of compound type, the COOSYSTEM@1.1:LanguageStringList default type can be selected.
  • If the form has already been released, the type of a field can be changed to compatible types (e.g. from string to hyperlink or password).
  • The generic “Object” can also be selected as allowed default object for object fields if Compute Value of Field or Filter Values is defined. Thus, any objects can be returned in calculated fields or a filter can be defined to ensure that only instances of certain object classes can be inserted.
  • The Evaluate Filter Expression as Boolean Filter option can be used in the value filter to specify whether the filter expression is evaluated as a Boolean filter. By default, the filter expression is evaluated as an object list filter.

AdministratorsPermanent link for this heading

As an administrator, you can expect the following new features.

  • In the vApp configuration, the Maximum Number of Entries in Simplified Lists field can be used to set the maximum number of entries in lists displayed in the property editor. Clicking the “Show Details” button displays the full list.
  • In the vApp configuration, the Maximum Number of Columns in Simplified Lists field can be used to set the maximum number of columns in lists displayed in the property editor.
  • In the vApp configuration, the Show Symbols in Object Lists by Default field can be used to define whether the ShowIcon control option is set to true or false, if it has not been explicitly defined for the respective object list.
  • In the vApp configuration, on the “Advanced” tab, the Hide Link to Help Page in Explanations field can be used to define whether a link to the user help is displayed in the context-sensitive help.
  • In the user environment, on the “User Interface” tab, in the Limits for Determining the Navigation Path of an Object field, the limits can be reduced to improve the performance. The navigation path is evaluated, for example, when opening a link to an object.
  • In the user environment, on the “Workflow” tab, in the Show Advanced Properties for Activities
    field, it can be defined whether additional properties are displayed for activities that are generally not user-relevant.
  • The server loader loader.exe has been replaced by the new server loader cooload.exe.
  • A separate, much smaller MSI package without Webview2 runtime is available for the Fabasoft Folio Client (FolioClient-Win11.msi). This package can be used on Windows 11 systems, since the Webview2 runtime is an integral part of the operating system. The MSI package can also be used on Windows 10 systems if it is ensured that the Webview2 runtime is installed.

DevelopersPermanent link for this heading

As a developer, you can expect the following new features.

DomainsPermanent link for this heading

An object of object class COOSYSTEM@1.1:PrimaryDomain represents the primary domain. Properties that can be configured only once per system have been moved from COOSYSTEM@1.1:CurrentDomain to the primary domain. For example, coort.GetPrimaryDomain().domaintestsystem can be used to access the property Test System of the primary domain.

The action COOSYSTEM@1.1:GetDomainAttribute allows reading properties from a CurrentDomain object with fallback to the originating domain (COOSYSTEM@1.1:domaincreatedby) (e.g. coodomain.GetDomainAttribute(#domainfinalformat)).

Following properties are now only be defined in COOSYSTEM@1.1:PrimaryDomain:

  • COOSYSTEM@1.1:domainanonymoususer
  • COOSYSTEM@1.1:domainauditdatasource
  • COOSYSTEM@1.1:domaincurrconvtable
  • COOSYSTEM@1.1:domainenabledtc
  • COOSYSTEM@1.1:domaineventqueuecache
  • COOSYSTEM@1.1:domainmasterusers
  • COOSYSTEM@1.1:domainmulticastcache
  • COOSYSTEM@1.1:domainqueryscopes
  • COOSYSTEM@1.1:domainreplacementuser
  • COOSYSTEM@1.1:domaintestsystem
  • COOSYSTEM@1.1:domainupdatetoken
  • FSCAPPDUCX@1.1001:currdomcoverageexcludedswcs
  • FSCAPPDUCX@1.1001:currdomcoverageprefix
  • FSCAPPDUCX@1.1001:currdomrecordcoverage
  • FSCCODEEDITOR@1.1001:currdomcheckapp
  • FSCDUCXUNIT@1.1001:domaintestsystemtype
  • FSCVAPP@1.1001:telemetrypublicformid
  • FSCVAPP@1.1001:telemetrywebserver

Following properties should be read with COOSYSTEM@1.1:GetDomainAttribute:

  • COOATTREDIT@1.1:domaindisabledapps
  • COOATTREDIT@1.1:domainenabledapps
  • COOATTREDIT@1.1:domainuserprofile
  • COOSYSTEM@1.1:domainarchtofinal
  • COOSYSTEM@1.1:domainarchversremains
  • COOSYSTEM@1.1:domaincisqry
  • COOSYSTEM@1.1:domaindelegation
  • COOSYSTEM@1.1:domaindisablegroupsubst
  • COOSYSTEM@1.1:domaindisplayowner
  • COOSYSTEM@1.1:domainenableasteriskqry
  • COOSYSTEM@1.1:domainenablemmcqry
  • COOSYSTEM@1.1:domainenablequotas
  • COOSYSTEM@1.1:domainfinalformat
  • COOSYSTEM@1.1:domainoptimizemmcqry
  • COOSYSTEM@1.1:domainpublicaccess
  • COOSYSTEM@1.1:domaintype
  • COOSYSTEM@1.1:domainverstofinal
  • COOWF@1.1:localdomainwfpreferences
  • FSCCRYPT@1.1001:domainkeyserver
  • FSCDIGSIG@1.1001:dsgdomconf
  • FSCFOLIOCLOUD@1.1001:domainuseservicequotas
  • FSCFOLIOCLOUD@1.1001:domainusrenvtempl
  • FSCFOLIOCLOUDPAYMENT@1.1001:domainfreegroupapps
  • FSCLDAP@1.1001:domaindatasource
  • FSCRELREP@1.1001:defaultdbressource
  • FSCTEAMROOM@1.1001:domainbackgroundusersender
  • FSCVAPP@1.1001:activatetelemetryrec
  • FSCVAPP@1.1001:telemetryformid
  • FSCVAPP@1.1001:telemetryoption

General ImprovementsPermanent link for this heading

  • The color selection in the HTML editor can be enabled with the control option "allowColorEditing: true".
  • The jQuery control FSCCALDAV@1.1001:ControlStdCalendar can be used together with other properties on a form page. The controlinitheight parameter can be used to set the height in pixels (default value: 400 px).
  • The determination to which domain a numerator belongs to is no longer based on the user's current domain, but on the domain of the respective object for which numbering is to be performed. If in certain cases the previous behavior is needed, this can be achieved by implementing an action that is stored in NUMERATOR@1.1001:domnumact.
  • Kernel: When comparing currency properties, no exception error is thrown if the currency differs.

DiscontinuationPermanent link for this heading

Following functionality is no longer available:

  • OpenSSL 1.1.1n has been replaced by OpenSSL 3.0. Legacy algorithms and ciphers are no longer supported.
    In particular, processing of PKCS#12 files that use internally unsupported ciphers is no longer possible. Content that was encrypted via FSCEXPEXT@1.1001:Encrypt using the Blowfish, DES or Triple-DES ciphers must be decrypted or deleted before the update. After the update, they can no longer be decrypted using FSCEXPEXT@1.1001:Decrypt.
  • The cross-domain license check is no longer available.
  • The kernel-based integration for Mindbreeze is no longer supported.

Following third-party products are no longer supported:

  • Autodesk AutoCAD 2021 is no longer supported.