11.210: Technical Changes

In the Designer, fields of the field type 'MultiSelect' can now be created and placed on a card.

MultiSelect fields allow multiple entries to be selected in a single field. The primary purpose of MultiSelect fields is to automatically create or delete sub-transactions from transactions. If necessary, custom entries can also be used in MultiSelect fields.

GraphQL is an open-source language for data query and manipulation. It offers an efficient and flexible alternative to SQL, in the spirit of REST and ad-hoc web service architectures.

GraphQL support is enabled via the waveware server settings and can be used after restarting the service. To get started with GraphQL, you need a waveware server endpoint and a valid authentication token. Further information and examples can be found under 'Interface: GraphQL'.

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

The creation and editing of print forms in waveware is carried out using the comprehensive reporting tool 'List & Label' from combit®. The tool has been updated.

An automatic list export can be configured for selections. However, the automatic export was not executed if the beat rule was not executed exactly at the scheduled export time.

When creating new transactions directly in the table view, the Windows Client could crash if the name field (11) is a def catalog.

With very dark design settings, certain test device management dialogs in the Windows Client were difficult to read.

Using waveware Mobile 2, photos can be taken and saved directly in 'Image' fields. On some devices, the captured photos were saved rotated 90°.

SYNC is used to synchronize mobile data with the Main Station. The status is displayed via a progress bar. The window appears, but the progress bar was not updated. This was due to a display error in the waveware Windows Client. The synchronization took place in the background, and completion was acknowledged with a message.

The 'Stay signed in' option, which can be activated when logging in to waveware MOBILE 2, did not work for Offline Data Worlds. An error message appeared when logging in with this option.

The window for editing work steps could not be accessed in the waveware Web Client. Changing field contents was not possible. The window could only be closed using the Close button.

Display rules were previously called every time when a field switches, a field changes, an area changes, navigating between an object and a transaction, and a record changes.

Now only the selected tab is updated.

Main page tabs could not be opened in Custom Pages.

The building block 'MergeMultiplePrintFiles' did not work as expected when passing form names.

Opening the print dialog during a running debug session in DataManagement caused the Windows client to crash.

During a CSV import, it could happen that the data loading could not be completed.

People assigned roles with certain restrictions (on remote catalog fields checked with the dynamic filter 'User Function') could not log in.

With the help of SYNC, mobile databases are synchronized with the Main Station. The status is displayed via a progress bar. The window appears but the progress bar does not update. This is simply a display error in the waveware Windows Client. The synchronization takes place in the background and the completion is acknowledged with a message.

The 'Stay logged in' option, which can be activated when logging in to waveware MOBILE 2, does not work in Offline Data Worlds. An error message appears when logging in with this option.

Mass data changes can be carried out using multi-actions. The action 'Change field contents' makes it possible, for example: to change the content of a field in all (or specific) records of an object type. When setting the input field to be changed, incorrect selection and thus accidental changes to catalog terms could occur, as fields from nested catalogs were also offered.

When selecting the input field, no fields that belong to a catalog that lies behind another field are now displayed by default. This measure is for security purposes to prevent accidental changes to catalog entries. To also display such fields, the 'Show nested catalog fields' checkbox can be activated, which is located next to the input field selection.

When adding new documents to the DMS, a Supervisor Option can be used to specify that tags must be assigned to the document. If the 'Create link to DMS' property was activated when printing cards, there was previously no corresponding option to assign tags to this document when adding it.

The DMS tag assignment behavior can now be configured for card printing via the Supervisor Option "System / System (0) / waveware / Print Options / Document link". By default, no tag selection is displayed, but can be changed to "According to the DMS-SVO", "Show (Tag selection is optional)" or "Show (Tag selection is mandatory)" ('Print: Document Link').

If notifications had very long texts, they could not be read completely in waveware MOBILE 2 because they were cut off.

If you now long-tap on the notification, a small window will open showing the full title and content of the notification.

A button in the search line of the list starts a dialog in which a sorting can be specified for sortable fields using arrow buttons (waveware MOBILE 2: Transactions and Sub-Transactions).

The behavior after exiting edit mode in MOBILE 2 can be set via a Supervisor Option.

Depending on the type of editing (changing an existing record or creating a new record), you can set whether the previous page or the edited record should be displayed in view mode (waveware MOBILE 2: Customize Behavior after Editing/Creation).

Empty fields that appear by default on cards in view mode can now be hidden.

If the Supervisor Option "System / System (0) / Mobile / Cards / Hide empty fields in view mode" is activated, empty fields are invisible in view mode of a card.

QR codes can be scanned with the device's camera, when logging in, determining the object ID/object search, filling out fields, etc. If the code was very small, detailed, or generally difficult to read, detection was not always successful. The detection accuracy can now be adjusted.

Detection can be switched to 'Detailed' during scanning to improve accuracy. Scanning will then take a little longer. The last selected setting is saved. To save time, you should switch back to 'Standard' for easily readable QR codes.

From this version onwards, the 'RubyErbApi' and the functions from the 'CustomPagesControls' (LoyHutz.CustomPagesControls ...) do not use the JavaScript function 'eval'. Now an adapted version of the JavaScript function 'JSON.Parse' is used in all relevant places. This is also available for development or customizing: 'LoyHutz.Utils.parseJson'.

To continue to ensure compatibility, the following Supervisor Option must be enabled: "System / System(0) / Settings / Web-CustomPages / Allow parsing using 'eval'"
If activated, when using 'LoyHutz.Utils.parseJson', the previously used 'eval' function will be used in the event of an error. The Supervisor Option is only evaluated if the scripts were included via the RubyErbApi function 'api.IncludeScripts'. Otherwise, the behavior can be activated via JavaScript by setting the variable "LoyHutz.Util.allowParseUnsafeEval = true;" is set.

Notifications provide information about new releases from waveware. The creation of this notification has been adjusted.

A notification that a new waveware version is available for download will only be created if there is not one from the previous day.

Previously, tool windows in the Windows Client were automatically updated after every click on a custom button.

For performance reasons this no longer happens. If a rule does server-side actions, for example, have an effect on the DMS, the 'RefreshDms' building block must be used.

Selections with the selection filter "empty" or "not empty" produced unexpected results if there were empty strings in the filter field. The filter expected NULL as a value in the database when filtering for "empty".

Using symbol actions in the CAD viewer could lead to a memory leak. With each action, the RAM used in the Windows Client quickly increased by 200 MB to several GB, which led to a loss in performance.

If a drawing was re-imported via CAD import to update an existing import, information about stamps etc. was transferred, but symbol links were lost.

Field rights were not checked correctly in 'CatalogControls' of the Custom Pages.

If a user without administrator rights (missing 'SelectionPrintOutputEdit' right) changed the output type of a selection to "Print: Lists", an error message occurred and the waveware Windows Client was closed.

When printing cards, the sorting of lists, e.g. filled with work steps integrated into an LL print form are not always correct.

After updating the Offline Data World and switching from Online to Offline mode, the app had to be closed and restarted once in order to successfully log in Offline. Otherwise an error message appeared and the login was aborted.

An incorrect status was displayed for delegations (sub-transactions). The 'Status' field (13) was used here. Instead, the 'Activity Status' field (8005) must be present on the mobile view.

The field mapping or adjustments made in a field mapping may not have been applied correctly during an import.

With the help of SYNC, mobile databases are synchronized with the Main Station. The status is displayed via a progress bar. The window appears but the progress bar does not update. This is simply a display error in the waveware Windows Client. The synchronization takes place in the background and the completion is acknowledged with a message.

The 'Stay logged in' option, which can be activated when logging in to waveware MOBILE 2, does not work in Offline Data Worlds. An error message appears when logging in with this option.

Protection against CSRF ("Cross Site Request Forgery") is now always enabled. Disabling this protection represents a significant security risk, so the option has been removed from the waveware server settings.

Tokens are used for protection, which the server generates and communicates as part of the returned page. If you use custom pages and the option 'Protection against Cross-Site Request Forgery (CSRF)' is activated in your server settings, you must ensure that the Custom Pages are modified accordingly before updating to this version. More information: 'Protection Against CSRF Attacks'.

When using the DMS and displaying documents, tags were retrieved multiple times. In addition, the documents were always reloaded when changing card areas within a record. When displaying a very large number of documents, this could have a negative impact on performance.

When importing test data, it could happen that import specifications were not applied correctly.

When generating an HTML email using the mail building blocks, the content was not correctly encoded and transferred to the email client.

For memo fields, you can also write the text in an additional text window. There was an error here: If the text window was used to create the text, then closed and the card saved, the text was deleted from the memo field and not saved.

TN-2412-00064

TN-2411-00877

In transport orders, packages were not installed or updated correctly. Neither dump files nor selections were processed in the target system. The files were copied but not processed.

Fixed

In data worlds with transport orders, packages can only be updated with a transport orders.

After updating the Offline Data World and switching from Online to Offline mode, the app must be closed and restarted once in order to successfully log in Offline. Otherwise, an error message appears and the login is canceled.

Will be fixed in one of the next releases.

When using the print function/form generator and when executing server lib rules, a problem could occur with the cache of certain catalogs.

Checking out and checking in documents in the DMS of waveware MOBILE 2 is currently not possible on Android due to a lack of permissions on Android.

Grouping fields using separators did not always work correctly.

After evaluating test steps remotely and saving the test rule, a "CriticalRuleException" error could occur.

Checking out and checking in documents in the DMS of waveware MOBILE 2 is currently not possible on Android due to a lack of permissions on Android.

When defining a serial appointment, the duration can be used to determine how many follow-up appointments should be created.

The option 'How to fit the TODAY period plus [X] months to the end of the month' has been changed to 'How to fit the START DATE period plus [X] months to the end of the month'.

With the start date as the beginning, the view is more clearly defined.

Importing a defective backup file could result in the DataManagement crashing.

When displaying the mobile work step evaluation in waveware MOBILE 2, loading time was longer than average. In tests, calling a large work directive with over 150 steps took about 1 minute.

When evaluating work steps, a detail page can be opened, e.g. to enter descriptions for negative reviews. If the detail page was opened very frequently while the steps were being processed, the app could crash.

Expandable transaction lists, which displayed additional fields of the record when expanded, were not available in waveware MOBILE 2.

If the following parameters were used together in appointment series:

• Validity correction is “earlier”
• Update on an appointment basis

it could happen that appointments that were corrected were deleted.

Due to the fact that Microsoft has already discontinued support for Xamarin, Loy & Hutz is now also discontinuing support for waveware MOBILE 1. From waveware 11.210.510 onwards, the waveware MOBILE 1 app will no longer be released. Connections from the old app to the waveware system are no longer possible with this version of the waveware server. Instead, use the new waveware MOBILE 2 app: 'waveware MOBILE 2'.

The October LTS version 11.210.141 is the last waveware server version with which the old waveware MOBILE 1 app is compatible. If you want to continue using the app, you may update to a maximum of one version of this LTS series.

Protection against CSRF ("Cross Site Request Forgery") will be available from the next release, which is currently available. It will be released in December 2024, will always be switched on. Disabling this protection represents a significant security risk, so the option in the waveware server settings will no longer be available.

For protection, tokens are used that the server generates and communicates as part of the returned page. If you use Custom Pages and the 'Protection against Cross-Site Request Forgery (CSRF)' option is activated in your server settings, please make sure that the Custom Pages have been converted accordingly before the next version. More information: 'Protection against CSRF Attacks'.

Checking out and checking in documents in the DMS of waveware MOBILE 2 is currently not possible on Android due to a lack of permissions on Android.

When installing DataManagement via ClickOnce, an abort could occur with the following error message: "The remote server returned an error: (404) Not found".

The deactivation of a data world could also be carried out when the Designer or System Rule Editor was open.

If the System Rule Editor was first opened without first opening the data management, subsequently calling up the data management resulted in the DataManagement crashing.

Referenced packages have been updated to implement a medium-level security update. It is strongly recommended to update to this version.

When all users of a role were displayed in rights management, the first record was invisible, i.e. it was displayed one record less.

When creating customer packages (with package number 1) there was an error and the subsequent crash of the System Rule Editor.

Mobile

The new waveware MOBILE 2 app has left the BETA development stage and is released for productive use as of this version. The app can be installed via the Google PlayStore or Apple AppStore. To operate the new app, at least one waveware server 11.200.6798 (LTS release April '24) is required. The waveware MOBILE 1 app used libraries from Xamarin, whose support was discontinued by Microsoft. The new waveware MOBILE 2 app is based on .NET MAUI and can be installed and used parallel to the waveware MOBILE 1 app.

If you are already using waveware MOBILE 1, we recommend upgrading to the new app as soon as possible. Due to the discontinued support for Xamarin by Microsoft, Loy & Hutz will also discontinue support of waveware MOBILE 1 with this LTS release - the last supported version of waveware MOBILE 1 is therefore 11.210.141.64 (or another version from this LTS series). The next release (expected November '24) will no longer contain a waveware MOBILE 1 client. Further information: 'Mobile: Version Change and Upgrade Information'.
waveware MOBILE 2 Documentation: 'waveware MOBILE 2'.

Since new waveware versions may be released at irregular intervals, updates have been included in the waveware notification system. When a new version is released, all users with the global right 'Receive update notifications for waveware' will receive a notification.

New versions are checked automatically in the background. If a new version is available, the waveware Service Center can be opened directly by double-clicking on the notification.
Using Supervisor Options (System / Additional Basic Functions (1861) / System / Update Notification) you can switch the notification on and off and specify whether the update check should be limited to LTS versions.

The mail building blocks OpenLocalMailClient, OpenLocalMailClientWithMultipleAdresses, OpenLocalOutlook and OpenLocalMailClientWithMailDraft enable emails to be sent using a local mail program.

If the locally installed Outlook client was used, it was previously necessary to have .net Framework 4.8 installed. This no longer works with newer versions of Outlook. The building blocks mentioned have therefore been changed so that they generate a temporary *.eml file. This file is then opened by the program that is associated with this file extension (normally Outlook). The eml file can be opened by both the new and the old Outlook.

The time periods for LTS releases have been adjusted. Previously, LTS releases appeared at intervals of 6 months and were provided with critical security updates every 12 months.

Starting with this release (October '24), LTS releases will be released at 12-month intervals and will be provided with critical security updates every 18 months. This means that major updates only need to be performed every one and a half years in order to be able to operate the version safely with smaller updates.

When inserting multiple documents into a card at the same time using drag & drop, it could happen that an inserted document was not linked to the correct record due to the stacking of the cards. This was visible on the relevant 'Document' object in the 'Assignment' transaction, as the field of the assigned ID ('Object ID' or 'Transaction No.') was empty.

To edit the content of a memo field better, the text can be opened in a separate window. The context menu of this separate window differed from that of a regular memo field, so that, for example, the phrase catalog could not be called up.

When displaying the mobile work step evaluation in waveware MOBILE 2, loading time may be longer than average. In tests, calling up a large work instruction with over 150 steps took about 1 minute (in MOBILE 1, loading was completed on average after 1-7 seconds).

The expandable transaction lists known from waveware MOBILE 1, which displayed additional fields of the record when expanded, are not available in waveware MOBILE 2. These will probably be replaced by a new function.