LUY 8.2.0

LUY 8.2.0

August 2025

With version 8.2.0-1 we are taking a major step forward by migrating from XWiki to Markdown, ensuring modern and consistent text formatting across LUY. We have also added a new predefined “Version – built-in” attribute to give you more control when working with versions of information systems and technical components. In addition, case-insensitive lookup in the Plugin API improves consistency and reduces the need of manual workarounds.

As always, this release also includes several performance optimizations and bug fixes to keep LUY reliable platform for your enterprise architecture management.

Please ensure a backup of your current LUY Data before updating to version 8.2.0-1. Especially considering our transition from XWiki formatted text to Markdown (see 1.1 below).

Improvements

1.1 Migration of LUY’s text formatting syntax from XWiki to Markdown

All multiline text fields, including descriptions and multiline attributes, in LUY are now stored in Markdown instead of XWiki syntax. This change ensures better interoperability with external tools, simpler formatting, and improved content rendering in the new frontend.

We have implemented markdown in such a way so that it is compatible with our LUY Classic frontend: The backend automatically converts Markdown to HTML for seamless rendering in the old UI. In order to use formatted text in LUY Classic, you will now need to use markdown formatting syntax.

Error handling & logging: Any failed XWiki-to-Markdown conversions are logged while preserving the original text.

The most frequently used formatting options work very similar in XWiki and in Markdown syntax. Some advanced XWiki syntax may not convert perfectly—review after migration. Markdown focuses on simplicity and readability, so some custom stylings are not supported. (see our Markdown vs. XWiki comparison in the expand below.)

With LUY now expecting Markdown formatting, please ensure that your Plugin and REST API integrations are using markdown formatting instead of XWiki.

Text input using XWiki syntax will be technically accepted, but won’t look good in LUY Classic since XWiki syntax is not translated into formatted text anymore.

* item 1
** item 2
*** item 3
* item 4

* item 1
  * item 2
    * item 3
* item 4

1. item 1
11. item 2
111. item 3
1. item 4

1. item 1
  1. item 2
    1. item 3
1. item 4

1. item 1
1*. item 2
1**. item 3
1. item 4

or

* item 1
*1. item 2
*11. item 3
* item 4

1. item 1
  1. item 2
      1. item 3
1. item 4

or

* item 1
  * item 2
    * item 3
* item 4

(% style="list-style-type: square" %)
* item 1
** item 2
* item 3

* item 1
    * item 2
* item 3

; term
: definition

First line  
Second line

|=Title 1|=Title 2
|Word 1|Word 2

or

!=Title 1!=Title 2
!!Word 1!!Word 2

| Title 1 | Title 2 |
| ------- | ------- |
| Word 1  | Word 2  |

(% style="background-color:red" %)
|=Title 1|=Title 2
|Word 1|Word 2

> This is a single quote.

> This is other quote with nesting.
>> This is the nested quote.

> This is a single quote.

> This is other quote with nesting.
>> This is the nested quote.

|=Header 1|=Header 2|=Header 3
|Cell One|(((
= Embedded document =

Some embedded paragraph.

* list item one
* list item two
  ** sub-item 1
  ** sub-item 2
))) | Cell Three

Performance optimization:

• Database queries related to formerly XWiki, now Markdown rendering have been optimized for faster load times.

• Improved caching of attributes.

1.2 Introducing the “Version - built-in” attribute

With this release, we are excited to introduce a new predefined LUY attribute called "Version - built-in". Per default it is enabled for information systems and technical components. This provides you with greater flexibility and control when managing version information for these building block types.

What does this mean? In LUY, all characters following a "#" in the name of information systems and technical components are interpreted as the version number of this information system or technical component. This value will now be automatically recorded in the "Version - built-in" attribute.

For example: An information system named "LUY #8.2" will automatically have its
"Version - built-in" attribute set to "8.2".

This attribute is read-only and is automatically updated when changes to the name of its information system or technical component occur.

You have full access to the version values within the following LUY features:

• Filter in list view

• Filter in all types of diagrams

• Query console

• Part of the Excel export as a separate column

• Plugin API

• REST API

To use the attribute in the Query console, Plugin API, or REST API please use the technical name provided on the page Technical names.

This new feature will soon replace the current "Version" filter, which is currently only accessible in the filter. To ensure a seamless transition for future releases, we highly recommend updating your current reports to use this new predefined attribute.

Important:

If you have previously created a custom attribute named "Version - built-in", please rename your custom attribute before the update to avoid conflicts with the new predefined attribute.

Limitations:

• The "Version - built-in" attribute is available as a column in list reports but it is not visible in the single element view. For cloud customers, the attribute is visible in LUY Nova.

1.3 Case-insensitive lookup is supported in PluginAPI

We improved the behavior of api.datamodel.findByTypeAndName to add an option to search for names specifically case-insensitive. Admins setting up the PluginAPI can now use a new ignoreCase option.

Previously, the method returned no result if the exact case did not match, e.g. searching for “JIRA" did not find an element named “Jira". This behavior was unintuitive and inconsistent for users configuring PluginAPI-based logic.

Now, by explicitly setting the ignoreCase flag to true, you can search in a more user-friendly and predictable way:

api.datamodel.findByTypeAndName('InformationSystem', 'JIRA', { ignoreCase: true })

Without the ignoreCase flag the method remains case-sensitive to preserve backward compatibility.

Fixed bugs

• Fixed an issue where relation attributes were incorrectly displayed in the list view.

• Fixed an issue where surveys could not be created via PluginAPI.

• Fixed an issue preventing api.metamodel calls in PluginAPI from functioning in reaction scripts. Scripts using metamodel methods now work reliably without the need for a manual workaround.

• Fixed an issue where setting a custom color for outer/inner type coloring in nested cluster diagrams would cause the other type's coloring to be removed.

• Fixed an issue where enabling external sharing on a report would inadvertently delete its associated tags.