Build 3625 - Maintenance

Build 3625 - Maintenance

About this build

This build brings numerous improvements and some bug fixes.

OAuth2 support for Microsoft 365

Microsoft has discontinued the possibility of logging on to the system with Basic Authentication (i.e. username + password) as of 30.9.2022. In order to use Microsoft services, such as receiving and sending emails, it is mandatory to log in with OAuth2. This procedure increases security, but is also more complex to set up. In particular, it is necessary to make the correct settings in the Microsoft (Azure) backend. A separate FAQ article provides information about this configuration work, which must be carried out by your IT supporter.
If the Microsoft backend is not configured correctly, timeSensor LEGAL cannot receive or send emails from the Microsoft server. In this case, please contact your IT supporter, as timeSensor support does not have access to your Microsoft backend.

Improvements in the mandate folder

Copy contact details

When working with the mandate folders in timeSensor LEGAL, you may wish to be able to copy the contact information on the right-hand side, for example, in order to process it in another software or to have your telephone system dial a telephone number. As of this version, you can do this by right-clicking:


Alternatively, you can click once on the contact information and wait until the field is in input mode. Now you can copy the desired information here with [Cmd] + [C] (macOS) or [Ctrl] + [C] (Windows). However, you cannot make any entries in the field; the new behaviour only serves to extract the information for transfer to other software.


Copy attachments

If documents with attachments are archived in the DMS module (e.g. emails), there is sometimes the wish to copy such attachments separately into another area of the archive. Until now, the document had to be moved to the desktop and then freshly imported. Now it is possible to copy an attachment directly into an archive by dragging and dropping:



Display assignments

If many contacts are listed in a mandate folder, it is easy to lose track of them. This is especially the case if there are dependencies. If, for example, you assign three opposing parties in a mandate, each of whom has taken a lawyer, it is difficult to see which opposing lawyer belongs to which opposing party. The following two screen shots, one of the mandate settings and one of the resulting mandate folder, show the problem:



As of this build, you can now make such affiliations visible when creating a mandate by right-clicking on indentations in the mandate settings. In this way, you can visually see that James Burger belongs to the opposing party Amram Frei:




This technique now makes it clear in the mandate folder who belongs to whom:



Improvements in the Communicator module

The communicator module enables automated email archiving. With this build, the module has become even better:

Reply and thread recognition

The communicator now remembers the header information contained in the email, such as the message ID, in order to recognise replies or entire threads. By checking for new incoming messages whether such a message ID is already assigned to a mandate, the communicator can assign related messages directly to the same mandate, which increases the hit rate.

Avoiding duplicates in the archive

The message ID is also used to check whether a corresponding document has already been archived in the archive (DMS module). If this is the case, the communicator displays the message directly with a green bar so that the message is not archived a second time. This avoids duplicates if, for example, the same message is sent to different employees of the office (e.g. copies).



Learning new email addresses

If you assign an address or a mandate to a "red" message, the communicator suggests that you transfer the corresponding email address directly into the dossier.

Improved control of the message flow

The communicator has the task of recognising incoming emails, assigning them, converting them to PDF and saving them in the relevant file. Remember: the communicator always receives copies of messages in the archive mailbox: the original message remains in your usual work mailbox. For this reason, you should ensure that the messages are also deleted from the communicator quickly after processing. Because once the message (as a PDF file) has arrived in the document archive (DMS module) of timeSensor LEGAL, there is no reason to keep the message in the communicator any longer.

To avoid having to do this yourself, you can set rules in the communicator for how the message flow should proceed. A message is first moved from the inbox (incoming messages) or from Sent to the archive. After a certain waiting time, the message is then automatically moved to the trash. After a further waiting period, the message is automatically deleted.

Assigned (green) e-mails are allowed to pass through the communicator more quickly, because there is usually nothing more to do with them. Unassigned (red) emails should move through the communicator more slowly to allow enough time for the message to be assigned. To configure the message flow, select Manage Accounts from the Tools menu. In the Message Flow section, click the Settings... button to configure the message flow. to configure the message flow.




In the Message Flow window for your account, set the desired speed at which messages move through the communicator's boxes until they are automatically removed. Click the Default Settings button to apply the recommended settings.




If you do not want a message to be moved automatically by the communicator, give it the status 'In Progress' (right-click on the message and select 'Mark as In Progress'):


Bug Fixes

Verschiedene kleine Verbesserungen und Fehlerbehebungen runden dieses Wartungsupdate ab.


    • 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 ...