Improvements

Data-triggered action rules can be created for more classes. Data-triggered action rules, previously restricted to asset classes, can now be defined for any object class with generic operations for editing, creating, or deleting the object defined. The drop-down list to set the target operation will only show the operations applicable for defining data-triggered action rules.

With the introduction of object inspection, a single-click on an object on the Alfabet user interface opens the object inspection pane and double-click opens the content area of the object. If links in the user interface do not target an object, the object inspection window will be deactivated. In this case, single-click and double-click will open the link target for the following link types:

• Links opening data quality findings. This applies to the My Data Quality Issues view as well as to any link defined in a configured report with the NavigateToResolution instruction.
• Links in configured reports created via one of the following Alfabet instructions: LinkAssignment , EditLinkAssignment , DynamicLinkAssignment , and JoinURLLink

If a data quality rule violation is due to a missing definition on a property, a link will be added to the Data Quality Findings panel. Clicking the link in the Data Quality Findings panel will move the focus directly to the property in the content area where the issue must be resolved.

If multiple indicators were added to a property group in a content area, the sort order was dependent on the REFSTR of the indicator and followed the order of definition of indicators. This behavior has been changed and administrative users defining indicators can change the sort order for indicators within the same evaluation type. The indicators are added to property groups in the order of appearance in the Indicators view of evaluation types. The sort order in the view can be changed using drag-and-drop.

The Generic OAS Integration has been enhanced to provide solution designers the ability to send complete JSON payload in the request body of a REST API call. The ADIF Designer view, which supports report column mapping to request body parts, allows a top-level JSON content returned in the report to be mapped. When the mapped report column provides the complete JSON payload, it is sent to the endpoint as the request body. Alternatively, the mapping view in the ADIF also supports mapping of columns providing JSON content to objects and arrays on the leaf level.

In the resource bundle mapping view, the incoming response body can be mapped to a JSON import scheme. In this case, the JSON response is mapped to Alfabet temporary tables that properly consume the JSON data.

The Register Event Logger functionality of the Alfabet Administrator and the register event logger functionality of the AlfaAdministratorconsole.exe command line tool are not required for NLog logging and have been removed.