Build 3513 - 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
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 brings minor improvements and bug fixes.
Update of location and court data (Germany)
timeSensor AG obtains the German location and court data from the Higher Regional Court of Stuttgart and makes this data available to its customers. With this update, the new JSON format is supported, so that the location and court data can now be updated again. When updating to this build, the location and court data are automatically updated to R2010.
The new data delivery now also includes the XJustice ID of the courts, which is required when using beA. However, the SAFE ID of the courts is not included, which is why this field can now be entered in the dossier. You can thus store the SAFE ID of the courts with which you communicate in the dossier in order to simplify communication with the courts via the new Communicator module.
When selecting the competent court, the selector window now shows a menu with the matters and, after the corresponding selection, the competent court. The new menu appears after selecting "Competent authorities client" or "Competent authorities opponent".
Disclaimer: the display of the competent court by the timeSensor software is based on the recorded address of the client or the opposing party and is a non-binding suggestion. The correctness of the competent court must be additionally verified by consulting the relevant sources!
Updates of the location and court data are periodically made available in the download area. They can be read in by the administrator in the Settings area, with Menu Admin under Special.
Further improvements
- In the DMS (in the tab Drafts and Archive), the filter for selecting documents is now set to the last 12 months by default in order to optimise loading times.
- Internal mandates can now also be archived. They behave like normal mandates in this respect.
- The archived messages in the communicator window can be deleted automatically after a certain period of time in order to reduce data banning. Since archived and assigned messages are already stored in the DMS (Archive tab), it is not necessary to keep messages received in the communicator for a longer period of time.
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 ...