Skip to main content
Skip table of contents

Release Notes 7.4.12

Bug fixes

The following bugs have been fixed in Release 7.4.12.

X4 Web Apps

Key

Summary

X4BUG-252

In some cases, the login dialog did not appear when a Web App was opened or after logging out when trying to log in again. This bug is now fixed and the login dialog is always displayed correctly.

X4BUG-1449

Access rights set for individual components or modules worked as desired for the module and the first level in the <Components> hierarchy in the .wad file. From the second level, the configured access right no longer applied, so that all users could access the relevant components. This bug is now fixed.

X4BUG-1497

In ComboBoxes with autocompletion, the first entry in the picklist was pre-selected. If a character of this entry was intentionally or accidentally deleted, the picklist remained empty. This bug is now fixed and the first entry is no longer preselected. Instead, a placeholder such as "Please Select" appears at the top of the list, and users can start typing directly to find a matching entry.

X4BUG-1515

For read-only text fields, the distance between the display name and the field value was too small. This bug is now fixed and the elements are aligned the same way as for active text fields.

X4BUG-1564

In the <Map> control, the data binding for the iconUrl attribute no longer worked in X4 BPMS 7.4.4. As a result, marker icons were not displayed if the icon source was bound by a property. This bug is now fixed.

X4BUG-1768

In Grid Components, the visible attribute was not correctly implemented in grid columns, so certain columns were not displayed. This bug is now fixed and even if data binding and fixed values are used, all columns for which visible is set to true are displayed.

X4BUG-1944

In the mobile view, the action buttons in dialogs were not aligned correctly and the button name was not fully readable. This bug is now fixed.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.