Digest 6.2

Owned by Team Kolibri (Unlicensed)
Last updated: Apr 27, 2021 by A-Team

This article informs about changes that may lead to actions.

client

Mass input of table rows

The behavior to add several new table rows at a time in forms has been optimized. Double-click a table row as if to edit it. Now, instead of making a copy of this table row, the action button has been changed to create a new table row with the edited data. After creating a new table row, the dialog will stay open and users can keep adding new rows. The dialog is closed by clicking the Cancel button. This saves users a few clicks, as it is no longer necessary to select a row, edit it and make a copy for each to new row to be added.

CSV Export

From now on, the decimal separator used in the CSV files depends on the user's definition language setting.

designer

Workflow models' "Startable with" configuration has been changed

The configuration of the properties that control with which object type instances a process can be started has been changed. 

In previous version, four indirect properties have been used to control this behavior ("Main object type", "Process start with main object", "Allow other object types", "File element quantity"). We have decided to change this in order to improve handling and also to enable certain configurations that were not possible with the previous version (for instance, that the same model can be used with or without an object). 

The two new properties are:

  • "Start without an object" - if this checkbox is active, the model will be startable without an object
  • "Startable with objects of type" - allows to select the object types that the model can be started with. It is possible to select from the list of available object types (documents and folders), and/or to select "General Document"/"General Folder" which will then apply to all documents and folders (Also those that do not exist in the schema currently. For instance, this is very useful if a model is to be used by all documents, and new types are added to the schema in the future. The model will then also be startable with these new types without having to change the model itself. If the administrator has manually selected all existing document types, the model would have to be changed as well, and the new object type would have to be added).

The models deployed to the server will be automatically updated to use the new properties, so no manual migration of deployed models is necessary.

The update step follows these rules:

  1. All models are startable without an object by default ("Start without an object" is set to TRUE)
  2. If "Process start with main object" was set to TRUE then
    1. "Start without an object" will be set to FALSE and
    2. The "Main object type" will be added to the list of "Startable with objects of type"
  3. If "Process start with main object" was set to FALSE and "Allow other object types" was set to TRUE the
    1. "General Document" and "General Folder" will be added to the list of "Startable with objects of type"

Warning: The models saved on local disks in projects will not be updated automatically. They should be either updated manually, or a new project snapshot should be created after updating the server component (they will contain new properties).

Info: The client will always show the first document that is in the file of a process. The file of a process is implemented as a list, and can be manipulated from scripts if a different document is to be shown in client in different activities of a process (for instance, if we have a process that models logistics, in the early steps of the process it is important to show the invoice, then payment confirmation, while in later the delivery information).

Configuration of object types that are allowed for use with a custom action has been changed

The visual configuration of object types to which a custom action applies has been updated to follow the same design philosophy as for the workflows. The configuration has also been updated in management-studio.

management-studio

Check of index data consistency and repair function

In special circumstances the full-text index data can differ from that in the SQL database. A new full-text index operation supports a consistency check of the full-text index. If configured, the found differences are repaired.