New

The user interface can be rendered in dark mode with light text on a dark background. Dark themes cause less strain to the eyes and are favorable in low light environments. In addition, highlighting can be enhanced. Light colors shine out on a dark background.

A default dark scheme is available for users after migration to Alfabet 11.9. In addition, administrative users and solution designers can decide to base newly created color themes on dark mode. This is only recommended for customers using a preconfigured Alfabet 11.9 solution. Customers having customized the solution with configured reports need to adapt all color definitions in the report configurations to work with both dark and light themes, which can be a huge effort.

Colors and icons defined in the standard Alfabet configuration have been adapted to work for dark themes.

The Alfabet user interface has been enhanced to support keyboard navigation. This is an important step towards 508 compliances for the Alfabet 11.x user interface. Users need to know only a small number of key combinations to perform the major action on the user interface.

Some values which are important to record for objects can be calculated from data already available in the Alfabet database. Calculated properties have been introduced as a new type of object class property for these use cases. customers can create a calculated property based on a native SQL query which defines a database view for storing the calculated values. The database view calculates the values on swmn at runtime. From a user perspective, calculated properties are handled identical to any ReadOnly object class property. They can be displayed in graphics, data workbenches and content areas to inform the user about important data about the objects of an object class.

Calculated properties cover a higher range of usecases than calculated indicators. They can be used to calculate values which are not related to evaluation and can return multiple data types, like dates and references. They provide reliable display of up-to-date values without users having to trigger update via a button interaction. To ensure a good performance of runtime calculation, calculated properties shall be based on simple queries only. The availability of calculated properties is adaptible per class setting.

Tooltips are displayed for values in drop-down fields in data workbenches, content areas, and editors. Users can hover over the info symbol next to a value in the drop-down menu and display a tooltip that provides information to help them understand the available options for selection. The tooltips show existing hints that have been specified for protected and public enumeration items as well as descriptions specified in the Description field for objects like applications, ICT objects, etc.

Roles and indicators can be set in property groups in class-based content areas. The indicator type or role type can be assigned to the property group in the new Property Group field in the standard editors for definition of indicator types and for assignment of a role type to an object class.

Some property group captions have been changed in the preconfigured Alfabet solution to enable unambiguous selection of property groups.

Categorized visual items are introduced to define content items with placeholder text for the actual content. Categorized visual items hide the actual content behind a placeholder which can include a description, an image, information about the category the categorized visual item belongs to, and a tag with highlighted information. The category provides a mean to structure the content items according to use case. Users can see immediately which category the content item belongs to. Coloring can be used as an additional means to destinguish between categories.

Categorized visual items are defined independent of a specific content area and can be added to multiple content areas as content item.

Categorized visual items added to the content repository are by default added with the Categorized Visual Items item type. You can optionally define additional subtypes for this item type, which are then also selectable by the user to see only categorized visual items you assigned to the subtype.

Enumerations can be assigned to object class properties of the type Integer to display the integer values as text in the Alfabet user interface. For example, the user type for users is stored as an integer. While it was displayed as text in standard graphic views, it was displayed as integer in data workbenches generated for the object class PERSON.

A new enumeration type integer enumeration has been introduced. While enumeration items for string enumerations consist of a string value only, enumeration items for integer enumerations consist of both the integer the string represents and the string that shall be displayed for the integer. Users will see the string value on the user interface while the integer will be stored when the user selects the string value.

In data capture templates, either the integer value or the string value of the enumeration items can be returned.

The following enhancements allow user administration in data workbenches:

The standard generic operations have been added to the standard Alfabet meta-model:

• A generic operation to create interface systems has been added to the object class InformationFlow. The selected information flow will be automatically assigned to the interface system. Predecessor and successor are prefilled in the editor with the components the information flow is targeting.
• Generic operations to define the relation of applications to business data and business processes to business objects via business data usage have been added to the object class BusinessDataUsage.
• New generic operations have been added to information flows to provide definition of information flows for components and peripherals. This is a resolution for ticket ASD-6167.
• The button interactions to manage user authentication have been added to the meta-model as generic operation of the object class PERSON and will be available in any data workbench or content area of the object class. The buttons can be excluded from display in the class settings.
• The basic functionality for editing, deleting, and creating objects has been moved from object profile buttons to generic operations fro the following object classes: BusinessData , BusinessDataAttribute , BusinessDataUsage , BusinessObject , BusinessObjectCategory , BusinessSupport , Contract , ContractDeliverable , ContractDeliverableUsage , ContractDependency , ContractGroup , ContractItem , ContractPayment , DataRetentionPolicy , ProjectDependency , ProjectGroup , ValueNode , ValueArc , ValueNodeArch , VMMeasure , VMMeasureType.

Solution designers with access to Alfabet Expand can define generic operations for editing, creating, and deleting objects, adding objects to a parent object and detaching objects from a parent object. This capability enhances the possibilities for solution designers to provide button interactions for custom object classes or custom object class properties.

SCIM is a standard for cross-domain identity management and an important part of identification management in cloud environments. Alfabet 11.9 supports SCIM management with Okta® or AzureAD® as identity provider.

SCIM integration will push user data from the identity provider to the Alfabet database, updating the user information regularly. New users are added to the Alfabet database as anonymous users. The user profile assignment is updated based on identity provider group affiliation. A web-based SCIM management application is available for administration.

A new UseCase object class has been added to the standard meta-model in preparation of the new AI Portfolio Management feature that will be published as part of the preconfigured Alfabet IT Transformation server solution in the near future.