Multiple persons can be selected when editing roles inline if the role type specification allows multiple persons to have the same role for an object.
Saving of URLs has been changed to add a line break in front of the URL specification only if a title is defined. Issues occurred when line breaks were added to URLs without a title specification. This fix is a resolution for ticket ASD-7742.
The navigation from an element in a data workbench visualization (for example, a pie slice) to a data workbench showing the relevant objects has been fixed:
If the user creates a data workbench visualization for the data displayed after drill-down, the filtering applied to the data table is maintained for the visualization. This fix is a resolution of ticket ASD-7822.
Drill-down showed results for business charts with authorized users as X-axis data. This fix is a resolution for ticket ASD-8211.
Rendering issues in data workbench visualizations have been addressed:
Numbers in stacked bar chart data workbench visualizations show the correct numbers for all bars. This fix is a resolution for ticket ASD-8342.
The error which occurred when the data for the visualization contained empty date settings has been fixed.
Issues have been resolved when searching for objects if more than 300 objects are available.
If a search was executed in the Structure Columns pane of a data workbench and the search settings were redefined, the selection of the columns based on the old search criteria was removed. This issue has been resolved. If the search criteria is redefined, the selection is maintained and moved to the end of the list of selected columns.
The rendering of the editor to change the release status has been resized to provide complete readability. This fix is a resolution for ticket ASD-8332.
Hints are displayed when a user points to a value in the Status field in the user interface.
The Subordinate Features Gantt (FTR_FeaturesGantt) shows the target completion date as a tooltip on elements. This fix is a resolution for ticket ASD-8557.
Application landscape diagrams are no longer copied when an application is created as copy of an existing application.
Slider control filter fields are cleared when the user clears filter settings via the Clear All option.
References can be correctly set between objects if the user interface is rendered in a language other than English. This fix is a resolution for ticket ASD-8219.
If the user interface is rendered in the dark theme, icons in reports are colored the same in the report and in the report legend. Black and white SVG icons will be shown with inverse colors while all other icons retain the coloring.
The data quality rule severity symbols (Hint, Warning, Error) displayed in breadcrumbs are now persistent if they are clicked to open the data quality findings window. This fix is a resolution for ticket ASD-8238.
The Data Quality Rule editor correctly renders the text in the editor and values in drop-down lists. This fix is a resolution for tickets ASD-8113 and ASD-8090.
The query test functionality in the Data Quality Rule editor provides information about a false column name for complex queries. Execution of data quality rule queries with false column names are also logged with Nlog.
Configured reports based on a native SQL query correctly show values with multiple lines in a cell if the query is defined accordingly. This fix is a resolution for ticket ASD-7623.
Workflows migrated with workflow migration definition no longer trigger email notifications for withdrawn workflows. This fix is a resolution for ticket ASD-8374.
All user context settings are completely cleared if the functionality to clear the user context settings is triggered.
Standard generic operations to create information flows in the context of a different parent application/peripheral had the same caption. It was therefore not possible to identify the information flows when defining a data-triggered action rule. To solve this issue, the generic operations were re-named to include the parent object class name. Customers wanting to see the caption without the parent class name in the user interface can change the caption in the relevant class settings for information flows.
The execution of scheduled jobs has been revised to avoid deadlocks and reduce the need of rescheduling. This fix is a resolution for ticket ASD-7489.
The timeout specification in the server alias configuration valid for data quality rule calculation uses the ADIF timeout instead of the default timeout. This change reduces timeout issues caused by long calculations. In addition, data quality rules already existing in the database will not be deleted if a calculation fails. This fix is a resolution for ticket ASD-8091.
Class settings and editors have been added for all monitor types, and the monitor classes and their class settings are visible in Alfabet Expand. The solution designer can create and edit monitors and data workbenches can be created for monitors. This fix is a resolution for ticket ASD-7225.
If an ADIF job is executed asynchronously or synchronously from the command line and the -idletime setting is shorter than the execution time of the ADIF job, a warning instead of an error will be logged stating that the triggered job is either not started yet or not finished yet. This also applies to ADIF execution via RESTful service calls. This fix is a resolution for ticket ASD-8179.
Import of data from Technopedia® failed because of an issue with the required specification of the Technopedia URL. The slash at the end of the URL specified in the XML object GenericAPIIntegrationConfig is no longer removed when establishing the connection.
Text added to categorized visual items can be added to the XML object VocXML so that it is added to the vocabularies and can be translated. The translation will then be used if the user interface is rendered in the respective language.
In Alfabet Expand, the specification of arguments for the search functionalities in user profile menu items has been re-implemented and is now identical to the functionality provided in Alfabet 10.
In Alfabet Expand, two private class settings were available for the object class UseCase. One of these class settings has been removed. This fix is a resolution for ticket ASD-8070.
In class settings, the sort order of property groups can be specified for the property group in general and for the property group in content areas. The definition of the sorting of the property group in content areas now correctly supersedes the configuration of the property group in general. The content area specification is used for the content area it is defined for while the sorting for the property group is used in all other content areas.
The erroneous Tags attribute has been removed from user profile configuration objects. User profiles are added to AMM files as reference data and not as tagged solution objects. This fix is a resolution for ticket ASD-8294.
In the editor to generate an AMM file for meta-model update, the values in the drop-down list to select reference data are in alphanumeric order.
A new Database > Reset Instance Count to the Maximum ALFA_INSTID option has been added to the context menu of object classes. This option should only be used if the import of objects via ADIF or RESTful services (for example, on synchronization with a third-party component) fails, objects are not created, and an ALFA_INSTID value leads to gaps in the stored ALFA_INSTID values. The new option should only be used with extreme caution because it can lead to errors if the counter is reset while users delete the objects with the highest ALFA_INSTID values simultaneously via the user interface. This fix is a resolution for ticket ASD-6650.