Release 61, January 2022

general.png

Reports

To make it easier for you to view data in reports, we have changed the display of fields from multiblocks and multilines — now the values of such fields are displayed in one cell separated by semicolons.


When setting up a report in the Columns block, in the Format column, you can select the Combine values with separator ";" value if a field from a multiline and/or multiblock is specified as a report column. Read more: Creating a report.

  • If the number of values of one field from a multiline or multiblock displayed in a report cell exceeds 50, the Show more button will appear;
  • If the fields of a multiline and / or multiblock are not filled in, the report will contain empty values.

WYSIWYG in fields

To immediately follow links inserted into fields and select fragments of text, for example, in italic font style, you can use HTML markup — just pick out the text in fields and select the desired function on the pop-up text formatting panel:

Undo / redo the last action;

  • Bold typeface;
  • Italic typeface;
  • Underline font style;
  • Strikethrough typeface;
  • Bulleted list;
  • Numbered list;
  • Hyperlink;
  • Paragraph format;
  • Cleaning the markup.

2022-01-24_15-12-37.png


You can use HTML-markup in the following fields:

  • In fields of type Text Area in object cards, in add. attributes in client requests;
  • In the system fields Description;
  • In the Note field for client requests;
  • In the Description field for events and tasks;
  • In the Note field for notes.

The formatted text is rendered without HTML-markup elements (i.e. as Plain text):
  • When exporting to PDF, Excel, CSV (for example, when downloading a case card);
  • When generating a DOCX document based on a template;
  • When viewing report data;
  • When uploading reports.

Bugs and Fixes

  • The search is not performed by deleted values of dictionary in cases, objects or other entities of the Case.one, and as a result of such a search, an empty value will be displayed now.
  • We have eliminated the possibility of filling in the fields in tasks of archived cases — now, at archived cases, all fields of task form are inaccessible for filling.

admins.png

WYSIWYG in fields

The following restrictions apply when using HTML-markup:

  • Tabulation not supported:
    • If indentation was tabulated, it will be cleared;
    • If you paste text from Word — tabs will be automatically replaced with spaces.
  • Synchronizing with Casebook does not overwrite the formatted value in the field, so the automation workflows do not respond to changes in the field.
  • When editing formatting and/or adding a hyperlink, automation workflows for editing a specific field will not work, since the text itself has not changed.

Bugs and Fixes

  • We have corrected the behavior of the automation workflow with multiple operators If when the field value is automatically changed using a formula.
  • Now, in the Log section, in the entity editing events, all changed fields of the event and tasks are displayed.

devs.png

Public API

In API v2, we added the following additional attributes to the GET /api/v2/participants method to filter the list of participants:
  • Name;
  • Type (Person or Company);
  • Email;
  • Telephone;
  • Surname;
  • Name;
  • TIN;
  • Checkpoint.

In API v3, we added a group of methods for managing participants, where work with the created fields is now performed through the Tag — Value bundle (as in methods for working with objects):
  • DELETE /api/v3/participants/{id} — method to delete a participant by ID;
  • PUT /api/v3/participants/ExcludeParticipantFromProject — method to exclude a participant from the list of participants in the case;
  • PUT /api/v3/participants/{id} — method to update data on a participant and his additional. attributes.
  • POST /api/v3/participants — method to create a participant with completed add. attributes;
  • GET /api/v3/participants/{id} — method to get a participant with add. attributes by identifier.

In API v3, we added a group of event management methods, where work with the created fields is now performed through the Tag — Value bundle (as in the methods for working with objects):
  • POST /api/v3/events — method for creating an event with filled additional. attributes;
  • GET/api/v3/events/{id} — method for receiving events with additional. attributes by identifier.
  • PUT/api/v3/events/{id} — method for updating data on an event and its additional. attributes.

Bugs and Fixes

  • We have improved the performance of indexes on database tables — now indexes filtered by IsDeleted work correctly, keeping DynamicFilters working, if a value for filtering is passed as a parameter (IsDeleted = @pram).
  • Now you can use indexed fields in workflows of recalculate rights by user.
  • We removed unused and obsolete indexes on database tables.
  • We continue to work on porting to Angular:
    • We moved the event form using new services for working with the created blocks and additional. attributes (similar to the transfer of the task form).
    • Completely transferred: user and client profiles, work with users and clients in the Administration section, account card with all blocks, tabs, forms.
  • We have configured caching for files in the internal API GET api/download methods.
  • We fixed work of RabbitMQ with Active Directory integration enabled.
  • Now Person or Companies participants are created without errors when integration with Elasticsearch is enabled on instances that work with PostgreSQL.