Build 3393 - Maintenance

Build 3393 - Maintenance

About this build

This maintenance build contains minor programme improvements and some bug fixes.

4D Database 18.4 LTS

The 4D database, which is the basis of timeSensor LEGAL, is continuously being developed. The current build is based on the 4D database 18.4 LTS.   Please note that the timeSensor client updates itself once to database version 18.4 after the update. The client updates itself automatically if the operating system allows it.
In order for the timeSensor Client to update itself automatically to the latest version, it must be located in a directory with full read/write access rights. If necessary, contact your IT administrator.


Add employees

timeSensor LEGAL provides a data entry assistant for easy entry of employees of a company or organisation:
  1.  Select a company or organisation in the address list.
  2. Click on the blue "+" button to add an address.
  3. Answer the following question with "Yes":
Now the data entry assistant appears. From this build on, it contains additional fields to directly enter the personal contact numbers (personal e-mail, mobile phone, etc.) of the person.

Invoice list with differentiated total fields

The following improvement of the current build will please the members of your team who deal with accounting.
The following illustration shows an invoice data record in which an advance invoice in the amount of 1'190.00 was credited (the amount was first cancelled and then credited to the invoice from the account "Transitory items". In addition, a payment of 2'000.00 was booked in the invoice record. This results in a total of 3'190.00, which is listed under "Total booked".
Since timeSensor 9.0, advances are no longer credited outside of the accounting, but advance amounts are first reversed properly, i.e. posted back to the "transitory items" account and then credited from there to the invoice. Thanks to this procedure, advance invoices that were created under a different tax rate than the current one can also be correctly credited.

As of this build, timeSensor LEGAL not only has the field "Total booked" in the invoice list, but now also two additional fields "Booked from DP" and "Booked other". The accounting staff can thus see directly in the list how much of the booked amount has come from the clearing of existing credits and how much has come from payments.


Security

Since timeSensor LEGAL is increasingly used in connection with a cloud server, we have increased the password requirements as of this build. In the settings area you will find the Security tab in the Admin/Special menu. Here you can set the right balance between comfort and security. If the slider is on the far left, the password requirements are low and simple/short passwords are allowed. The further to the right the slider is moved, the higher the requirements become:
IMPORTANT: If your server is in the cloud, then you should move the slider to position 3 or 4 to ensure optimal data security.

The following table shows the password requirements depending on the position of the slider:
Position of the sliderMinimum length of the password
Required characters
Position 1 (far left)4No restriction
Position 210Min. 2 classes of characters (upper case, lower case, numbers, special characters)
Position 312Min. 3 classes of characters (upper case, lower case, numbers, special characters)
Position 4 (far right)
14
Characters of all 4 classes required (upper case letters, lower case letters, numbers, special characters)


Electronic invoice transmission via LEDES Standard

For law firms that send invoices to Anglo-Saxon countries, timeSensor LEGAL now supports the LEDES standard with a new module. This allows invoice data to be sent electronically or uploaded to the corresponding portals. Detailed information on the use of LEDES in timeSensor LEGAL can be found here.

Speed

Code optimisation has reduced the loading time for the mandate folder. Depending on the infrastructure and the number of documents in the document archive, loading times are reduced by up to a factor of 20.


Cost centres

Cost centre names can now be 35 characters long instead of 20.


Bug fixes

Bug fixes from various areas round off this maintenance update.
    • Related Articles

    • Build 3646 - Maintenance

      About this build This build finalises the improvements of the last preview build and brings further improvements. Trigger emails from tSL Background An email can be triggered at various points in timeSensor LEGAL, for example in the dossier or in the ...
    • Build 3366 - Maintenance

      This article has been machine translated. If you find any errors, we would be grateful if you could report them to translation@timesensor.com. About this build This build is especially interesting for our German customers, because it contains the new ...
    • Build 3322 - Maintenance

      This article has been machine translated. If you find any errors, we would be grateful if you could report them to translation@timesensor.com. About this build This is a maintenance build with various small improvements and bug fixes. A special ...
    • Build 3090 - Maintenance

      This article has been machine translated. If you find any errors, we would be grateful if you could report them to translation@timesensor.com. macOS Notarisation for Catalina As of this build, timeSensor LEGAL is fully notarised under macOS and thus ...
    • Build 3333 - Maintenance

      This article has been machine translated. If you find any errors, we would be grateful if you could report them to translation@timesensor.com. About this build The highlight of this maintenance build is the completion of the new Reports window, which ...