RELEASE: LAGO TANA 6.9 Now Available!

Published On: November 13th, 2025|By Comosoft|3.6 min read|

Dear Customers,

LAGO Tana 6.9 – The New Release Is Here!

A strong finish to 2025 and a promising start to 2026. The year 2025 has flown by – full of exciting projects and shared success. As we prepare for the festive season, we’re excited to present the new LAGO Tana Release 6.9!

With LAGO Tana 6.9, we once again focus on innovation, efficiency, and seamless integration. This update delivers powerful new features designed to make your workflows smoother and more transparent than ever.

More Transparency with LAGO History Triggers
You can now configure History Triggers to view completed or deleted automated jobs. This gives you full visibility into your processes and ensures complete traceability across your workflows.

Optimized Color Management with the LAGO Asset Processor
The new LAGO Asset Processor module allows you to centrally define color profiles used when importing assets in the CMYK color space. At the same time, LAGO automatically generates RGB previews – ensuring consistent colors and perfect presentation across all media channels.

New Possibilities with the LAGO API
The LAGO API now supports import and export of InDesign documents, enabling even smoother integration with your creative workflows.

Of course, LAGO Tana 6.9 includes many more enhancements – all detailed in the accompanying Release Notes. We thank you for your trust and collaboration throughout 2025 and look forward to an inspiring and successful 2026 – with more innovation and smarter solutions from LAGO!

Kind regards from Hamburg

Peter Jozefiak | Managing Director

Released version: LAGO Collection 6.9.1.39

Find the downloads, release notes and further information in the customer area of our website:

VISIT CUSTOMER AREA

Highlights

LAGO History

As of LAGO TANA 6.9 it is possible to create history triggers for automat jobs. This allows to also view completed or deleted automat jobs.

Product Data and Asset Management

It is now possible to check in assets in LAGO DAM via a dedicated new icon that can be found below the previews of the respective assets. The already existing icon for the export can be used for the check out. Checked in assets can either replace the old asset or be uploaded as a variant.
The functionality “Split and Merge”, that was available in LAGO Explorer, has been added to LAGO PIM.

LAGO Asset Processor

For the Import of Assets with the LAGO Asset Processor it is possible to configure color profiles in the Central Configuration. They will be used when importing CYMK assets and when creating RGB assets for previews and thumbnails:
LAGO/Image/ColorProfileForCMYKInput
LAGO/Image/ColorProfileForRGBOutput
If no values are specified, USWebCoatedSWOP.icc will be used for CMYK Import and AdobeRGB1998.icc for RGB Export.

LAGO API

There is a new endpoint for the LAGO API making it possible to import InDesign documents to LAGO:
PUT baseURL/LagoLink/link/v3/documents/indesign/documentID/projectId/VariantTypeId
There is a new endpoint of the LAGO API which makes it possible to export InDesign documents:
baseURL/LagoLink/link/v3/documents/indesign/projectId/VariantTypeId/page

LAGO Admin

The new user right ‘Manage Menu details’ is now available under ‘Administration’. When having this user right assigned, it is possible to create, edit and delete menu values and sub-menus without having the user right ‘Administrator’. To create, edit and delete menus, the user still needs to have the user right ‘Administrator’.

XML export

Two new optional attributes have been introduced for shops:
ShopTypeName (type: xs:string)
UniformInHierarchy (type: CMXMLBoolean)
These attributes are only written if both the central configuration entry (LAGO – Shop – ShopTypesMenuName) and the menu specified there in exist. If menu elements are missing, an empty string is written for the menu type.
In LAGO PIM it is possible to start an XML export for a selected shop.
It is now possible in LAGO PIM to trigger the rules for automatic assignment of elements and articles to a selected shop.

Automat jobs

The automat job type “Collect for Output” created one folder per document head variant, resulting in many duplicate assets being exported in case many similar elements exist among different document variants. Now the user can choose to export all pages of a project into one folder, sharing a folder with the linked assets when running an automat job of the type “Collect For Output”, in order to save disk space and time and when exporting data. The checkboxes “Project into one folder” and “Variants into one folder” are available in the automat job settings configuration.