List of critical changes in version 3.12.50

Functional changes

Changes in user interface

  1. Pdf.js component to preview pdf files were updated to version v2.2.228. New features are now available when working with pdf files: work with a text layer, table of contents, viewing attachments, full-screen mode.
  2. The field marked as "Read Only" is not editable, including when creating a block entry. The field can only be changed in quick edit mode.
  3. Implemented display of initials of users with double, triple, etc. names. If the surname, name or patronymic is compound and is written with a hyphen, then the initials will also be compound.
  4. Implemented 2 new settings for the "HTML" context variables in the ELMA Designer: "Display the Source Code button and  Display the ELMA button. If the settings are disabled, the "Source Code" and "ELMA" buttons will not be displayed.

New functionality 

  1. Added a new filter property for the process execution queue "Display process instances awaiting execution by timer". If the option is enabled, then process instances awaiting execution by timer will be displayed in lists.

Technical optimization

  1. Implemented encryption of configuration file sections.

    The encryption provider and sections are determined by the settings in Settings.config:

    # ProtectSettingsSection - enable/disable encryption

    # ProtectSettingsSection\{Section Name} - specify the section for encryption

    # ProtectSectionProvider - specify the name of the encryption provider

    In addition, you can use the encryption provider described in the configuration file. 

    To use encryption in a farm environment, you should import the private key container to all the farm machines.

  2. Changes in message archiving mechanism.

    Before. Old messages used to be archived once a week and for all users. Due to the number messages that had to be archived, this procedure took a very long time.

    Now. Messages are archived continuously and for one user at a time.

  3. Changed the way of loading document folder trees. Now the trees are calculated using the relationship table. The relationship table is generated automatically when saving workflow objects in the system. When updating the system, a folder relationship table is created and filled out. This may take some time, depending on the number of workflow objects.