Technical Changes 11.200

various announcements, apparently Vanessa and Stefan Berger have built something

With the help of serial appointments, appointments can be created automatically according to detailed settings.

The start date of a new appointment series is always TODAY. If the 'Start' field on the card is filled, this is the start date. If the appointment series is changed or extended, the start date is the current appointment and not the original start date, which is in the past.

When defining appointment series, a preview of the next three appointments in this series is displayed. If parameters are changed in the series definition window, the appointments in the preview change immediately.

Record restrictions can specify that only certain records in a table are shown to users. Other records in this table then remain “invisible”.

Restrictions can now be set on catalog fields, i.e. on fields that are contained in the catalog that lies behind a field.

This is useful for object catalogs, for example. If the object type 'Building' is stored as an object catalog on the 'Room' card (FM hierarchy), it can also be used here for the fields on the 'Building' card.

The setting takes place in a structured overview, similar to filtering a selection.

See also “Known Issues” below.

If the 'Basics.Record.GetCatalogFieldValue' building blocks was used in the rules, which reads the value of a field from a catalog entry based on a search value, it returned an incorrect value for languages ​​because it always compared with field ID 5 instead of with the field ID 2000005 to take the languages ​​into account.

When logging into an Offline Data World, for example, with waveware MOBILE, a message appeared stating that all licenses had been expired, even though there were still enough client licenses available. In this case, the login was canceled.

When synchronizing with SYNC, the following message could occur: "Record errors occurred when attempting to import the data from the Main Station via SQL. The data on your device is not complete. ...".

When updating a local station, the error "Resolution failed with error: No public constructor is available for type LoyHutz.AppStack.PackageUpdate.IRubyInstanceManager." appear. In this case the update was aborted.

A selection called by the ServiceCoordinator in the waveware Windows client always restored old settings (e.g. with filter values ​​in the filter line) and never updated them (so these filter values ​​could neither be changed nor removed).

If the filter line was displayed directly when a monitor list was created (property 'Show filter line'), then this line had no function in the selection result. Input to the line was not applied.

When activating a data world, fields that cannot be left empty could trigger critical errors (INT or BIGINT fields if less than 0 was entered) or warnings, which in turn could lead to the data world being put into service mode .

If a new field was created, added to a card and the changes were then imported while the waveware Windows Client was open with the customized card and an automatic logout took place, it could happen that entries were made in the new field after re-logging into the Windows Client were emptied.

When changing import sources, the client could crash with the following error message "ItemsControl is not consistent with the associated item source."

In the selection, tag fields can also be included in the list.

Tags can have a path structure with parent tags. The option 'Show parent tags' is available in the field properties. The respective tag path is then shown as a result of the selection.

When logging in to any waveware client, the 'Save login' function can be activated in order to log in automatically the next time the application is started. Checks that were previously carried out on the client side have been moved to the waveware server. The token that is generated in the event of a successful login with 'Save login' is still stored locally.

The behavior has also been adjusted: If the 'Stay signed in... allow' function was previously deactivated in the waveware server settings, the login was completely aborted with an error message if the checkbox was checked in the login dialog. Now the message “Save login not allowed” appears, but the login is still carried out. In this case, it will not be saved and you will have to log in again the next time you start it.

Backups can only be imported into existing data worlds. In order to import a backup into a new/empty data world, the data world must first be created manually.

The selection box "The selected data world is used to import the backup" in the dialog for importing a backup is no longer needed and has been removed.

When logging in to DataManagement, the password that is set up as default when waveware is delivered must be changed. If you have already changed your password as recommended before updating to this version, you will not be prompted to change it.

When you log in to DataManagement with the default delivery password, a dialog appears asking you to change your password. Enter the new password here that you would like to use to log in to Data Management in the future.

The supervisor password can be changed via DataManagement ('Miscellaneous / Supervisor password'). Previously, an empty password could also be entered here or the password could be reset.

In the future, the supervisor password can no longer be left blank when resetting via DataManagement.

Using the new card function 'Share' in the 'Card' menu area of ​​the Windows Client, a link to the currently open record can be created. If the link is sent to other people, they can open it in a browser or in their own Windows Client.

The prerequisite is that the person who opens this link has the current waveware Windows Client locally and has access to the record. When the link is executed, the waveware Windows Client is started and the card that was previously shared is opened.
You can create a link using the 'Share' button or [F11] when the card is open. With [F3] a link from the clipboard is opened, if available. Otherwise a window for entering a link will open.

If the CAD viewer was in selection mode and a specific room was opened from it, it could happen that not the correct room was displayed, but another one from a completely different floor plan.

Catalog field values ​​determined in List And Label print forms using the 'GetCatalogFieldValue' function were not always loaded correctly.

Fields of type 'Image' can be given a file size limit via the Supervisor Options (System / waveware / General / Field size limit). If this limitation was subsequently activated or reduced, problems could arise when saving existing records with images that were too large. The record cannot be for example, saved until the image that is too large has been replaced. In addition, the automatic scaling did not work properly when adding new images.

The functionality has been adjusted so that there is no error message on the card for existing record. i.e. the record can be opened and saved as normal. If you add an image that is too large, it will automatically be scaled down to the maximum size set in the Supervisor Option.

Time fields could not get current time in the appointments on iOS. In this case, the time selected in the editor was not included in the field.

Roles in the rights system can be provided with a description to store information about the purpose or scope of a role.

These descriptions are now displayed for roles in the availability dialog (e.g. selection). The search function also searches in descriptive text.

When restoring a backup that was previously created without DMS, there was always a query as to whether the DMS should be imported. If the query was confirmed with "Yes", an existing DMS that is stored directly in the data world was deleted.

If a backup without DMS is restored in the future, the existing DMS will always be retained. The message only appears if there is a DMS in the backup to be restored or if changes are made to the DMS.

The waveware MOBILE 2 (BETA) app can now also be used in Offline Mode, which is required if a direct connection to the waveware server cannot be established while using the app.

The app is in BETA stage. Its use is therefore recommended for testing purposes only. In addition, use requires that the data world has been set up accordingly ('DataManagement: Duplicate / Offline').

During a CAD-DWG import, the client crashed when zooming on block references (clicking on the eye symbol).

If you were logged in to DataManagement as a customizer and tried to change your password, it could happen that the waveware server settings were reset to the default.

Runtimes can be set for client connections, after which a session becomes invalid and an automatic logout occurs. It could happen that there was no logout after the set time had expired.

The app logs could not be sent via email on iOS. The email app was displayed briefly and then immediately closed again without any input being possible.

If a selection has been created with a flexible filter that can be assigned a value before each execution of the selection and executed via the Service Coordinator in the app, no search was carried out when entering the filter fields and therefore no suitable values ​​were suggested, as is usual in other clients.

When subsequently setting up operations via the 'Tools' / 'Operations' / 'Setup/update Operations' menu, it could happen that operations could not be created if catalog entries were no longer available.

If the filter of a selection was changed in waveware Web and the change was not saved before execution, it could happen that multi-operations that you only carry out for all records in the monitor list were instead applied to all records in the table. Example: default filter of the object type 'Room', which in the initial state determines all records ("Room ID not empty"), adapted so that only one record is output in the monitor list. In this monitor list open 'Multi', 'More actions' and e.g. apply Currency Field Recalculation to all records in the monitor list. A message then appeared that the rule was executed for all records in the table, instead of just the one filtered record in the monitor list.

The new waveware MOBILE 2 app is available as a BETA version and is delivered with waveware 11.200.7135 or can be installed via the Google PlayStore or Apple AppStore. You need at least a waveware server 11.200.4370 to use the new app. Offline Data Worlds cannot yet be used in the new app.

The waveware MOBILE (1) app used libraries from Xamarin, whose support was discontinued by Microsoft on May 1, 2024. The new waveware MOBILE 2 app is based on .NET MAUI and is currently in the BETA stage. It is possible to use both apps in parallel on one device.
Further information: 'waveware MOBILE 2'.

A new setting is available for the selection outputs 'Microsoft Excel' and 'CSV file' to set the separator for a line break within memo fields.

As before, the default setting is "\r\n" for CSV and "{CRLF}" for Excel output. Other possible separators are now "{CR}", "{LF}", "{SPACE}", "{TAB}", ";" and ",".

The 'OutputPicker' building block creates a dialog for selecting a selection output. Previously, “Objects and Catalogs” and “Comprehensive Selection” were available there.

Now the 'OutputPicker' building block enables also the "FreeSQL" selection output.

When packages are updated, an update log is output as an HTML file via the package manager.

Now the package update log contains also information about versions of the updated packages.

If an export was called via the Windows Client, the client option was not taken into account. Only data from the current client was ever exported. In addition, no export rules were executed in the Web Client.

In addition to a normal installation via the MSI package, the waveware server can also be extracted into a directory. This will be started via the file "WavewareServerExtract.cmd", which is located in the shared directory. The extraction aborted with an access error.

The script shell in DataManagement can be used to check update scripts syntactically and to execute them. An error could occur when executing the scripts.

Window titles on card tabs were not displayed completely depending on their length and were shortened dynamically.

The new Supervisor Option "Show tab text completely" can be used to ensure that the text in the card tab (e.g. object name) is not shortened.

The 'wavewareServer64.msi', which installed the waveware server in previous versions, has been renamed to 'wavewareServer.msi'.

The functionality is unchanged. An update of the waveware server can be carried out as usual. If you use scripts for automated installation, adjust them with regard to the new file name.

This release is an LTS version (Long Term Support) that includes 12 months of critical security updates. LTS versions are particularly interesting for companies that need stability in their IT system and are less interested in the latest functions.

Going forward, LTS versions will be released at 6-month intervals (October 2024, April 2025, October 2025, etc.) and will receive critical security updates every 12 months. This way you only have to perform a major update once a year to be able to safely operate the version with a few smaller updates. Further information under 'Version Scheme and Support Duration'.

A filter line can optionally be displayed in a monitor list. If a filter value was selected from a catalog, you had to click in the filter field again after selecting the value in order to apply the value.

Fixed: Filter values ​​selected from a catalog are applied directly.

If automatic check-in/check-out is activated in document management, an access error could occur when opening checked-out files. The file could then not be opened in read-only mode.

If a value was selected from the catalog for a catalog field in the waveware Windows Client, then removed from the field and then selected again via the catalog, the field remained empty.

Client groups enable summarized displays of records from all clients that have been assigned to the group. Client groups that contained at least one inactive client were not displayed correctly for other active clients in the group.

When assigning roles to users via the rights management dialog, roles with very long or compound names were difficult to identify because these names were cut off in the dialog.

Fixed: The rights management dialog has been revised so that the lists of assigned and available roles adjust to the window size.

With the help of the 'Collective Object' package, various objects can be grouped together for a common ATA process. Its operations are then transferred to the individual objects that belong to the collective object. Time and costs from the ATA process of the collective object can be distributed among the individual objects. With the help of this package, similar appointments can be bundled into one appointment and only this appointment can be processed, for instance.

The soon-to-be-released 'Waste Management' package records waste containers with precise data on waste types (European Waste Catalog EWC), location, quantities and other information. The counter function is used to record waste quantities. The evaluations provided give an overview of the waste balance.

A crash could occur if, for example in a key management locking plan, all locks in a row or column were set at the same time.

A series, e.g. consisting of appointments may not have been resolved correctly if the start date was subsequently changed. It could happen that the first date of the series appeared twice.

Basic functions of waveware can also be provided via the web browser using Custom Pages. You can now influence the display of bool fields.

The Custom Page control 'LhFieldContent' determines the corresponding input field that matches the type of field from a specified table number and a field ID. Bool fields can now be displayed in various ways, such as a checkbox (default), switch or toggle. To do this, the new attribute 'BoolDisplayType', which regulates this display type, must be transmitted to 'LhFieldContent'.

Data entered into waveware can be prepared and output using various printing options.

When printing the 'Email with PDF' output, the text of the email can now also be interpreted as HTML. To do this, activate the 'Text as HTML?' property. You can then enter HTML in the 'Message text' field and format the text in this way.

With the help of a tracing, time data can be collected that is needed to resolve latency issues during rule development. External tools (e.g. Jaeger) can collect this data after the interface has been set up.

When using Jaeger, you must now ensure that the "jaeger-all-in-one.exe" is started with the parameter "--collector.otlp.enabled". Also check the setup dialog in waveware DataManagement: the settings for Jaeger have been combined to specify an 'endpoint URL'. For more setup information: 'waveware Server: Tracing and Metrics'

Target values ​​could be defined in the dashboard, but did not appear in the diagram. Setting the coloring of the target value in the display area may also not work under certain circumstances. The color setting field remained empty despite the color being selected.

The Designer could crash if a drawn field was placed on a card within the 'Templates' Designer session.

Using the print dialog, an address and an associated contact can be set, which will be sent to the form when it is printed. After setting an address, the contacts are automatically filtered. However, if the contact selector was opened by double-clicking the 'Contacts' field, the contacts were not filtered correctly.

An Image field can be used to load and display images into a record. If such field was present on a transaction, it could happen that the field content was not updated correctly when scrolling between transactions.

The font and size between drawn and regular fields differed on the card. This caused various disadvantages in card design.

Fixed so that drawn and regular fields use identical fonts.

Single Sign-on With SAML could only be used on the Waveware Web if the protection against "Cross-Site Request Forgery" (CSRF) was deactivated in the settings of the waveware server (area 'Web server').

Selection: The button to adjust column widths to fit content appeared in a monitor list on the web only after running an output setting without the 'Adjust Columns' option.

Change to a function: A serial appointment "Safety Inspection" have previously also been created for sub-devices of ME objects with the property 'ME system' = "1" and 'ME system' = "1+2" ​​for which there is a serial appointment "Safety Inspection",  .
Since the probability that devices connected via 'Belongs to' will have individual appointments is significantly higher than shared appointments and problems can still arise with shared appointments, the dependency between the appointments of the devices was switched off.

With energy management, a comprehensive tool for consumption analysis and process optimization is now available. The two Meter packages 'Meter transaction' (1104) and
'Meter object' (1116) expanded and modernized. This module also includes the new packages 'Registering performance measurement' (1921) and 'Meter Evaluation' (1927).

In waveware, a self-defined working area with the desired views (cards, tool windows...) can be used when starting.

With the new building block 'ApplyWorkingArea', which is used in the started rule, a supervisor can administratively provide a working area for users. This working area is loaded at startup, regardless of whether a user has defined a personal working area himself.

Via interfaces, e.g. REST, external applications can execute parameterized rules on the waveware server. This requires prior authentication of the user under whom data is to be queried.

You can now also use access tokens for authentication to make accessing waveware from external systems easier while making it more secure. After activation via the waveware server settings, access tokens can be created as a transaction on staff records. Further information: 'Interfaces: Access via Token'.

Microsoft .NET offers libraries for integrating modern functions into your own programs. The current .NET 8.0 release includes improvements to performance, garbage collection, and the core and extension libraries. waveware is now based on .NET 8.0.

It is not necessary to install the .NET 8 runtime manually. waveware applications automatically include the required runtime components.

In connection with the update to .NET 8.0, the DataManagement PowerShell module also requires at least version 7.4.1. Versions below are no longer supported.

When using the DataManagement PowerShell module, it is checked whether you are using at least version 7.4.1 of PowerShell. Otherwise a corresponding message will be shown. More information: 'DataManagement: PowerShell/Command Line'.

Google Chrome and browsers based on Chromium (Microsoft Edge, Opera, Brave, Vivaldi, etc.) at least version 119. Mozilla Firefox is required in version 118 and Apple Safari in version 17.

If a text with a leading space was inserted into an existing field using the multi-function 'Change field contents' ('Append new field contents to old'), the space was cut away.

An optional filter line can be displayed in the 'Monitor list' selection result. If "like" or "not like" filters with square brackets in the filter term were used here, the filter was not applied correctly and the monitor list was often emptied.

A plan loaded into the CAD viewer was displayed when scrolling through objects, e.g. rooms not updated.

Colorings that were set up for the Navigator in the 'Structure list' area were not displayed correctly in the waveware WEB.

Fields that are stored as locked in the database could be changed via the client under certain conditions.

Fixed: Locked fields can no longer be changed from the client.

Single Sign-On (SSO) enables uniform authentication in the working area using Kerberos, MSAL or SAML. Despite successful registration, it could happen that  an error message ["Cannot read properties of null (reading 'errorCode')"] was displayed in the waveware WEB.

Operations are displayed in a structured manner in waveware. If there are operations for an object, they are displayed automatically. When scrolling to an object that does not have any operation, it could happen that the operations of the previous object were displayed.

Single Sign-On with SAML can only be used in waveware WEB if protection against "Cross-Site Request Forgery" (CSRF) is deactivated in the settings of the waveware server ('Web server' area). If you have activated protection against CSRF and are using SSO with SAML in waveware WEB, postpone the update until the next release if possible.

Tags can be used to uniformly label records from different tables to make them easier to find, group and assign.

As of waveware 11.200.5266, rights to use tags can be assigned in more detail via the rights system. Since then, a distinction has also been made between local tags (for specific tables) and global tags (for all tables) during creation.
The global right 'Use tags' is no longer required and has been removed. Roles that had this global right in previous versions have been migrated to the 'Tags: Global Tags' global right. Existing tags from previous versions are automatically available globally for all tables. In addition, personal tags are now always available globally for all tables. The options when creating a tag have been adjusted accordingly. Additional Information: 'Tags'.

Notifications are short messages that inform waveware about actions and status changes, e.g. about a newly received task or the imminent arrival of an appointment.

As notifications, when enabled via the global right, can be an important part of the information flow, the Notifications window is now always displayed. This ensures that notifications reach users. The window can still be placed anywhere, but can no longer be closed. Further information: 'Notifications'.

If the display of a selection is suitable for a group, you could previously switch to the group view using a button. All grouping levels were then expanded. This meant that the list could become confusing if there was a lot of data.

Now with the option 'Activate group view' the result with this option can be displayed with the group view activated. To do this, the list must contain at least one grouped field.

With the 'Expand group view' option, the result can be displayed with all rows expanded when the group view is activated.

After executing the 'Multi' function, it always returned to the start of the selection.

Now this selection is executed again and the selection result (after the changes made by Multi) is shown. If a placeholder query was used, the selection is executed again with the previously used placeholders.

When opening the appointment series dialog, the default setting for the series pattern was previously "Monthly, in this month".

The default setting now depends on whether the 'Start on' field on the appointment card is filled. If so, this date is used as the starting date, i.e. "Monthly on [date]". If the 'Start on' field is not filled, the setting remains "Monthly, in this month".

The 'Print Properties' dialog box was a bit too small by default, so not all of the content was visible.

In the case of an object-level selection, records were not displayed in the calendar if the object/catalog did not have fields of type "Date(Time)".

If an import rule 'Global for all tables' is set in the import options, the settings 'for all objects' are used instead when evaluating the import options. This can lead to errors during an import.

After adding a document in the DMS, the 'Tags' tool window was activated incorrectly.

The Ruby engine was not running with the waveware server service. Among other things, CustomPages did not work correctly. It was only possible to use it if the waveware server was run via console.

Due to an error during session creation in the waveware server, an increased memory usage could occur. This in turn could lead to delays in the processing of internal processes.

If the waveware Mobile Client was left idle for several minutes without any interaction, high processor load caused the app to crash.

When logging into with waveware Mobile using Offline Data Worlds, there could be increased waiting time.

Optimizations in caching and server availability queries to reduce login wait times.

The Ruby engine does not run with the waveware server service. Among other things, CustomPages do not function correctly. It can only be used if the waveware server is run via console.

MQTT is an open protocol that enables communication between machines. With the MQTT module, waveware provides functionalities with which MQTT clients can be created in a data world-related manner.

The MQTT protocol works on the principles of the publish/subscribe model. The transfer of data between the MQTT clients is usually handled by an MQTT broker.
MQTT clients, created on the server side via the waveware MQTT module, establish connections to MQTT brokers and execute publish/subscribe actions.
Further information in the article 'waveware Server: MQTT'.

Combined selections previously had no setting to output one selection per worksheet when using an Excel template.

Multiple selections can now be output even when using an Excel template file with the target option 'one worksheet per selection'.

The JavaScript API can be used to influence the runtime behavior of the CustomPage controls. 'MultiCatalogControl' now allows access to the MultiSelect ComboBox.

A new 'MultiCatalogControl' element provides access to the MultiSelect ComboBox used to select a field value via the JavaScript API in Custom Pages. Functions can be used, for example, to retrieve or reset current field value.

LHSQL is SQL syntax optimized for waveware. This syntax is based on the T-SQL syntax and extends it with its own functionalities. Support for SQL functions has been expanded.

The SQL functions 'LAG', 'LEAD', 'RANK', 'PERCENT_RANK', 'CUME_DIST', 'NTILE', 'FIRST_VALUE', 'LAST_VALUE' are now available in LHSQL and can be used in rules or the SQL tester, for instance.

Depending on the type of output, address information can be specified during printing, which is transferred to the print forms. The display of these address catalog fields can now be customized.

The display of the Companies catalog fields can be set using the Supervisor Option 'Properties' (System / System (0) / waveware / Print options). By default, the record ID is displayed for each table.

Using the 'Adjust line height' property, you can use the selection list to set the line heights of a monitor list to be dynamically based on the field contents. Up until now, only a fixed line height could be set in waveware Web.

The 'Adjust line height' option is now also available on waveware Web.

Keyboard navigation has been improved in the waveware Windows Client.

If you switch between document windows/cards in the Windows Client using the key combination [Ctrl] + [Tab], the input focus is now in the window when it is opened, so that you can switch between fields directly using [Tab]. For monitor lists or FreeSQL selections, after opening the window (again), you can use the arrow keys to mark a record and open it using [Enter]. Overview of the most important keyboard shortcuts 'waveware Hotkeys'.

After exporting and then importing a dashboard into the same data world, the imported Dashboard was empty after restarting waveware. The export/import of Dashboards was previously only intended for transfer to other data worlds. In the future, an exported Dashboard can also be successfully imported into the same data world.

When updating from a version <11.200.821.31, tags are automatically created from the DMS fields 'Category 1' to 'Category 3' and assigned to the respective documents. However, due to an error in the update step, the category fields were not converted.

Sub-transactions could not be assigned tags via waveware Mobile.

In Android, when creating a new tag, the keyboard was visible but the input field disappeared. It didn't show up again until typing tag name.

If synchronization was activated in the Navigator structure list, filters were applied via the header and a record was then called up from it. In the case of very large lists, it could happen that after opening the record in the Navigator structure list, not the currently opened record was marked, but only the main parent element.

This package allows you to plan and prepare instructions. In addition to the location, date and time, it is determined which people should be instructed on which types of devices. All participants can be invited to the event via email. You will receive all relevant information as well as a calendar entry and can then register or cancel registration for the event.

The Ticket Communication package enables sending messages between ticket creators and ticket editors. To do this, a sub-transaction 'Ticket Communication' is attached to the transaction 'Event'. When you save a new sub-transaction, a message is created, which is then displayed on the ticket object in the form of a new 'Ticket Communication' transaction.

Rental Management

Master Data Management (1445)

Package has been expanded to include some functions:

• Consideration of capping limits on the basic rent
• Button for transferring allocation accounts from the 'Apportionment accounts' catalog (336) to the transaction 'Apportionment accounts' (1025) on the business entity, as well as for transferring the transaction 'Apportionment accounts' on the business entity to allocation accounts on the usage contract
• Automatic creation of a vacancy contract

New function for the index check: After the index check has been carried out for the usage contracts, corresponding suggestions for adjusting the fee details are determined for the affected usage contracts in the transaction 'Index checks' (2361). These are automatically displayed in a color-coded monitor list. Suggestions for fee changes can be adopted directly from the list.

The two packages have been linked together: the operating cost balance can now be automatically transferred to the debit positions. Debit positions that have been partially or (over)fully paid (payment amount) can be automatically transferred to the actual payments (the actual payments can therefore be used for operating cost accounting).

The packages for configuring Single Sign-On have been expanded with a Supervisor Option for central switching on and off. The Supervisor Option is present in the path “Waveware Module / SSO / %SSO Package% / General”. If the option is deactivated, normal authentication is carried out and the authenticate rule of the installed Single Sign-On package is not used.

During an update it could happen that import schemes could no longer be used correctly; for example, the scrolling and display no longer worked correctly with CSV or the “default formula” could not be edited in the appropriate editor.

When logging in in Offline mode, the error "Exception has been thrown by the target of an invocation." appear. The login was then aborted.

When adding a new tag in Android, the keyboard is visible but the input field disappears. It won't be visible again until you start typing the tag name.

Tags can be used to mark records to make them easier to find and assign.

Rights to use tags can now be assigned in more detail via the table right system. Rights to view, create and assign tags are granted separately for each object type, transaction and catalog.
In addition, a distinction is now made between global and local tags. Users can create and use personal tags that are only visible to them.

When setting up a data world, command line arguments can be passed to ClickOnce installations, for example, this can cause the login mask to be skipped when starting a client. The specified command line arguments were not always applied correctly.

Creating a new data world via DataManagement led to a crash if additional windows (e.g. the System Rule Editor) were open when the data world was saved.

Fixed: Open windows are now checked before a data world is created.

On lower screen resolutions, not all elements in the window were accessible when exporting via DataManagement. There was no way to scroll.

Drawn fields enable the read-only display of any values, e.g. about rules. When setting up these fields, a "custom style" can be activated using the 'Type' property to individually define the text color and display. However, fields of this type were not shown on the card.

Quickly switching between existing export rules could cause the Export Related Catalogs or Objects window to disappear and no longer update.

When setting up catalog fields with the Designer (field type 'Catalog'), the display of the field contents can be customized. For this purpose, the fields of the catalog to be displayed are formatted with curly brackets in the field property 'Catalog field display'. The values ​​may not have been displayed correctly on the card.

When you enter an incomplete value in a catalog field, a pop-up window appears with appropriate auto-complete suggestions. If the suggested values ​​in this pop-up window were sorted using the column headers and a value was then selected, a possibly incorrect value was adopted into the field.

Mandatory fields that were only readable were no longer framed in red when empty.

A date or time can be selected in the app in corresponding fields using small dialogs that suggest the current date or time by default. If a date or time was deleted from such field, when it was re-entered, not the current time but the deleted value was suggested in the dialog.

Using the camera to add a photo to documents of a record caused the app to crash on Android 13.

When installing waveware, the Microsoft Visual C++ 2010, 2012 and 2015 runtimes were previously required. Microsoft support has already been discontinued for Visual C++ 2010 and 2012.

As of 11.200.4928.55 (September release), only the Microsoft Visual C++ 2015-2022 Redistributable (a single executable runtime) is required.

When adding a new tag in Android, the keyboard is visible but the input field disappears. It won't be visible again until you start typing the tag name.

The selections in the Mobile APP did not use filters on tables with field rights.

You can use the local package manager to install packages without an active internet connection. However, uninstalling packages was previously only possible via the package manager with access to the waveware Service Center.

Installed packages can now also be removed via the local package manager of the DataManagement. All existing packages are listed in the dialog. Select the packages to remove and click 'Remove selected packages'. Further information: 'Uninstall Packages Offline'.

The structure list in the Navigator can display a tree structure of records that belong to an object type.

The filter function can be used in the structure list to select all records belonging to the tree according to the corresponding filter terms. The result is displayed as a  flat list. If you delete the filter term from the line, the tree structure is immediately displayed again.
The filter in the structure list is only available if the Object Tree package (1013) is set up.

By default, sorting in the Navigator structure list is based on the 'Outline' field (FID 11694) of the 'Object Tree' table. A different sorting field can be set in the Supervisor Options.

If the sorting in the structure list of the navigator is to take place according to the sorting field selected there, the checkbox 'Ignore sorting from object tree package' must be set in the Supervisor Options for the respective table.

Single Sign-On (SSO) enables uniform authentication in the workplace using Kerberos, MSAL or SAML. The process is now also available for the CAD-DWG Client.

Previously, authentication via Single Sign-On was only available for Windows, Web, Mobile Clients and CustomPages. The authentication procedure has now also been adopted for the CAD-DWG Client. For example, rules already created to authenticate the Windows Client are now equally applied to the CAD DWG Client. Single Sign-On is still not supported on the CAD-DGN Client.

Building blocks for executing and displaying selections have been expanded to include optional parameters for specifying an output target.

The 'ExecuteComposedSelection' and 'ExecuteSelection' building blocks, which can be used to execute a specific selection and display the result, have been expanded to include an optional 'target' parameter, which allows specifying an output target. If the parameter is empty, the monitor output type 'New Window' is used.

If a template is deleted during the selection printout, it is checked for use in other selections. This check failed with a misleading message.

If a selection result is output as a monitor list, further temporary filtering can be applied to displayed fields in the header of the monitor list. If these filters were reset, a crash occurred if the selection contained fields that were set to 'not visible in the monitor list'.

It could happen that dashboard windows were not loaded when reopening the waveware Windows Client. The problem always occurred when the 'Custom Views' option was set in the main window layout settings, but no view was selected. The workaround is to change the layout to 'Use last view when starting the program'.

If a search was carried out in the tool window of the Windows Client and the search result was then sorted in this window, a crash occurred.

Fields that store a date in the waveware Windows Client have a small calendar that can be opened using a button in the field. If the buttons for monthly browsing were used in this small calendar, the control closed and you had to reopen it.

Fields that record location in waveware Mobile could be changed even though these fields were deactivated.

When loading an Offline Data World, no users, rights and roles were transferred if the default client with ID 1 was inactive or did not exist. In this case, login was not possible.

When using Sync, an error occurs while updating serial appointments. The message “The loaded record is already being processed or is not current” appears. Installations that do not use Offline Data Worlds are not affected.

The Selections in the Mobile APP do not use filters on tables with field rights.

Example: As soon as field rights are set on the 'Tasks' table, the filters no longer apply to this table.

If new cards were opened from various areas, e.g.  when using operations, from the navigator or when copying, the card always appeared in a new document window instead of the currently open window. The cause was an error in the 'OpenCatalogView' rule.

The Windows Client could crash if the table view was used under certain conditions. The crash only occurred if only read rights existed for the relevant transaction type, more than one record existed in the transaction type and the transaction record was reloaded before switching to the table view.

ClickOnce enables waveware installations on Windows that can be installed or updated with minimal user interaction. Under certain circumstances, errors occurred during the distribution of the ClickOnce installations. It could happen that files required to run the clients were missing after the installation or update.

The Hash attribute 'api.Filter' was not updated when used in controls. The error existed from the second execution. The first cached value was then no longer replaced.

In waveware Mobile, selections did not apply filters to tables with restricted field rights. if for example, field rights were restricted on the 'Tasks' transaction table, filters in the selection for this table were ignored and the full database was returned.

After the first successful login, the biometric login in waveware Mobile no longer worked if the values ​​in the 'Staff ID' and 'Login name' fields differed.

Basic waveware functions can also be provided via the web browser using Custom Pages. A default tag can now be specified for a file upload to the DMS.

It is now possible to configure a tag control inside a 'LhFileUpload' control. For this purpose, the control offers a new parameter 'tagsHash', into which HashAttributes for the tag control can be passed.

New rule trigger for catalog dialog

Executed when the catalog dialog is opened.
If more than one filter term is specified for the same field, the last entry is taken into account, all others are not.
More information in the help article.

TN-2305-00150

Dynamic filters can be set in the selection using date filters. If a date "TODAY + 5 months" was used here and the 'From this date' property was set to "Last day of the month", an incorrect value was returned in the case of December, namely "01/31/2024" instead of the expected " 12/31/2023".

When executing commands via the DataManagement PowerShell, errors could occur when loading "Microsoft.Extensions.Logging".

When exporting via the Windows Client in LH format, no client information was output, even if the 'Export client information' option was activated in the export rule.

TN-2306-00697

When opening a universal selection, the error message "Print form'' could not be found" appeared if the Supervisor Option 'Automatically generate missing default components' was deactivated and e.g. new transaction types were used in the selection. The message also appeared if no print output was set up for the selection, e.g. when using a monitor list.

When creating a series type for appointments, an appointment type must be set by default, since the field is a mandatory field. In the Web Client, however, the specification of the mandatory value could be avoided and the series type could be confirmed in the dialog without an appointment type.

Web CAD

In the web CAD viewer, the toolbar sometimes became invisible when navigating between cards. The toolbar appears whenever an object to which a CAD plan is linked is opened. If you then use the 'Next' and 'Back' buttons to scroll to another object to which no CAD plan is linked, the toolbar is hidden again. After scrolling back to the object with a link, the plan appeared in the CAD viewer, but the toolbar remained hidden.

With a negative evaluation of test steps in the dialog in waveware Mobile, some fields dynamically become mandatory fields. If these mandatory fields were filled in the detail view and then switched back to the list view, the note (triangle symbol with an exclamation mark) remained. Only processing another test step made the note disappear.

The 'FieldChanged' trigger was not addressed after editing a field and swiping directly to the next step within a test step evaluation.

Added missing function 'UseSapShiNamespace' to gRPC serialization. The SAP Supervisor Option 'Use SHI instead of BITLH SAP namespace' had no function.

When a data world is activated, a database structure check takes place in DataManagement, which ensures that differences between the database and DefDB are avoided and that any missing information is subsequently transferred to the database. If database errors are reported during this check, the program usually provides automatic solutions. DataManagement crashed with a message about a network problem when attempting to use the proposed solutions.

The 'SetDrawnFieldStyle' building block can be used to dynamically change the appearance of a drawn field at runtime.

The building block controls whether the submitted drawn field is displayed normally, disabled, as a caption, etc. The building block should be used in a 'FieldStates' rule and is only intended for dynamic drawn fields.

CustomPages provide basic functionalities of waveware via the web browser. The file extensions that are not permitted in the DMS, which can be set via the Supervisor Options, are now also checked within the interface when a file is uploaded.

Previously, the 'LhFileUpload' control did not take into account the illegal file extensions configured for the DMS. The server-side check prevented the upload in such case. By default, the control now takes into account the impermissible file extensions in the DMS. To change this behavior a new hash attribute 'DisableDMSExtensionsBlacklistCheck' can be applied.

With CSV import, tables and fields can be assigned to the columns of the imported file. Tables that are available there depend on which main table is selected. (e.g. 'Room' also has 'Real Estate' and 'Floor' as catalog fields on the card.)
Previously, if tables and fields were assigned, but then the main table was changed, the assignment was deleted because it was then no longer applicable.

The assignment is no longer deleted so that the assignments that have been set are not simply gone. Instead, a warning icon with a tooltip is now shown at the assignment to inform users that this assignment is unrelated to the main table and consequently will be ignored.

After selecting an output type in the print dialog, the labels for the properties of the output type were usually displayed very narrowly, making the texts almost impossible to read.

The display of these labels has been adjusted by better dividing up the individual areas (forms, output type, availability, etc.) of the print dialog. In addition, changes to the widths are now saved context- and user-specifically, so that after a one-time adjustment and renewed call of the dialog, all previously defined widths are restored.

Fixed so that the title is now fully displayed.

In the print dialog, you can use the 'Show/edit form details' button to open a dialog in which further information on the current form is displayed. Configuring data sources via this dialog resulted in an error.

If the Supervisor Option 'System / waveware / General / Show object/catalog type' is deactivated, the content of a selectable field from the card appears in the tab of a document window instead of the table name. For objects, Field ID 12 'Name' is used by default. However, if the corresponding field was empty, the title in the tab was also empty.

Fixed so that the table name is now displayed when the corresponding field on the card is empty.

When using dialogs in waveware Mobile to record or change values, it could happen on the Apple iPad that fields of the dialog were moved so far up when the keyboard was expanded that they were no longer accessible.

If a field of type 'Location' was emptied in waveware Mobile, an error "Object reference not set to object instance" appeared.

The output of field contents as a barcode was sometimes not possible in the waveware Web. An error "The barcode text has an incorrect format" was often reported, although the same field content could be successfully output to a barcode via the Windows Client.

Escalation messages can now not only be sent by email, but also as a notification. For this purpose, another card area 'Notification Settings' is available in the 'Steps' transaction, in which, as with the previous email settings, the message to be sent can be configured.

A detailed summary is now displayed in the test data preview after a record has been transferred, in which you can read exactly which records were moved from which location to which location or were newly created. A current waveware version is also required for this.

With the 'First Aid Book' package, supported by an assistant, accident reports can be created quickly and easily, recording the people involved, the location of the accident, a description of the course of the accident and, if necessary, a picture. These can be worked out in detail later.

The 'Risk Assessment' package supports users in assessing and documenting the risks that occur at the workplace. The risks can be assigned to different scopes and measures can be defined if necessary.

Additional security when logging in: The package provides the necessary rules/fields to generate the codes for two-factor authentication and then to request them when logging in.

Quick reference to other waveware users about a record. Note is used manually with a short note text as a notification. Double-click opens the record.

When displaying the measurement history, the date of test step results was incorrect. In addition, the display of a test step for activities was inconsistent. Either the ID or the name was displayed here.

A structure overview of all usable tables and fields is available in the tree views 'Available tables and fields' in Selection/Filter and Selection/List.

Building block 'AllTags' in path 'Modules.Tags.Data', which returns all tag links associated with a record, has been renamed to 'AllTagLinksOfRecord'.

The 'List & Label' reporting tool has been updated to the current version 28 SP1 (28.001).

The creation and processing of print forms is implemented in waveware using the extensive reporting tool 'List & Label' from combit®. List & Label has been updated in waveware to eliminate an error in the Form-Designer that could lead to a crash.

If there were a lot of notifications for one person, it could happen that the waveware Windows Client crashed with an unhandled exception when trying to mark all notifications as read at the same time.

In the Designer view 'Sub-Transactions', the field list of the table view can be set for sub-transactions. However, the general properties of the view were only displayed if at least one field was added to the view.

Fixed: General properties are now also offered if the view has not yet been assigned a field and the standard field list is therefore valid.

If for example, the properties 'Editable' or 'Mandatory field' were changed, it could happen that the title of the field in the grid became invisible.

In the Designer, it can be specified for catalog fields whether entries from the catalog must be used or whether free text input is also possible (mandatory catalogs, 'M.Cat.'). When trying to enter free text in such field in the Windows Client, the catalog window first opened. If the window was aborted or confirmed, the error message "RuleException" appeared.

When performing data homogenization, e.g. second ME types, all assigned instructions and their documents were transferred to the other type, but not the documents that were directly assigned to the ME type.

If an existing photo was transferred to an image field on Android, the image was displayed rotated.

Assigned and available tags may not have been visible in waveware Mobile if the current app was used with an earlier version of the waveware server.

Offset error in the list of drawings that can be displayed in CAD Custompage, so nothing was displayed when the last list item was selected.

The DataManagement Client can be started with parameters via the command line and a login can be carried out.

A new Supervisor Option makes it possible to hide tables in DataManagement. In this way tables that only provide raw data for certain functions for instance, are invisible in the Designer and the System Rule Editor.

The Supervisor Option 'System / System (0) / DataManagement / General / Hide tables in DataManagement' allows the BIM raw data tables to be hidden in the Designer and the System Rule Editor (e.g. in the 'FieldPicker' building block).

If files are linked via the 'New' dialog, only one file could be selected in this dialog. It was only possible to link several files using drag & drop.

Multiple files can now be selected and linked at the same time via the 'New' dialog.

A field of 'Location' type can be used to collect and store geographic positions. Positions could differ incorrectly and be displayed slightly shifted, when setting and subsequently opening via the positioning dialog. In addition, viewing, navigating and zooming was not possible without changing any existing position information.

The 'SetStandardButton' building block can be used to create and change buttons in the waveware ribbon using the System Rule Editor. However, the building block parameter for adjusting the index, i.e. the button position in the ribbon, had no effect.

Fixed so that an index passed to the building block is applied correctly. In addition, you can now use the "-1" index to always place the button at the end of all buttons on the ribbon.

When assigning transactions to objects in Designer view mode, it could happen that the context menu could not be used and the assignment could not be completed.

When using an InputBox to query values ​​in the Windows client, it could happen that the last 2-3 characters were not visible when entering a text field within this InputBox if the content was very long.

When tapping on 'Back' in the calendar of the Mobile Client while creating a new appointment or when switching from month to day view, the app could crash under certain circumstances.

The placeholder "*" can be used to scroll through all objects when searching for objects in the Mobile Client. If there were more than 1000 rows of results and the end of the list was reached when scrolling, the app could no longer be used and crashed.

In the Nobile Client, an input box enables data to be entered in one dialog. Certain values, e.g. transaction numbers or device IDs, can be scanned directly via QR code. However, this caused the app to crash.

The table view for transactions could not be opened in the web client because a rule controlling the view did not exist.

A backup with a database, which in turn was created independently of the database, can be imported back into any database system. You can optionally make the corresponding setting when creating a backup via the DataManagement. An error occurred when restoring such database-independent backups, so that only the first 5000 records were restored. The workaround was importing the 'backup.wavedump' file, which is located in the backup, again.

A structure overview of all usable tables and fields is available in the tree views 'Available tables and fields' in Selection / Filter and Selection / List.

In the Web and Windows Client, the field IDs are now also displayed in brackets behind the available fields in this overview so that fields can be clearly identified if the same or similar names exist across tables.

In the area of ​​the JavaScript API of the CustomPages, the 'CatalogControl' and 'ComboBoxControl' have been extended with function parameters.

For the 'CatalogControl', there is now the parameter 'SetValue', with which a value can be set. 'ComboBoxControl' received various new parameters, which are described in the documentation.

In addition to files, a URL can also be linked in document management (DMS). As of version 11.200.2706.40, a field containing the name of this URL can be specified via the "DisplayedDocumentName" field tag.

The dialog for embedding a URL in the DMS has been extended for the FAT client. If a field has been tagged, the 'Display text' field is available in the dialog for linking a URL. A name for the linked URL can be assigned here.

When outputting a calendar via the selection, you can now set the monitor output type and an automatic update. The settings are available in the 'Calendar' output type.

You can use the 'Monitor output type' to specify whether the calendar should be displayed in the current window, in a new window or in an external window that you can arrange as you like. The 'Automatic update' setting defines a predefined update interval if new or external window is set under 'Monitor output type'.

A transport order is used to transfer changes from a waveware system to another system. This function is used to easily import customizations to packages or DEF files from a development system into a test or production system.

A system update by importing a transport order is no longer possible. The versions of the source and target system may differ at most in the build number, otherwise the option in DataManagement is blocked.
To protect less experienced users, an expert mode with more detailed settings is now available.

A system update to version 11.200 from a version lower than 11.180 is not possible.

With an update, it is now also checked whether the initial version is at least an 11.180. Otherwise a message is shown that an update sequence must be adhered to, with a link to the Update-FAQ in the Online Help.

One or more result rows of a monitor list can be easily copied out using the context menu and for example, can be pasted to Microsoft Excel. If a memo field containing tabs was copied, the field content was spread over several cells when pasted into Excel.

Fixed: Tabs are replaced with spaces in the field content.

Fixed: Room stamps are now updated on validity changes.

A context menu could not be opened for fields that are displayed as a checkbox (Boolean) on the card, because the trigger 'FieldContextMenu' was not triggered.

When deleting a field content, e.g. when a new building was created, the building ID was entered manually and deleted immediately, an overlay appeared so that the deletion could not be completed.

After adding a new tag, the tag might not display correctly in the 'Available Tags' section in the Mobile Client.

When using the 'SendSmtpMail' building block, emails could not be sent if attachments were passed in from paths. In addition, when using 'SendMail' as an alternative to 'SendSmtpMail', no Linklist/LinkRecordList could be passed in from the DMS. An error message then appeared.

The 'SendSmtpMail' building block is deprecated. 'SendMail' should be used instead, since it offers a greater range of functions. The 'SendMail' error that no Linklist/LinkRecordList can be passed in from the DMS has been fixed.

Building blocks that were previously copied from a rule in the System Rule Editor were not displayed for example, via the context menu in another rule at the level of the mouse pointer, but at the lower right edge of the rule. This could lead to them being easily overlooked and re-inserted.

The waveware Windows Client crashed when opening the export window if an existing export setting referred to a table that no longer existed.
The problem could be worked around by restoring the missing table, if possible.

The DataManagement PowerShell could not be used correctly. Accesses for example, via scripts or from external applications to create or manage data worlds failed.

When opening or creating objects, the app crashed if you were using an older waveware server (< 11.200.3434.39) and were logged in via a user account with reduced rights.
The trigger was a recently introduced right to use notifications in combination with the old waveware server.

Secure client connections set up previously were displayed as insecure in the waveware Windows Client, although they had been correctly secured in advance. This was just a display error of the message in the status line.

BETA: PostgreSQL, a free and platform-independent database system, is supported for new waveware installations.

In addition to Microsoft SQL Server and SQLite (only recommended for small single-session installations), the PostgreSQL database is now supported for test environments.
PostgreSQL is intended to serve as a free open source alternative to Microsoft SQL Server and can also operate with multiple simultaneous sessions. PostgreSQL 15.1 is considered as the lowest version.
A productive use is currently not recommended.

Print forms are created and edited using the form editor. In doing so, waveware transfers data sources to the editor, which are offered as variables, tables or fields. Previously, all available data sources were always transferred to the form editor. Depending on the scope, the data sources quickly became confusing. A large number could also negatively affect performance both when printing and when editing a form.

Since only a fraction of the data sources are often required in practice, data sources that are available in the form editor can now be configured for each form. To do this, activate the dialog for displaying the form details and click on 'Configure data sources'. By default, all data sources are still offered in the editor. More information: 'Forms: Configure Data Sources'.

waveware now has an OpenTelemetry interface that allows monitoring with tracing applications such as Jaeger.

The setup is done via the DataManagement. Click the 'Telemetry' button to configure. More information: 'waveware Server: Tracing and Metrics'.
The profiler that could be run in the System Rule Editor has been dropped. Performance problems can be diagnosed much better with the help of OpenTelemetry.

Microsoft .NET offers libraries for integrating modern functions into your own programs. The current version .NET 7.0 focuses on being consistent, modern, simple and fast. waveware is now based on .NET 7.0. This results in an improvement in the performance of the basic system and increases future security.

The DataManagement PowerShell module now requires at least PowerShell 7.3.1. PowerShell 5 and below are no longer supported. It is not necessary to install the .NET 7 runtime. The individual waveware components already bring the corresponding runtime with them.

waveware previously had two interfaces to establish client connections: one based on the web server (default port 10000) and a pure gRPC interface (port 17000). Both interfaces exposed exactly the same API. They only differ in that the integrated Kestrel web server is used or the gRPC library.

In order to simplify and unify the configuration, the pure gRPC interface (port 17000) has been removed. This also results in a smaller server size and an improvement in performance (less memory usage). In addition, administration becomes easier because only one port is required. More information: 'waveware Server: Protocol of Client Connections'.

In the System Rule Editor, a rule for 'FieldStates' can be used on the client side to specify which fields should be hidden, disabled or changed. There is a new additional trigger 'FieldStatesServer', which is executed after the previous trigger 'FieldStates' and checks server-side locked fields for changes.

Hidden and disabled fields are cached on the server side. If the client makes a change to these fields ('FieldStates'), the change is rejected. It is thereby no longer possible to manipulate the HTML in the Web Client and to change fields that are actually locked.
If this test is desired, it can be activated using the Supervisor Option (System / System (0) / waveware / Cards / General). More information: 'Trigger: FieldStatesServer'.

The CAD import can also be carried out without a user interface using the command line. Two new parameters bring more dialog options to the command line.

There are two new CAD import parameters:
"-importAsSvg" can take the values ​​0 or 1. Corresponds to the checkbox in the schema dialog.
"-levelOfDetail" corresponds to the selection box in the same group in the schema dialog and specifies the level of detail. The value 0 stands for the first entry "Default", 1 for "Fine", 2 for "Maximum". More information 'Command Line Call: CAD'

The waveware clients can now also communicate via HTTP1.1. This facilitates working with firewalls and reverse proxies that do not have HTTP/2 support.

The use of HTTP1.1 can be enforced using a prefix in the server address. More information on using prefixes: 'waveware Server: Connection Establishment'.

Moving appointments means that an existing appointment is assigned to a different calendar group or calendar. It is checked beforehand whether the record may be reassigned.

The behavior for assessing whether an appointment can be moved can now be adjusted in the new rule trigger 'CanMoveAppointment'.

In Mobile Device Management (MDM) that support configuration policies for applications (Managed App Configurations), you can set specifications for waveware Mobile.

Configuration policies can now be extended with new key-value pairs that further define login preferences. More information under 'Preset Login Data Using MDM'.

In addition to good password complexity, changing passwords regularly is an important part of ensuring data security. The password change is therefore now also possible in waveware Mobile.

You can now change your password at any time via the main menu of the waveware Mobile Client (menu item 'Change Password').

The use of biometric information for logging in (Face ID or Touch ID) secures the "Remember me" function and thus enables the app to be started quickly and securely.

As of 11.200.2965.37, the use of the 'OnOffBiometricLogin' and 'IsActivatedBiometricLogin' building blocks is possible to secure the saving of the login with biometric information. The function is now integrated directly into the waveware Mobile main menu. Setup using a custom rule is no longer required. Further information on the application under 'Login with Biometric Data'.

In Document Management in the waveware Windows and Web Client, the symbol of a pin shows whether documents have been assigned to a record.

In the Mobile Client, a small pin is now also displayed on the 'Documents' button of an open object if documents have been assigned to the object.

The SAP Connector for Microsoft .NET is required to use an interface to SAP.

Version 3.1 of the SAP Connector for Microsoft .NET is now being delivered. See system requirements for information here.

This release no longer supports a direct update from an 11.170. The version being updated from must be at least an 11.180.

If you still want to update from an earlier version to the current release, you can do this step by step using one or more intermediate versions. Please note the information in the FAQ 'Update Process, Update Order'.

When creating serial appointments via Multi, the number of days was not set correctly. This bug only affected Multi. The serial dialog in the cards correctly calculated the number.

After importing test data (e.g. with ETC files) in the waveware Windows Client and then importing test data again via the waveware Web Client, it could happen that the import in the Web Client aborted without an error message.

When editing the package properties in the System Rule Editor, changes to Supervisor Options could not be saved if an option was created with the 'KeyValuePairListEditor'. In this case, an error message appeared, which erroneously indicated a missing name, although all fields were filled.

An error occurred when publishing rules in the System Rule Editor that contained types only from the server.

Sub-transactions could be entered but not saved via the 'Save' button, only via exiting the card.

In some cases, the CAD viewer could not be loaded correctly in the Web Client.

Searching with only the placeholder asterisk "*" was no longer possible in Custom Pages. However, placeholder searches with "**", "a*", "*b" etc. worked.

The 'OpenLocalMailClient' building block did not open the local email client and returned false, even though a local email client was installed.

Fixed: The local email client is called using an additional .NET 4.8 program. Please note that the .NET Framework 4.8 must be installed when using this building block.

An area may not have been filled with the correct parent room data when using the wraparound scheme.

In the list of room stamps, the entry for the currently displayed stamp remained empty, but the entry was present in the drop-down list.

Transaction lists: Sub-transactions can be displayed as a card and in a list (table view). This is now also possible with transactions.

Transaction lists are set up in the Designer and in the Supervisor Options and are then available for appropriate transactions for better overview and quick data entry.

In some cases, rules that were edited or created in the System Rule Editor could not be published correctly in order to use them in waveware clients. In this case, the waveware server had to be restarted in order to enable the rule.

The authentication using MSAL did not work in the waveware Web Client if single clients (single client in Microsoft Azure) were used. In this case, the data transfer was not error-free.

When starting waveware Mobile, e.g. a delay can be set so that automatic VPN connections can be established in the background before the app connects to the waveware server. However, pre-configurations of waveware ('InstantLogin', 'InstantLoginDelay' and 'SplashScreen') were not executed correctly.

The Customizer management in DataManagement has been redesigned and is now available in the same place as a user management.

As usual, customizers for DataManagement can be created in the user management, customizers can be logged off and debugging processes can be interrupted.

What is new is that the DataManagement administrator is also managed here and no longer under 'waveware Server'.

The 'Recent' (1897)  system package caused problems in the ChangeRange, which could result in erroneous scenarios in various processes. For this reason, among other things, the 'GetAllUtransRecords' building block did not work correctly. Under certain circumstances, this no longer supplied any data.
As a workaround, the "1897.Card.Entered" rule could be completely deactivated.

The 'List & Label' reporting tool has been updated to the current version 28.

The creation and processing of print forms is implemented in waveware using the extensive reporting tool 'List & Label' from combit®. In order to integrate current developments into waveware and to achieve full support of Windows 11, List & Label was updated from version 27 SP1 to the latest version 28.

The existing selection filters for all determined tables of an export are queried and displayed in the 'Available filters' area. This can be used to determine which records are to be exported.

In order to improve clarity and performance when loading the available filters, filters are only displayed for new export directives after the relevant selection types have been selected. The 'Available filters' window is therefore initially empty with such export specification. Click on the new 'Choose selection types to display' button to activate the required selection types. The filters for the selected types are then offered. For more information see 'Export: Available Filters'.

In Multi 'Further actions' you can provide your own multi rules specifically intended for a specific application. By default, the description of the executable data rule is used in waveware clients, which, however, is intended for application developers in the System Rule Editor and could possibly be formulated too technically.

Comments can be stored in backups and transport orders.

When creating backups and transport orders via DataManagement, you can now enter any comments that describe the data status of backups in more detail, for instance. These comments will be displayed again before importing them later.

Bar/QR codes play a key role in the mobile recording of objects or in inventorying. With the help of the camera, which is integrated in many mobile end devices, these codes can be scanned without any additional equipment.

In very dark environments, the camera of mobile devices could only be used to a limited extent when scanning bar/QR codes. With the new 'OnOffFlash' building block you can now switch on the camera light/flashlight of the mobile device in a corresponding rule in the System Rule Editor.

Warnings about wrong field types during package import, were not displayed correctly in DataManagement (area 'All Messages') and also not fully output in the HTML log file.

If the calendar is opened in the mobile client from any object, all available transactions of the object are displayed in the dropdown. Then if you changed to the transactions 'Appointments' and opened the calendar here again, all available transaction types were offered again and not just the opened transaction type (in this case 'Appointments') and its sub-transactions.

Fixed: When opening the calendar from a specific transaction card, only records of the opened transaction type and its sub-transaction are displayed.

Changed client IDs were not taken into account in a package update with data (dump) in client versions. This was noticed during a package installation from the ticket system. This delivers the 'Ticket status' table with several status values, which are assigned to the client with ID 1 in the standard system. After installation, the 'Ticket Status' table was set up to be available globally/across clients (client identifiers of data rows changed to 0). In a subsequent package update, the client IDs were reset to 1. The package update therefore did not take into account the individual setup.

Fixed: When activating the data world, it is checked again whether the data is in the correct client.

In the Rights Management, it was possible to withdraw the role 'Supervisor' from the user Supervisor. This allowed the supervisor to be excluded from waveware. It was no longer possible to log on and the message "Access to the data of this client is not allowed!" appeared.

The 'SFtpConnection' building block can be used to establish an SFTP connection. So far, no port deviating from the standard could be specified.

Changed client IDs are not taken into account for package updates with data (dump) in client versions.
This was noticed during a package installation from the ticket system. This delivers the 'Ticket Status' table with several status values, which are assigned to the client with ID 1 in the standard system. After installation, the 'Ticket Status' table was set up to be available globally/across clients (client identifiers of data rows changed to 0). With a subsequent package update, the client IDs were reset to 1. The package update therefore did not take into account the individual setup.

When activating the data world, from one of the next versions it will be checked again whether the data is in the right client. This will fix this bug in one of the next versions.

Selection - Monitor list with grouping: Switch type of grouping

Data from a selection can be displayed in a grouped list. This is always a list with grouped columns first. The type of grouping view can now be switched to a detail view here.

The use of biometric information for login (Face ID or Touch ID) saves the repeated entry of a user name and password when opening and thus enables the app to be started quickly.

To set up the login with biometric data system-wide, use the 'OnOffBiometricLogin' and 'IsActivatedBiometricLogin' building blocks. In any mobile rule, this form of login must be activated once with the 'OnOffBiometricLogin' building block, e.g. after pressing a custom button. Then log in once in waveware Mobile, activate the option 'Remember me' when logging in and tap on the custom button set up beforehand. Authorization is obtained by scanning Touch ID or Face ID once. Then you can log in via Face ID or Touch ID.

Swipe gestures make it easier to use apps. In waveware Mobile, dialogs can now be created for example to show websites or text content, and can be scrolled through with a swipe gesture. In this way you can integrate your company's news into waveware Mobile and distribute it easily.

In waveware Mobile, the new swipe gesture dialog can be integrated into the general workflow by rule. You need three new building blocks for this:
'ShowSwipeDialog': Shows a new dialog with a submitted set of pages. The pages can be scrolled through with a swipe gesture. The respective page content can be created by rule or be a website.
'SwipeDialogPage': Creates a new page in the dialog with title, header, images and texts.
'SwipeDialogWebpage': Creates a new page in the dialog, where the page content is a web page.

Field rights allow restrictions on rights for certain fields in a table. The field rights set up are now also taken into account in CustomPages.

Field rights are only applied to controls in CustomPages where it is by definition possible. This affects the following: 'FieldName', 'LhFieldLabel', 'LhFieldContent', 'LhCatalogFieldContent', 'LhMultiSelect', 'LhMultiTableControl', 'LhTableFieldContent', 'LhTableContent', 'LhTransTableContent', 'LhUTransTableContent' and 'RecordValue'.
In addition, field rights are only checked if data is retrieved or requested from the control. If data is retrieved via a rule (e.g. using 'GetGridDataSource' in conjunction with 'customSelect'), the field rights in the server rules must be validated. When saving via the CustomPages, the validation must also take place in the corresponding server rule. This is because field rights do not apply to server-side rules.

Documents in the waveware document management can be indexed with tags. With the help of the Supervisor Option ('DMS tag assignment when linking'), the assignment of tags can be made mandatory directly when uploading or linking new documents. It can sometimes happen that not all tags can be assigned to a document.

In this case you can use the new rule trigger 'GetTagsForAssignment' to specify which tags should be available when linking/uploading a document. If such rule exists, it must return all tags that are to be offered in the dialog. Any logic can be implemented, so that filtering is also possible in this way. If the rule does not exist, the previous default behavior, which shows all tags, applies.

For access to various email servers, e.g. from Microsoft Azure/Office365, authentication with a user name and password (basic authentication) may no longer be sufficient. Another/additional method (OAuth – Open Authentication) is required here in order to successfully authenticate on the server.

Building blocks that retrieve or send emails to waveware (establish an IMAP, POP or SMTP connection) usually go back to the central settings in the Supervisor Options (system / waveware / mail options). Here for example, the client ID created in Microsoft Azure and the associated client ID are stored so that authentication is guaranteed system-wide.

The internal table column 'G' is part of every waveware standard table and contains the unique ID of the record. The value in the 'G' column is unique worldwide thanks to the use of a so-called GUID. This offers particular advantages when exchanging data between waveware systems, especially when importing and exporting.
Up to waveware 11.180 version , the 'G' column was protected from double entries by a unique constraint. This restriction has prevented the easy import of data of one client into another client.
Due to an error, this restriction was removed in version 11.180 and no longer referred to column 'G' alone, but to columns 'G' and 'M' (internal client ID) together. This only enforced that records within a client had to have a unique ID in the 'G' column. It is currently possible to import a client into another client.
Only installations that work with multiple clients are affected. Updates from 11.170 to 11.180 and newer are generally unproblematic, since double IDs in the 'G' column could only occur if changes were made directly to the database or with unforeseen actions, such as importing a client into another client.

Since this state can be problematic for various data structures, the 'G' column is made unique again by error correction.
If there are duplicate entries in table column 'G', there is a system update step that assigns new values ​​for duplicate entries and also takes the dependencies (transactions and sub-transactions) into account.

Changed client IDs are not taken into account for package updates with data (dump) in client versions.
This was noticed during a package installation from the ticket system. This delivers the 'Ticket Status' table with several status values, which are assigned to the client with ID 1 in the standard system. After installation, the 'Ticket Status' table was set up to be available globally/across clients (client identifiers of data rows changed to 0). With a subsequent package update, the client IDs were reset to 1. The package update therefore did not take into account the individual setup.

When activating the data world, from one of the next versions it will be checked again whether the data is in the right client. This will fix this bug in one of the next versions.

When creating a new transaction on IOS it can happen that the area where a new sub-transaction can be filled is not expanded.

The error can be avoided by selecting the new, non-expandable sub-transaction in the app, deleting it (action button 'Delete') and creating it again (plus button). An empty template of the sub-transaction ment is then created, ready to be filled out and saved.
Will be fixed in the next release.

The 'Deleting' and 'Deleted' triggers are now also available for sub-transactions.

A field can now be specified via the "DisplayedDocumentName" field tag on table 86 (document), the content of which contains a name for a document in the DMS. The field tag applies to all documents, not just URLs.

Tags are used in waveware to categorize records with simple terms. The tags can be now also used in the Mobile Client.

When outputting a selection with list option 'Output format' = "All in one cell" to Microsoft Excel or a CSV file, several pieces of information were previously written into one cell separated by a comma.

With the help of the system function 'Notifications' system function you can easily be informed about data changes. As of 11.200.821.31, a new notification can be created/triggered using rules via the System Rule Editor. As of 11.200.1652.30 there is a process to create triggers for notifications of any table without having to create rules yourself.

In many cases, however, this optional process is not required since only system notifications are to be received from packages or rules, so this process has been transferred to the 'Notification Assist' (1890) package. Therefore, to create custom notification triggers via Assist, the 'Notification Assist' (1890) package is now required.

A placeholder dialog appears when executing all selections that use placeholders in filters. In this way, variable values ​​can be entered by the user before a selection is made. When entering the filter terms, the context menu was missing, that provides options to copy, paste, cut, etc.

A crash could occur when loading a drawing and reading in layer groups with duplicated name entries.

Global dashboards that were hidden at the start (tool window option 'Hide') and only activated via the waveware status bar could no longer be opened by the person who created them. This problem occurred from waveware 11.200.1652 and usually only affected people who created the dashboard themselves.

When using operations, it could happen that when deleting an object and its transactions, not all related operation transactions were also deleted. If an object was created again later with the same ID, it could happen that these operation transactions were visible on the new object.

When updating from an 11.180 or 11.190, the operators of all restrictions were changed to "=", which could lead to unexpected behavior.

Under certain circumstances, IronRuby was not installed correctly when installing the waveware server. When using the corresponding building blocks, the error message "An error occurred when running the building block - the system cannot find the specified file" appeared. The reason was that the IronRuby files were missing in the waveware server directory.

Dashboards that displayed correctly in earlier versions may not return the expected results in version 11.200.2706.36. For example, bar/line charts with series representing different measures with identical index in bar sections or in different line shapes showed incorrect visualizations.

In many tables, the internal column 'G' accepts an ID (so-called GUID) which, together with the client information (internal column 'M'), uniquely identifies a record. Records can therefore be uniquely identified within a client with this ID. In connection with a bug fix, waveware 11.200.2706.36 only specified a uniqueness check (index) for the 'G' column.

The index was removed again from 11.200.2706.40, so that the ID in the 'G' column still only has to be unique within one client.

With the help of notifications, you receive short notifications for any actions directly "in-app" in every waveware client.
Push notifications will be soon available for the Mobile Client, which display waveware notifications directly on Android or iOS.

The functionality is in the beta/test stage. If you would like to test the functionality in advance, contact your system partner. You will receive a token that you will need to set it up. However, make sure that you do not transmit any GDPR-relevant data via push notifications.

Listings of tags used in selections are not yet displayed in the Mobile Client. If, for example, a selection is opened that is to list tags for devices in Mobile Client, the cell for the tags remains empty in the selection result.

Will be fixed in the next release.

Universal selections enable selections for transactions across all object types. There is now a new section 'All objects and catalogs' for universal selections in the list of available tables and fields for selection filters and lists. Here all fields are offered that have the same field ID and the same field type in the related higher-level tables of a transaction type and are activated for selection.

The fields contained in 'All Objects and Catalogs' can be used both in the selection filter and in the list. If an offered field has the same catalog stored in all higher-level tables, the catalog support or 'auto-complete' function is activated when entering the field value in the selection filter. If the field provided has the same name in all higher-level tables, the name is also used as the column header in the output, otherwise the field names are lined up. However, aggregations are not allowed for these fields because they are selected by sub-query with 'UNION' when executing the selection.

When creating a notification, you can now differentiate between a personal and general notification.

Only the person who was explicitly specified when creating the notification trigger or the person who created it receives a personal notification. Several people can receive a general notification at the same time. In order for a person to be able to create corresponding notification triggers, they need one of the following roles, which you must create in advance via rights management and assign to the person: "NOTIFICATIONS_Admin" (access to the creation of personal and general notification triggers; creation of personal notification triggers for other people) or "NOTIFICATIONS_Personal" (Person can only create notification triggers for themselves). For more information, see: 'Notifications: Create or Customize Triggers'.

If a column of type 'uniqueidentifier' was empty, it still had the content "00000". This was not identified as "empty" but as "filled".

The DatabaseGenerator has been adjusted so that empty GUID fields are also correctly recognized and removed when activating a data world. This applies to both MSSQL and SQLite. The "PROCG" column has been removed from the table 'T_TRANS_LINK' and all references to it. A unit test has also been added, which creates a GUID column in the database and fills it with data to check whether the column is removed correctly.

The design of the print output (email, printer, etc.) is defined via print forms. The handling of the forms in the print dialog has been improved. In addition, building blocks relating to printing have been restructured in the System Rule Editor and categorized/grouped according to their intended use.

Print forms that are created for an object type vor example, can now be filtered by form type in preparation for Telerik Reporting (see announcement below) for a better overview. You can also call up further information on a form via the print dialog (button 'Display/edit form details').

Drawn fields enable read-only display of any value, e.g. via rules. It was no longer possible to copy these field values ​​to the clipboard.

Client groups allow for a summary of all records from the clients that belong to the group. The list of available client groups may not have been updated correctly, e.g. after changing the active client.

In the Mobile Client, fields can be grouped in areas that can be opened and closed in order to display large cards as compactly as possible. If several such areas were set up on a card via the Designer (property 'Collapsed?'), only the last of the card could be expanded in the Mobile Client. Other areas could not be opened.

The print functionality will be expanded to include Telerik Reporting in one of the next release versions. If activated via the Supervisor Options, the new form type is available in print dialogs.

This new function can already be used now. However, it is a preliminary version in which not all components are available (including the localization of the interface and the associated documentation).

With the help of the system function 'Notification' you can easily be informed about data changes. In this way, you always have an eye on updates of important elements and reduce response time.
A notification can be sent to a person or to an entire group of people (role, Staff Functional Group). You always have an overview of your personal notifications via the new tool window 'Notifications', which is structured almost identically in the waveware Windows, Web and Mobile Clients.

As of 11.200.821.31, a new notification can be created/triggered using rules via the System Rule Editor.
In addition, there is now a process to create notification triggers from any table without having to create rules yourself. For this purpose, the 'Notification triggers' catalog provides a wizard that guides you through the setup step by step.
See 'Notifications' for more information on how to set up and use it.

An update of the data world is no longer mandatory in the future if a new version has been installed that differs from the previous version only in the last digit (so-called 'build'/'revision'): e.g. from version 11.200.1652.25 to 11.200.1652.30.

Such update will appear when the data world has been disabled. Since it is not mandatory, the data world can also be started without performing the update. If the version differs in one of the preceding digits (e.g. so-called 'Major' and/or 'Minor'), the data world must be updated before activation.

Drawn Fields

Drawn or painted fields provide a quick way to output read-only data for rules or any other card functions.
The assignment of the field IDs of painted fields has been adjusted. The IDs from 13000 to 13499 are released for user-defined creations in customer data worlds. The range 13500 to 13999 is reserved for packages. Such IDs (13500 to 13999) must be registered in the future.

In the past, various misbehaviors occurred due to overlapping field IDs of drawn fields. Therefore, please only use fields from the free ID range (13000 to 13499) on your cards and in customer packages. Packages released by Loy & Hutz and partners do not use this area, so there can be no overlap.

Which fields from the object type 'Staff' are to be displayed in the rights management can optionally be set using the "showinrightsmanagement" field tag. Important internal fields 'Staff ID' and 'Login name' were then hidden.

The fields 'Staff ID' and 'Login name' are internal fields, which is why you cannot set the field tag for these fields. As a result, these two fields were not displayed with optional field arrangement. The fields are now always displayed even with optional field arrangement, without having to mark them with the field tag.

Special characters and umlauts in a string field were not saved correctly in forms with file upload. Question marks were saved for these characters instead.

Although no external changes were made to a data world, the message "The data world was changed outside of waveware..." may appear after various actions in the data world management.

Corrected so that the message only appears if the data directory was not created by waveware or was changed manually.

The last positions of the opened cards are saved personally via layouts ('Open last view again when program starts'). If the person's table rights for one of the saved cards were subsequently withdrawn, the result was a crash when the waveware client was started.

The 'Structure List' navigator view could not be updated manually ('Refresh' button in case of disabled synchronization). Data was retrieved but was not displayed correctly when the window was continuously open.

If the pattern in the series definition of an existing series appointment was changed to a weekly one, it was possible that no valid appointments could be determined from the settings. A message pointed this out.

Fixed so that the pattern can be modified successfully.

Creating notification triggers via the new 'Create trigger' wizard does not work correctly for transactions. Notifications may not be generated when such a trigger occurs.

The problem will be fixed in the next release.

For this purpose, a new control 'LhTagSelection' was added, which creates a tag selection. The 'LhFileUpload' control has been extended by the following hash attributes (with hash attributes it is possible to pass HTML tags or special properties):
ShowInactiveTags (show inactive tags), MaxTagCount (max. number of selectable tag entries), EnableOptionalTagSelection (enable optional tag selection), TagSelectionLabel (set identifier).

A cleanup function is now available in DataManagement under 'Miscellaneous' that deletes such erroneous  records.

There is now a new field 'Series Type', to which the 'Series Types' catalog is stored. This enables better filter options in the selection. For existing serial appointments, a record can be automatically created in the 'Serial Appointments' catalog and the catalog field can be filled using a tools function.
For new appointments, a 'Series type' can first be selected on the card. This is then used as a template when opening the series definition window.
In addition, new multi-functions through new multi-rules for changing certain properties of appointment series, e.g. interval, validity, series start/series end, appointment view.

In practice, when you create appointments, you usually want the first appointment to be prompt. Therefore, the default setting is changed here to "This year" or "This month".

Since a new sub-transaction cannot be created in such situation, the button has been disabled.

Tags are used in many areas to categorize items with simple terms. This form of categorization is now also used in waveware for assigning and grouping any  records (object, catalog, transaction, sub-transaction) to freely definable keywords.

You can create and assign tags to any record intuitively using the new 'Tags' tool window, which you can display for each open card. Visualize tags or symbolize priorities using colors, which you can specify from the Tags gallery. You can also structure tags hierarchically to clearly define tag affiliations. In this way, a tree structure of a categorization is created, which you can use to easily evaluate the selection or search, for instance.
The 'Tags' functionality is directly applicable. See 'Tags' for more information.

Roles are used in the rights management of waveware to assign permissions, restrictions, client rights, etc. to persons. Until now, the purpose of a role could only be understood with the help of an appropriate name.

Notes can now be stored for all roles, e.g. to describe their use in more detail. There is a new column 'Description' in the list of roles for this purpose.

A record filtering can be set up at the 'FilterObjectRule' parameter of the 'ShowObjectSelectorDialog' building block using an expression. Any custom arguments can now be passed to this expression. There is a new 'FilterObjectRuleArguments' input on the building block for this purpose, which accepts a list of key-value pairs. These can easily be evaluated in the expression at 'SearchFilterArguments'. More information under 'ShowObjectSelectorDialog'.

The assignment of color and pattern in a selection used to be somewhat confusing.

A new, clear solution that is based on the interface of the filter and list compilation. To select the field, another window is opened in which you can easily open and close levels and filter by fields.

Web content is displayed in waveware Windows Clients using a browser control. Previously, you could choose between IE (Internet Explorer) and Chrome in the settings of the waveware server. Both components are now being replaced by WebView2, the Microsoft Edge Control.

Unlike the Chrome Control, the WebView2 Browser Control receives updates via the Windows update function, which ensures that the control always meets the current security criteria without any further effort for update. In addition, the WebView2 control improves performance, provides a way to run downloads directly and enables developer tools to be called up directly, e.g. to simplify debugging during package development. Since Microsoft Edge uses the Chrome Engine internally, all current web technologies will continue to be supported.
The 'WebView2 Runtime x64' is required before installing the current waveware Windows Clients (waveware FAT Client and DataManagement).

Keywording plays a major role in document management. The new tags can be therefore applied to documents, for example, to replace the fields 'Category 1' to 'Category 3'.

The 'Tags' functionality provides the option of assigning keywords to documents in order to make it easier to search for specific files later or to enable a grouping (tree view) of the documents. Until now, indexing and grouping was mostly done using the 'Category' fields in the 'Document' object.
During an update, tags are automatically created from the entries in the 'Category 1' to 'Category 3' fields and assigned to the respective documents. If you have a very large document library, allocate time for the update. The field entries remain after the update and can be used further with the help of the compatibility mode, in case you use them in your own rules. In a new installation, the 'Category' fields are no longer included.
See 'Document Management: Tags' for more information.

The 'Update status' filter function in the DataManagement package manager had no effect on the result. For example,  "Only Updates" filtering will continue to include all packages.

Selections can also be called up directly via rules, e.g. using a 'CustomButton' that is placed in the waveware ribbon. If a selection called up in this way contained filters with placeholders, no dialogs were displayed that asked the user for filter criteria. Required filter criteria were only queried when executing the selection via the selection of waveware.

Fixed so that dialogs for determining filter criteria appear now also when the selection is made using rules.

Fields of field type 'Boolean' are displayed on CustomPages using checkboxes. There was a display error here: the checkbox was displayed twice.

In the field properties of a selection list, optional column headers can be set up for fields that are used instead of the field name. These column headers were changed in the Mobile Client, when defining user-defined filters on a selection result, not taken into account, so that only the field names were displayed there.

Tasks for an appointment list can be created via Multi (Multi - 'More actions' - 'Create Tasks from Appointment List'). This could lead to errors if the generated tasks contained sub-transactions (e.g. internal or external tasks). The sub-transactions were stored correctly for the first 100 tasks. The number of sub-transactions then doubled every 50 records (>100: 2 sub-transactions, >150: 4 sub-transactions, >200: 8 sub-transactions, etc.).

Among other things, availability is made available only to certain people or roles in the selections, lists, filters and outputs. Inactive people were displayed as a blank line.

Fixed so that empty rows are no longer displayed.

With the help of the system function 'Notification' you can be informed about data changes from one of the next releases. In this way, you always have an overview of  updates of important elements and reduce response time.

Building blocks and triggers for creating and using the notifications have already been implemented in this version. The integration of the system package, which provides a user interface and integrates the necessary processes into waveware, will take place in a later version.

When adding fields as a filter criterion or as part of a selection list, the first level of all available fields is shown first. Previously, you could expand nodes individually or expand them all.

In addition to the filter field, there is now a new input field in which the number of levels can be specified, that should be taken into account when expanding the nodes. In addition, levels can be expanded and collapsed individually using the '+' and '-' buttons.

Filter / List: You can enter a filter term above the available tables and fields in the field 'Filter displayed fields'.

Fields that match the entered filter term are now displayed in bold. This improves the overview of the matches.

The selection list controls the display of fields in selections. In the case of a field whose catalog is static (the so-called DEF catalog), only the catalog terms could previously be output in a selection.

In a selection list displaying a DEF catalog field (e.g. 'Status'), it is possible to display the item icon instead of the term. To do this, only the field option 'Output type' = "Icon" must be set in the selection list. The 'Sort type' = "Icon" can also be specified.
Note that DEF Catalog terms must be previously iconized via the Designer to use this feature.

The current waveware versions can now be downloaded from the waveware Service Center.

You can now download the released waveware versions from the waveware Service Center. All you need is a valid user account, which you can set up yourself in a few steps if you don't already have one: 'waveware Service Center: Registration'. The new menu item 'waveware Download' is displayed in the 'Technical Support' area of ​​the Service Center.

The 'List & Label' reporting tool has been updated to the current version 27 SP1.

The creation and processing of print forms is implemented in waveware using the extensive reporting tool 'List & Label' from combit® company. List & Label has been updated from version 26 SP3 to the latest version 27 SP1 in order to integrate current developments into waveware and to fix a critical error with nested project templates that led to an application crash.

Size, position and arrangement of document and tool windows are managed in waveware via workspaces/layouts. It is now also possible to create a new custom view if 'Reopen last view on program start' is activated.

By default, the last states of all windows are restored, as they were set before waveware was exited. This ensures the option 'Reopen last view on program start' in the 'Workspaces' dialog. Previously, a custom view could only be created if you had previously switched to the 'Custom View' option in the dialog. If a saved view already existed, it was loaded and displayed directly. Window positions that you may have wanted to save were thus overwritten.
Now you can also create a new custom view if the option 'Reopen last view on program start' is set. This allows you to back up the current workspace at any time without the risk of overwriting it first.

The 'Basics.Record.CreateUTransRecordSuccessor' building block, which should create and link a new sub-transaction, was not working as intended. In addition, the use has a negative effect on the performance of various processes such as Offline/Sync.

If a path to a transport order(*.ztransaction) was selected within the data world administration in DataManagement, a network error occurred during the check and the DataManagement crashed.

If the Mobile Client was reinstalled and client ID 0 was then used when logging in, the message "Session has already expired. waveware will now be closed." appeared.

Fields with specific values ​​can be highlighted using coloring. Changing the color of a field always required a refresh of the record list in the Mobile Client to reflect the changed color.

After installing a package that brought new tables, these were only displayed in the Supervisor Options once the waveware server had been restarted. For example, no status terms could be set for new transaction tables.

Fixed: Tables are correctly listed again in the Supervisor Options after package installation without having to restart the waveware server.

The 'IsDevelopmentSystem' building block, which is required to record in a rule whether it is a development system, only worked within the scope of the waveware Server or DataManagement.

Fixed so that it can also be used in client rules.

Starting with this version, Microsoft .NET 6.0 is used internally in waveware. When installing or updating the waveware server and the clients, the required components of the .NET Framework will be automatically installed in the future. Even with ClickOnce installations, the .NET no longer has to be installed manually in advance.

With the Assist, you can ensure that users successfully complete all relevant steps of a process. The new system function is available from 11.200 for the waveware Windows, Web and Mobile Clients. The Assist is gradually being added to many standard packages and can also be used at any time in your own solutions, controlled via the customer package (1), for instance.

In the Designer context menu, you have the option of copying one or more properties to the clipboard for documentation purposes. This is now possible in particular for (grayed out) properties that may only be read, and also for all properties of an element selected in the Designer at once: 'Copy Properties to Clipboard'.

The Mobile Client GRPC communication can now take place via a proxy server. In order to use a proxy server, it must be activated in the system settings of the smartphone. This setting can usually be found in the WLAN settings of the end device.

Log entries are stored in a consistent format in the new system package. A classification of the entries into levels defines the importance (0 = high importance/serious error - 4 = lowest importance/information). The structure is like a tree structure: the higher the set level, the more detailed the log becomes. A new protocol is set up and the recorded protocol entries are evaluated directly via the waveware Client. More information: Documentation on 'Logging' (1833)

The dialog is no longer required and has been removed because single sign-on on the web and custom pages is no longer possible and has been switched to MSAL or SAML. More in the Single Sign-On (SSO) section.

The selection tables T_SELECTION, T_SELECTION_FILTERSET, T_SELECTION_FIELDSET, T_SELECTION_OUTPUTSET now have the columns CRTIMESTAMP, TIMESTEMP, USERNAME and these are filled when saving:
CRTIMESTAMP (only when creating a new component): DateTimeUtc of the saving process
TIMESTEMP: DateTimeUtc of the save operation
USERNAME: Name of the logged in user

waveware Server, waveware Windows Client and DataManagement can no longer be run on x86/32-bit operating systems. Only the CAD-DWG and CAD-DGN import client are still delivered as a 32-bit version for technical reasons.
Please note that the ClickOnce links have also changed for this reason. 64-bit installations of the ClickOnce client also require a reinstallation of the client after the waveware server has been updated.

IronRuby support will be phased out over a two-year period. This means that support is still given until around mid-2023.
With the current version, waveware receives IronPython support in return. Please convert all update scripts and ERB pages to IronPython within two years.

This release changes the behavior of system and user rules. For a user with the license right 'Package development', it was always the case that no user rules were executed. This is no longer the case: user rules are executed and system rules can be edited. Execution behaves in exactly the same way as without the license right of 'Package development'.

Until now, a WCF service was used in waveware for this purpose. As of Microsoft .NET 6.0, which is used from waveware 11.200, no longer supports WCF services, the previous standard procedure for Single Sign-On in the waveware Windows Client and on the Web/CustomPages must be replaced by Single Sign-On via MSAL (Microsoft Authentication Library - Microsoft authentication library) or SAML (Security Assertion Markup Language - XML ​​framework for exchanging authentication information). Both methods have been integrated in waveware for a long time and offer the advantage that they can be used not only for the waveware Windows Client, but also for Mobile and Web Clients. This way you can use a single SSO standard for all platforms.
More information at 'Single Sign-On with SAML' or 'Single Sign-On with MSAL'.

Operations have been improved in terms of performance and clarity. If for example, a transaction or object is opened via the object or transaction search, the appropriate entry is now marked under 'Operations'. Since the search with a large number of operation transactions resulted in longer loading times, the search has been optimized so that only the important first level of the building structure is searched. In addition, operations can now be viewed page by page. At the bottom of the window there are buttons for scrolling. The number of entries in a page can be set in the Supervisor Options.

Since waveware depends on support from Microsoft or .NET 6.0 in order to be able to offer a corresponding integration of web services, we unfortunately have to stop supporting SOAP/WSDL as well. The support of REST interfaces is still guaranteed. Packages that include WSDL or provide rules in the "Webservice" folder are affected. It is recommended to switch the previous WSDL interfaces to REST interfaces if possible.

New waveware installations will soon be able to run with a PostgreSQL database. The function is already supplied here, but will only be fully functional with next release.