List of critical changes in versions 3.12.х

List of change in version 3.12.2

Creating a document

When creating a document (object, process) with a required Attachment field, the file uploader text in the web part is highlighted with bold font and a red asterisk.


Document approval

The Comment field can be removed from document approval, acquaintance and signing tasks. The possibility to make a comment required became nested.


List of changes in version 3.12.1

Connecting via proxy server

Continue when headers are passed to the server:

With default settings, this box should be left unchecked; the connection will be established successfully.

Web part, Document management, Tasks, Business processes

Capabilities of creating sub-tasks have been extended.

How it was:

It was possible to create sub-tasks for user tasks, SMART-sub-tasks for SMART-tasks, project sub-tasks, but impossible to create acquaintance or approval sub-tasks.

How it is now:

"Parent task" -> "possible sub-task types":

Parent task Possible sub-task type
Regular approval Approval, Acquaintance, Tasks (all sub-tasks are regular)
Process approval Approval, Acquaintance, Tasks (all sub-tasks are regular)
Regular acquaintance Acquaintance, Task (all sub-tasks are regular)
Process acquaintance Acquiantance, Task (all sub-tasks are regular)
Regular consideration User task (the existing capability of creating decision-based tasks remains)
Process consideration User task (the existing capability of creating decision-based tasks remains)
User task User task
Process task User task

The existing capabilities of creating sub-tasks also remain.

Nesting of sub-tasks is unlimited.

All the task types, for which sub-tasks can be created, feature the Create Sub-task item in the Actions button.

When clicking it, a dialog box opens, where you can select a sub-task type and other parameters. When you create acquaintance or approval sub-tasks, the dialog box may feature the Require Digital Signature option.

The presence of the Require Digital Signature option depends on the global digital signature settings (Administration - Document Management Settings - Digital Signature Settings).

There are separate switches for the acquaintance and approval tasks. Selecting "Yes" removes the Require Digital Signature option from the dialog box for selecting a sub-task type, and the new sub-tasks are affected by the module global setting, or by the diagram element setting.

After creating at least one sub-task, the Sub-tasks tab is added to the parent task form. This tab contains a table with sub-tasks, but the sub-tasks of these sub-tasks are not displayed.

When creating acquaintance or approval sub-tasks, the created sub-tasks are included in the current sheet to avoid creating tasks of another executor.

New approval sub-tasks are automatically included in the parent sheet, the system does not suggest selecting a new or an existing sheet when creating sub-tasks. The sub-task creation form does not allow selecting the approval type.

The approval sheet form changed - the Executor column features indenting for visualizing the sub-task hierarchy.

The approval sheet result is affected only by the top level tasks. The results of their sub-tasks have no effect and only support the author's decision making.

When you try to complete a task, which has active sub-tasks, the system will point that out. If you choose to continue, active sub-tasks will remain in the system, except for approval sub-tasks. The active approval tasks will be closed by the author.

The possibility to cancel acquaintance and approval sub-tasks was added. To do so, the sub-task author or their manager must open the task page, click Actions and select Cancel Task.

Next, it is required to enter a comment and confirm canceling.

If a task is canceled, the current task executor receives a notification that the task has been canceled by the author. If there were active sub-tasks in the canceled tasks, these tasks would be displayed in the notification along with a suggestion to make a decision: keep them or cancel.


Marked as Obsolete:

  • Method EleWise.ELMA.Security.Managers.UserCertificateManager.CheckSignature  - "Obsolete. Use EleWise.ELMA.Security.Services.AuthCryptoProviderService.CheckSignature".

Document Management

Marked as Obsolete:

  • method VerifyData у EleWise.ELMA.Documents.Extensions.ICryptoProvider, "Obsolete. Use CryptoProviderBase.Verify";
  • manager EleWise.ELMA.Documents.DigitalSignature.CryptoProviderManager "Obsolete. Use EleWise.ELMA.Documents.Services.SignCryptoProviderService";
  • method EleWise.ELMA.Documents.Managers.AcquaintanceTaskManager.SignValid, instead use EleWise.ELMA.Documents.Services.SignCryptoProviderService;
  • method EleWise.ELMA.Documents.Managers.ApprovementTaskManager.SignValid, instead use EleWise.ELMA.Documents.Services.SignCryptoProviderService;
  • method EleWise.ELMA.Documents.Managers.DocumentVersionExtManager.SignValid, instead use EleWise.ELMA.Documents.Services.SignCryptoProviderService;
  • structure EleWise.ELMA.Documents.Models.DigitalSignature.Signer is obsolete, use EleWise.ELMA.Security.Models.Crypto.Signer;
  • structure EleWise.ELMA.Documents.Models.DigitalSignature.VerifyDataStruct is obsolete, use EleWise.ELMA.Security.Models.Crypto.VerifyResult;
  • method EleWise.ELMA.Documents.Docflow.Web.Extensions.ICertificateSelectionOnMultipleSigningWeb.RenderMultipleSignCheckBox is obsolete and no longer used.

Interfaces of the following encryption providers are updated:

  • In the server part of the Security assembly, an encryption provider base interface is allocated (Uid - ProviderUid, Name - DisplayName, Settings - Settings, signature verification method - Verify, hash calculation method - GetFileHash) EleWise.ELMA.Security.Extensions.ICryptoProviderBase;
  • in the web part ICryptoProviderWebBase (Uid - ProviderUid, js scripts registration method - RegisterScripts, add certificate script preparation method - PrepareAttachCertificate);
  • authentication and sign encryption providers are separated in the server part EleWise.ELMA.Security.Extensions.IAuthCryptoProvider (new) and EleWise.ELMA.Documents.Extensions.ICryptoProvider (this interface is now inherited from EleWise.ELMA.Security.Extensions.ICryptoProviderBase);
  • in the web part EleWise.ELMA.BPM.Web.Security.ExtensionPoints.IAuthCryptoProviderWeb (new) and EleWise.ELMA.Documents.Docflow.Web.Extensions.ICryptoProviderWeb (it is now inherited from ICryptoProviderWebBase);
  • Thus, when updating the implementation of a custom EP in document management:
    • in the server part, re-define method Verify of AbstractCryptoProvider, since VerifyData is outdated; the implementation is identical;
    • in the web part, define the methods/properties Provider, RegisterScripts, PrepareAttachCertificate.

List of changes in version 3.12.0

1. When importing a project plan you can merge it with the plan you are importing to;

2. Possibility to display a report as a table.

To display the result as a table, a Razor markup template can be generated (the Template –> Table Template button in the toolbar on the report layout tab). The result is displayed as a standard table with sorting, grouping, paging, column settings, and Excel export. Table settings are saved for each user individually (column display, sorting, paging). If the report is changed, all the custom table settings are reset.

* Sorting/grouping by columns of the String type is unavailable for Oracle DBMS

Limitations on data source queries when using the table mod:

  • A query must start with select
  • Do not sort the selection results in the query - it is done by means of the table (do not use order by in the query)
  • Limited alias name, depending on DBMS

              SQL Server –  128 characters

              Firebird 2.5 – 255 characters

              PostgreSQL – 63 characters

              Oracle – 30 characters, for version 12.2 and higher – 128 characters

  • Do not limit the selection result in quantity (offset of the first result and the number of results) - it is also done by means of the table. Depending on the DBMS, different keywords are used.

              Firebird –  FIRST,SKIP

              PostgreSQL – OFFSET,LIMIT

              SQL Server – OFFSET,FETCH NEXT

  • To be able to sort/group the displayed table by column for HQL data sources, you must specify its alias.

Using service columns to customize the result of the selection from SQL sources

For HQL sources, data in the table are shown using the standard display templates. To customize the data display for SQL sources, you can use service columns.

  • Column for displaying in the table - postfix _$view.
  • Column for using when exporting to Excel - postfix _$export.

To use service columns, you need to add to the source selection a column, whose name consists of the name of the customized column and a postfix. Sorting/grouping will be performed according to the data from the source column, not from the service one.

An example of a data source query (MS SQL Server)

Generating a Razor markup for the report layout

Report layout wizard in the table mod

Generated Razor markup for displaying the report in the table mod

The report display in the web part

Public methods and interfaces

  1. Class EleWise.ELMA.Projects.Models.MSProject.ResourceMergedView was deleted;
  2. Class EleWise.ELMA.Projects.Models.MSProject.TaskMergedView was deleted;
  3. Method GetEngineVersion was added to the interface EleWise.ELMA.Runtime.Db.Migrator.Framework.ITransformationProvider, which returns the DBMS server version number.