Improvements

The User Settings editor has been revamped to show only one Update button. Changes to the default user profile, current theme, and interface language are all saved and updated with a single click of the Update button, which automatically closes the editor.

Better usability in global search. The global search field in the masthead has been improved to streamline the user experience. The search term a user enters for the global search is retained in the search field if the Category is changed.

Persistent search term and results in the navigation panel. The navigation panel's search field retains the search term and results even after the user selects an item, making it easier to revisit and explore additional results without reentering the search term. The search term can be removed by click the x button next to the search term.

Data quality rules are now only triggered for the attribute that is changed via inline edit in a data workbench or content area. This ensures that only relevant data quality rules are recalculated rather than all rules for an object, which enhances performance significantly. When the user opens a content area, the status of the data quality rule with the highest severity (Hint, Warning, Error) for the object is displayed in the breadcrumb next to the current object's name. A user can click the severity symbol in the breadcrumb to open the data quality rule pane that lists all issues, including when the data quality violation was first reported and the last time the rule was recalculated. A Recalculate button in the pane allows the user to recalculate all data quality rules for the object on demand. The data quality rule severity symbol is available on relevant content items and clicking it opens the data quality rule pane with relevant information about the data quality violation.

Users may now explicitly recalculate indicators. This new capability mitigates potential performance bottlenecks caused by the automatic recalculation of a high number of calculated indicators with complex calculation rules. The options to recalculate indicators are not available for read-only user profiles. Users can rescan indicators as follows:

• Click the new Rescan All Indicators option in the three-dots menu of a content area to recalculate all indicators available for the current object. The indicator recalculation button is available next to each indicator in an attribute group. The button has a tooltip showing the date and time when the indicator was calculated.
• Click the new Rescan All Indicators in the Group option in the three-dots menu of a content area to recalculate all indicators in an attribute group.

Users may now explicitly reload the data in a content item via the new Refresh Content Item option in the three-dots menu of the content item. This option ensures that a user can decide to explicitly refresh only the selected content item. This boosts performance and ensures that the user avoids wait times. The new Refresh Content Item capability is activated per default on content items.

Automatic reloading of all content items upon data changes can be re-implemented for content items by solution designers in the configuration of the content area or guided data view.

Tooltips  have been extended to include the following:

A new functionality that lets users zoom in and out of reports provides a significant improvement in analyzing data in reports. A new Zoom button is available in the toolbar of the report or a content item with an embedded report for most report types including matrix, Kanban, branching diagram, diagram view, cluster map, and node arc reports.

A new Structure button is available in the toolbar of many standard views (GraphicViews) showing a tabular dataset. Similar to the Structure button in data workbenches, users can add, remove, and sequence the columns in the view. Note that some columns as well as a few views are excluded because they cannot be changed for technical or methodological reasons.

Selectors now show radio button controls if the user can only select one object. Multi-select checkboxes are used if the user can select multiple objects. This addresses the issue in ticket ASD-7649.

Filter settings in data workbenches are retained when the user changes the language displayed on the Alfabet user interface. Filter values are kept in the new language for the following:

• property with an enumeration definition
• property with a string range definition
• indicator value based on an indicator type with a range definition

The configuration options for generic operations have been enhanced.

• Configure confirmation messages for generic operations that add new and existing objects and detach objects from a parent object.
• The Object-Based Operation Context > Enabled attribute and the Base Context Class of generic operations are now evaluated independently of each other which has enabled the configuration of each attribute to be simplified.
  • If the Object-Based Operation Context > Enabled attribute is set to True, the button will be shown in the content area for the relevant object class.
  • If the Base Context Class attribute is specified, the button will be displayed in data workbenches only if they are embedded in the content area of the object class specified as the base context class.
• The REFSTR values of the objects currently selected in a data workbench or the current object of a class-based content area are passed to generic operations triggering an ADIF job or event.

• The ALFA_MM_PROP_INFO table has been extended to also include information about calculated properties. The new Boolean property Is Calculated Property ( IS_CALC_PROP ) of the ALFA_MM_PROP_INFO object class stores the information whether the object class property is calculated.

The specification of a query to define a data workbench is optional in Alfabet 11.10. If no query is defined for the data workbench, the data workbench includes all objects of the object class or object class stereotype specified in the Class / Stereotype Name attribute. Queries can optionally be defined to limit the number of objects in the data workbench. For example, a query might be configured to display only objects assigned to the parent object that the user is currently working with.

The length restriction to import translated interface strings has been increased from a 600 characters per string to a maximum of 850 characters. This increase provides more flexibility to configure hints and explanations for users on customized interface elements.

A new Alfabet query instruction allows the coloring of release status values to be included in tabular configured reports:

• SetReleaseStatusStyle(ColumnName,ClassName)

To define the instruction for an object class stereotype, the stereotype must be defined in the instruction after the class name separated with a colon: ClassName:StereotypeName.

A new option can be configured to reduce the maximum number of base objects to be processed for a data-workbench configured report. This ensures that reports with an excessively high number of base objects do not cause performance bottlenecks.

The new XML attribute MaxNumOfBases has been introduced for the XML object SolutionOptions to restrict the maximum number of base objects handed over to the report. When this attribute is set and a user opens the report with a higher number of base objects, a message is displayed to the user about the restriction. The default value of the new XML attribute is -1, which means that no restriction is applied.

Variables used in the XML object GenericAPIIntegrationConfig can be defined directly in the user interface in the definition of the integration connection for the generic API integration. This provides more flexibility in who and how the variables are defined and is an alternative to defining them in the server alias configuration of the Alfabet Web Application. Note that the server variable definitions in the server alias configuration supersede definitions in the integration connection specification.

For Alfabet 11.10, the example configuration files required for the Alfabet Web Application and the Alfabet API server have been changed and re-structured to increase usability and introduce new technology.

The content of the alfasettings.json file has been changed:

• A change in Alfabet software architecture requires that in the alfasettings.json file, the AlfabetWebConfig section must be changed to:
  • "AlfabetWebConfig": {
    • "presentationSessionManagerBuilder": "AlfaPresentationInterfaceImpl.Integrated.IntegratedPresentationSessionManagerBuilder, AlfaPresentationInterfaceImpl",
    • "expandManagerBuilder": "Alfabet.Services.Interfaces.ExpandConfigurator, AlfaMMProviderServiceInterfaceImpl"
  • }
• The NLog settings have been removed. A separate NLog configuration is required with a separate NLog configuration file.

The availability of log files has been changed:

• An Example folder is available not only in the AlfabetWebApplication , but also in the AlfabetAPIServer and the Programs folders.
• All example folders have sub-folders for on-premise installation, demo installations, cloud installations, and container installations. The folders contain all files required for the configuration including the NLog configuration files.
• Nlog must be configured directly in the working directory of an application. For the Alfabet Web Application and the Alfabet API server, the directory config is used to store configuration files. An nlog.config file with a re-direct to the Nlog configuration file in the config folder is available in the root directory of both web applications. This file is delivered with each release. Any customer changes to this file will be overwritten whenever a new patch release is updated.

The log generation for processing of events led to issues and deadlocks in event execution. Logging has been corrected and event execution is improved.

A number of changes were made to Alfabet Expand to remove obsolete settings.

• The private CreateVoiceEndpoint and FeedbackBot_Event events are removed from the standard configuration. They were used for the deprecated AlfaBot and FeedbackBot functionalities.
• The Enable FAQ Bot and Enable Feedback Bot attributes have been removed from the user profile attributes. They were used for the deprecated AlfaBot and FeedbackBot functionalities.
• The restriction that information flows could not be created if their start and end dates were misaligned with the start and end dates of the source and target applications has been removed. Any enforcement of the definition of information flow start and end dates should occur via the specification of data quality rules. An information flow's start and end dates will be automatically aligned with its applications per default when an information flow is created, but this can be modified as needed. Misaligned dates are still highlighted in the Information Flow view.
• The Auto-Run attribute of the private UpdateReportsPopularity ADIF scheme has been set to False. The ADIF scheme is no longer run automatically on each update of the meta-model. This information was used for the deprecated AlfaBot. The popularity of configured reports is calculated by the ADIF job based on the information stored via presentation usage tracking. The ADIF scheme will be kept in the database to provide customers a means to check usage of their configured reports.
• The private Color and ForeColor object class properties will be removed from the Alfabet meta-model because they are no longer used for coloring in the user interface. If values exist for these object class properties for an object class in a customer database, the object class properties are not removed from the object class but changed to public object class properties.
• The Guide Page Designer option has been removed from the selection in the Alfabet Expand Access Options in the user editor. Guide pages are no longer supported.

The following attributes for the configuration of deprecated functionality have been removed from the server alias editor.

In the Server Settings > General tab:

• Control Client Aliases
• Enable MS Teams Outgoing Webhook without Authentication
• Send Web Message Direct: Web messages are not available any longer as button interaction. The URL of an Alfabet view can be shared directly with other users.
• Allow Edit Object Colors: The button to change object colors in charts is no longer available. Coloring is managed via color themes.
• Allow Usage of Run-Time Fonts: This attribute managed the font setting of deprecated GUI schemes.

In the Client Settings > Authentication tab:

• The SSO_Portal and SSO_CustomMethod options have been removed from the drop-down list of the Mode field. Portal integration and custom methods are no longer supported.
• The HTTP Server Variable for Portal Integration and Custom Method attributes have been removed because they were exclusively used by the portal integration and custom method.

The following embedded third-party components have been upgraded to a licensed version of the latest release:

• DevExtreme.AspNet.Core has been upgraded to version 24.2.7. Copyright © 2000 - 2025 Developer Express Inc., All Rights Reserved.
• DevExtreme.AspNet.Data has been upgraded to version 5.1.0. Copyright © 2000 - 2025 Developer Express Inc., All Rights Reserved.

For Apple® Safari® as browser used on client side, the minimum required browser version has changed with this component upgrade to 15.4 instead of 7.0.