release notes

Release notes Windows GUI and Web GUI (2022.2.15)

Related products: Windows GUI
Release notes Windows GUI and Web GUI (2022.2.15)

Hello everyone,

In this sprint, we made it possible to add sound files to messages, and we introduced a new extended property that sets the type of prefilters to be applied after a refresh.

You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.

Breaking

Only locked prefilters are applied after a refresh

As of this version, only locked prefilters are applied by default after an automatic refresh.
This is a refresh that occurs for example after a task is finished, or after a detail subject has been edited.

Until now, all prefilters were applied after a refresh. To change this default behavior, you can set the new extended property UseOnlyLockedPrefilterForRefresh to No.

This extended property specifies that only locked prefilters are applied after an automatic refresh. The default value is Yes. When changed to No, all prefilters will be applied after an automatic refresh.

New

Windows GUI performance improved

The Windows GUI performance has been improved when running on the Indicium Basic application tier.
These performance enhancements are especially noticeable in documents with a large data set. 

Playing audio messages

If you want to add a sound to your message, you can now upload an Audio file. The file will be played upon receiving the message. The allowed extensions are .wav and .mp3. This feature was introduced earlier but contained some shortcomings.

Example of a message with an audio file

 

Hi  @Sjors Niesten ,

Can you elaborate a bit more on the "Only locked prefilters are applied after a refresh”?
Does this mean that when you set a prefilter to "on” and you refresh the data that the prefilter will be turned off?


Hey @Robbert van Tongeren,

We're talking about refreshes after tasks or changing detail record; All refreshes that are done automatically by the gui. (This is not clear in the original update, and i will change it)
In those scenario's the default value of the UseOnlyLockedPrefilterForRefresh setting is reversed. The prefilters do not change their state based on the value of the setting.

 


Thnx for the clarification!


These performance enhancements are especially noticeable in documents with a large data set. 

 

Care to elaborate more on this matter - i.e. provide some numbers to backup this awesome enhancement?


Hi Ricky,

We focussed specifically on parsing the results (coming from Indicium Basic) in the Windows GUI.

The bigger the set (in rows and in columns), the bigger the improvement. 
For instance, in a set with 16000 records and 32 columns we improved the parsing of the set from ~9000 ms to ~1000ms. 

On small sets there is also a slight performance gain, but less noticeable. It also depends on the datatypes being used. `String` columns ((n)varchar/(n)char) were more expensive previously which is where a lot of the time was spent.

I do not have more numbers right now.