Release Notes 7.4.18

X4BUG-1850

If an HTTP REST endpoint is called using HTTP MetaXml as the input handler, the X4 server creates a <Request> XML document that describes the incoming request. In the <Path> <Parts> section, each segment of the URL is listed as either <Constant> (static text) or <Variable> (dynamic value).

Previously, the first segment was silently missing in the<InputHandler type="HTTP-MetaXml"/> configuration. As a result, the listing of path segments did not begin until the second URL segment. This bug is now fixed. The first segment is now correctly displayed as a <Constant> element, which is consistent with all other static path segments.

Example: Root constant for the endpoint myEndpoint with the URL /myEndpoint/items/{ItemID}

Before (faulty):

<Parts>
  <Constant name="items"/>
  <Variable name="itemId">42</Variable>
</Parts>

After (corrected):

<Parts>
  <Constant name="myEndpoint"/>
  <Constant name="items"/>
  <Variable name="itemId">42</Variable>
</Parts>

X4BUG-2339

Process Scheduler: If modified parameters and schedules were used at runtime, resetting all parameters to default resulted in the .runtime file being deleted. As a result, manually adjusted schedule changes were also lost and reset to the default state. This bug is now fixed so that resetting parameters no longer removes a .runtime file and existing runtime configurations (e.g. modified schedules) are preserved.

X4BUG-2387

Configuring the SQL Profiling The Exclude filter in the .profiling configuration had no effect when a process was started via a Parallel Process Starter Adapter. The affected processes were still displayed in the Process Monitor and logged in the database. This bug is now fixed so that processes that are excluded from the .Profiling file are no longer logged or displayed in the Process Monitor regardless of the startup type.

X4BUG-2193

POP/SMTP and IMAP adapters: In previous versions, sending and receiving email failed if S/MIME signing and/or encryption was enabled in the POP/SMTP or IMAP adapters. This bug is now fixed, so that e-mails can be correctly signed and/or sent and received in encrypted form again when S/MIME configuration is enabled.

X4BUG-2278

COBOL Copybook Reader: When processing ANSI-encoded files, the output was converted to UTF-8, which in certain cases corrupted characters. The original encoding of the input was not preserved correctly. This bug is now fixed so that the encoding of the input is correctly taken into account again and can be controlled via an optional parameter (encoding).

X4BUG-2102

Mapping Editor: If the Source view was enabled by default in the Mapping Editor in the Designer settings, mappings with an internal error ("Document was null") failed. In the Design view, however, the mapping worked correctly. This bug is now fixed so that mappings can be executed reliably regardless of the selected editor view (source or design).

X4BUG-2368

In previous versions, it could happen that the X4 Designer did not react during debugging of processes, especially if the debug functions Step Into and Step Over were triggered several times quickly in succession using the shortcut keys F5 or F6. In this case, the designer had to be terminated via the task manager, as it was no longer operable. As a result, unsaved changes could be lost. This bug is now fixed by preventing competing debug steps and securing potential endless loops in the debug process.

X4BUG-1462

<Video> control: In Chromium-based browsers (such as Chrome, Edge, Brave, Opera), embedded videos experienced long loading times, limited playback control (no fast-forward), and hang-ups when switching between the video page and dashboard. This bug is now fixed and video playback is now stable in Chromium-based browsers without lengthy loading times or restrictions on navigating between pages and videos.

X4BUG-1566

<Link> control: When using <Link> controls with the componentName attribute, the link target was not opened directly in a new window. Instead, a blank blue screen appeared; the link target was not displayed correctly until the browser was navigated back. This bug is now fixed and the link target is opened directly in a new window without any display errors.

X4BUG-1632

<UploadAction>: Two problems occurred during the upload with the maxSizeMB attribute set: The error message did not appear again when the same too large file was uploaded again, and after the file dialog was canceled, the application was stuck in the load state. This bug is now fixed so that validation errors are reliably redisplayed and canceling the file dialog no longer causes hanging status.

X4BUG-1730

<UploadAction>: An internal server error occurred when starting an upload via an <UploadAction> if an optional property of the type Decimal was empty in the Web App component. The error occurred after the file was selected and prevented the upload completely. This error is now fixed so that the upload is reliably executed regardless of the state of an optional property of the Decimal type.

X4BUG-1948

Grid component: Footer options configured in the GridSettings (cleanupEnabled="false" and reloadEnabled="false") were ignored so that the corresponding buttons were still displayed in the footer of the Grid Component and could be used. This bug is now fixed so that disabled footer functions are correctly hidden and can no longer be used.

X4BUG-1951

<ComboBox> control: In combo boxes, the list of suggestions was not scrollable with numerous hits and did not react to the mouse wheel. This allowed only the first visible entries to be selected. This bug is now fixed, so that the entire list of suggestions can be scrolled again and all entries can be selected regardless of the length.

X4BUG-1994

If a Web App used .viewmodel files for the properties of its components, the property model could be lost after several days of running the X4 server. Affected properties were then reported as referenced but not present in the model. A restart of the X4 server did not fix the problem – only a manual save via the designer temporarily restored the functionality. This bug is now fixed. The property model remains consistent even with extended X4 server runtime, regardless of whether component-level ViewModels or direct properties are used in the component.

X4BUG-2015

MasterDetail Component When navigating back from a detail view to the master or grid view via the global componentName, the underlying data model was not reinitialized. As a result, values of the previously opened data set could be retained and unintentionally processed further. This bug is now fixed so that the data model is completely reloaded when navigating back and no longer takes over outdated values.

X4BUG-1947

Process Monitor: If you navigated to a later page (> page 1) and then applied a filter with fewer hits, the page index remained unchanged. As a result, the current page was out of range, so no data was displayed even though results were present. This bug is now fixed so that when a filter is applied or changed, pagination is automatically reset to page 1 and the filtered results are displayed correctly.

X4BUG-2233

Process Monitor: When manually starting a subprocess from the Process Monitor with the Switch View to New Instance option enabled, an error message could occur because no valid execution details could be determined. This error is now fixed and it is no longer possible to manually start subprocesses in the Process Monitor. The Start Process button is now disabled for subprocesses.