Release 21 (21.0.21053.11023) – New Name , New Direction

Formate v21 is released 01.03.2021

This is an important event as it marks the first major release of Formate eVo under our stewardship. We are proud to announce that we have taken total ownership of the Formate eVo  Intellectual Property rights and control of the direction and development of eVo, from Trilogic Ltd. You will note that although we trade as Document Genetics, the software is provided and more importantly signed as Extra Resource Ltd, our parent legal entity.

This means that version 21` of eVo contains some significant changes, but primarily in two areas.

Install Location

A new install of v21 will now be located in the Program Files\Extra Resource Limited and ProgramData\Extra Resource Limited folders.  This has no real implications for a fresh install, but during an upgrade to v21, the contents of the current Program Files\Trilogic Ltd and ProgramData\Trilogic Ltd will be moved. As with any major upgrade, we strongly advise that all due care is taken with an upgrade and that you ensure that you have suitable viable backups in place before commencing.

A utility has also been provided (“C:\ProgramData\Extra Resource Limited\T3\Utilities\DeleteOldEvoFoldersandKeys.exe”) to clean up the old Trilogic Ltd installation folders located in Program Files and ProgramData and the registry after a successful installation.

Legacy PDF Functions are removed.

Legacy pdf libraries are now removed, pdf creation in print runs and scripting commands which are dependent upon legacy pdf libraries will cease to work. New commands have been available since v8.6 (May 2018), and should have been the preferred option since, but please be aware.

In addition, Formate eVo v21 introduces some new features and a significant number of default setup changes introduced after feedback from users worldwide. Details are in the attached release notes, and further information is available in v21’s help.

Ongoing Support.

At the point of a new release, support for any version of eVo older than 3 years, which is NOT the current major release will be retired. This means that as of the release of v21, support for versions prior to v8.4 will be retired, and these versions will be unavailable for autonomous download. Should help be required, then the end user will need to update to a currently supported version.

We are also announcing the retirement of any version of Formate eVo, prior to v8.4, and the introduction of a rolling 3 year retirement plan.

Server Name: Limited to NETBIOS character limit

Server name as entered into the Server Properties should be 15 or fewer characters in length. Otherwise communication with the server may not be possible and errors will be encountered licensing Dashboard

Complex Data types from a SQL database

Some times you will wish to use a complex data type from a SQL data base. if you do, use a convert() or cast statement in your SQL query to convert the type (such as an identifier or GUID) to a string.

sqlQuery = Select CAST(OrderId as char(36)) FROM Orders WHERE (OrderStatusId = ‘0c6d9b32-f1f0-5cf5-9364-09d94b7b62f4’)

Release 9.7.20314.11438

eVo 9.7.20314.11438 is a maintenance release, and should only be installed if the published fix is required.

Implements fix for error in ScanbarCode() module

Do not work on configuration file outside of Dashboard

[su_note note_color=”#ec2310″ text_color=”#f8f4f4″]Working on {evo} configuration files outside of Dashboard can cause serious problems.[/su_note]

Facilities are provided within the Dashboard application to work with various configuration items such as Form Types, Server Tasks, etc, and these include the ability to copy them within the same machine to provide a duplicate, or to copy from one machine to another in case you need to distribute the file (which is normally done by export/import rather than copy/paste). These built-in facilities in Dashboard are the only approved way in which to carry out those actions.

Copying, moving or deleting files in the configuration folder by other means such as using Windows Explorer or a command prompt is absolutely not approved and is extremely likely to cause problems. When you use the export/import or copy/paste/clone/delete facilities in Dashboard, a number of special processes are automatically carried out in relation to security, linking between various configuration files, identifying the machine on which a file was created, tracking which files exist, and so on. If you simply move, copy or delete a file in the configuration folder using a normal file manager or command prompt, none of those special processes will be carried out and there is a very high probability that either immediately or at some point later this will cause serious problems, up to and including loss of data and/or the entire installation becoming unusable.

Also, a file being deleted or copied outside of Dashboard may actually be in use by the Configuration Manager service at the time, so the attempted action may fail altogether anyway, or in the case of a file copy the copied file may not be intact (this won’t happen when you use the facilities within Dashboard as they make sure the file isn’t in use before doing anything like a copy or delete).

Type 4 printer drivers are recommended when printing from eVo

[su_note note_color=”#acf596″]When printing directly from eVo, if possible a Type 4 printer driver should be used.[/su_note]

This is because eVo uses Type 4 (XPS) printing, so if a matching printer driver is used then no format conversion is required and that avoids any potential problems and saves time. It is possible to print to a Type 3 (GDI/EMF) printer driver directly from eVo, and Windows will automatically convert the output into GDI format so this will normally work, but it will take slightly longer to print due to the time taken for the conversion. Also on rare occasions it has been found that the conversion routine (which is built into the Windows printing system) can fail to work correctly, resulting in corrupted output being sent to the printer. This may prevent the print job being printed at all, possibly with an error being reported, or it may be printed but with the content not as intended. Switching to a Type 4 driver avoids this problem.

To determine the type of an installed driver, go to “Devices and Printers” in Control Panel, select any printer, then click on “Print server properties”. In the dialog which pops up, select the “Drivers” tab and all the installed printer drivers are listed along with the type of each one. Unfortunately, many printer driver downloads and installers don’t seem to mention which type of driver they going to install, so you may need to install a driver first in order to then look in that dialogue and find out which type it was. A driver is likely to be Type 3 if there is any mention of either that type, or GDI, or EMF. It’s likely to be Type 4 if there is any mention of XPS, WPF, or print tickets.