Build 3631 - Preview
About this build
This build brings numerous improvements and some bug fixes.
Invoicing
Merge PDF documents
Invoices often consist of several documents: a cover sheet, a detailed view and possibly a form with a QR payment slip. While this is usually desired for printing (e.g. because the documents are to be pulled from different trays in the printer), this is more of a disadvantage when sending invoices by email. From this version onwards, you can therefore specify in the output options of your templates whether the resulting PDF documents should be merged into a single PDF document or not. If you want the PDF documents to be automatically consolidated into a single PDF invoice, select the option Automatic in the new menu PDF Merge in your (partial) templates:
Cosmetics in the invoice templates
In invoice templates, the expression INV_INSERT("transaction",...) is usually used to display the payments posted for an invoice. Until now, the expression worked in such a way that if payments existed, they were listed. However, if no payment was present, a line "Posted 0.00" was displayed. With the new option "autohide" this can be suppressed: if there are payments, they will still be listed, but if there are no payments, nothing will be returned. The new option is the second parameter of the command, thus: INV_INSERT("transactions"; "autohide").
Accounting
New output options for ABACUS Accounting
For the ABACUS software, which is widely used by financial service providers in Switzerland, timeSensor LEGAL has had the ABACONNECT 2012 interface for several years. tSL provides the accounting records in accordance with the ABACUS interface description as an XML file for further processing. Unfortunately, ABACUS accounting systems can be configured very differently with regard to the setup of chart of accounts and cost centres, which in turn affects what data the ABACONNECT interface accepts. For example, the ABACUS programme may report logical errors during import, even if the formal transfer of data is in the correct format. Since timeSensor LEGAL allows very free posting, the transferred postings occasionally collide with the logical rules defined within the ABACUS software for accounts and cost centres.
With this version, booking records can be prepared before transfer to ABACUS by suppressing or enriching certain information contained in timeSensor LEGAL:
- With the option Cost centres - Suppress on balance sheet accounts, any cost centres existing in tSL are suppressed for the booking of balance sheet accounts.
- The option Cost centres - default for profit and loss accounts ensures that a (default) cost centre is transferred when posting profit and loss accounts, even if no cost centre was posted in timeSensor LEGAL.
The following applies to the ABACONNECT interface: in individual cases, cooperation is required between all parties involved (financial service provider, law firm, ABACUS Support, timeSensor Support) so that the interface can be successfully configured. The challenge here is not the format of the interface data, but the preparation of the timeSensor LEGAL data according to the logical requirements of the setup of the relevant ABACUS accounting.DMS
Improved import dialogue
If you drag and drop a document from the desktop into the timeSensor LEGAL archive, an import dialogue appears. This now also shows the document name so that it can be changed in the same step if necessary.
Move documents
It is now possible to move one or more selected documents directly to another mandate. To do this, use the action menu in the archive (mandate folder or dossier) or right-click on the selected document(s). Select the command Move selection in the menu. In the dialogue that now appears, you can easily select the desired target mandate and carry out the move with a few clicks. If the target client has the same archive structure as the source client, the documents will be placed in the same position.
Copying documents
It is now possible to copy one or more documents directly into one or more other mandates. To do this, use the action menu in the archive (mandate folder or dossier) or right-click on the selected document(s). In the menu, select the command Copy selection -> to other mandates. In the dialogue that now appears, you can easily select the desired target mandate(s) and carry out the copying process with a few clicks. If the target mandate has the same archive structure as the source mandate, the documents are also filed in the same place.
Automatically close Word and Excel documents before check-in
If you have checked out a Word or Excel document from timeSensor LEGAL and changed it, it is important to save the document first and only then check the document back into timeSensor LEGAL. The reason for this is that timeSensor LEGAL retrieves the document from the hard disk and the changes made are only contained in this file if you have saved the document beforehand. Most users quickly get used to this mechanism, but newcomers sometimes find it difficult to adhere to this order.
As of this version, you can set timeSensor LEGAL to automatically save and close the Word or Excel document in question before checking it in. To do this, timeSensor LEGAL must give instructions to your instance of Microsoft Office, which may or may not be allowed depending on your infrastructure. For this reason, two settings can be made: a) a system-wide setting, which applies by default to all workstations, and a setting per user, which takes precedence over the system-wide setting.
We recommend the following procedure:
- Switch off automatic closing system-wide
- Switch on automatic closing for a test user
- Check whether the automatic closing works
- If successful, switch on automatic closing system-wide
- If there are individual users in whose environment the automatic closure does not work, then switch off the automatic closure there again.
You can make the system-wide setting, provided you have administrator rights, in the Settings -> Menu Admin -> Special -> System area:
If you have administrator rights, you can make the setting for the user in the Settings -> Parameters -> System area. Here the menu is set by default to System Standard: On or System Standard: Off. This means that the automatic closing for the user in question is based on the system standard. To override the system standard for the user concerned, the menu can be changed to This workstation: Off or This workstation: On.
Communicator module
Set responsibility for new messages
If a mailbox in the communicator is used for a division of labour, it can be practical to directly assign the person primarily responsible for incoming emails. You can set this primary responsible person by selecting the menu Tools -> Manage accounts in the communicator window. You will find the new setting in this dialogue:
Check for email duplicates
In the last maintenance build, the innovation was introduced that timeSensor LEGAL automatically avoids multiple imports of the same email. In this build, the functionality is refined in that the system now shows a query and lets you decide whether you want the email to be another mail in your DMS:
Use of the communicator in the context of different entities
As of this build, the administrator can decide whether the mailboxes in the communicator are displayed across entities or not. By default, only those mailboxes are displayed that are located in the entity in question. The new setting can be found under Settings -> Menu Admin -> Special -> Entities -> Range:
Bug fixes
Various small improvements and bug fixes 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 3609 - Maintenance
About this build This build brings minor improvements and bug fixes. Update of the 4D database from version 18.5 LTS to 19.3 LTS The 4D database, which is the basis of timeSensor LEGAL, is under continuous development. This build now uses version ...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 3351 - 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 In November, Apple released the new operating system macOS 11 (Big Sur). This build of ...