ICT objects and business functions have been added to the range of object classes that can be added as object to a service item. They were available for service items in Alfabet 10 releases and were missing in previous Alfabet 11 releases. This fix is a resolution for ticket ASD-10455.
If a user set a global filter in a content area, the items in the content area were not updated according to the filter setting unless the user clicked the browser refresh button. This has been corrected and visible content will be updated with the global filter settings. This fix is a resolution for ticket ASD-9817.
Empty values were not filtered if a data workbench column filter was set to return all values for an object class property based on an enumeration. The filter has been changed to explicitly contain an option for empty values.
Export of content areas caused the user interface to become unresponsive, preventing the export process from completing.
Favorites for workflow steps could not be opened.
Workflows configured to send an email when the workflow was finished terminated with an error message and the workflow was never marked as finished. The fix of this issue is a resolution for ticket ASD-10310.
The Use Recipient's User Profile for External Links setting in the server alias of the Alfabet Web Application was not honored when the user opened the user interface from a link in an email sent in the context of a workflow. The user profile opened with the sender's user profile and an error was displayed if the recipient did not have the user profile assigned. The fix of this issue is a resolution for ticket ASD-9767.
If a user selects objects in a data workbench or tabular view and then changes the filter settings, any selected objects that are no longer visible will be automatically deselected. In a hierarchical data workbench, if a user detaches a selected object from its parent, the selection is not transferred to the next object in the list. Any selection will be cleared.
If a user updates data in either the Basic Data or Object Details attribute groups in a content area or guided data view, and the updated data is part of the breadcrumb information, the object data in the breadcrumb will reflect the changed data.
The storage of workflow step status and comments was incorrect if saving of recent objects was activated in the server alias of the Alfabet Web Application. This issue has been resolved and workflow activities are now saved correctly.
Changes performed via button interactions on workflow steps did not immediately take effect because the button interaction did not update the content area. The fix of this issue is a resolution for ticket ASD-10416.
Users could not switch between the Analysis View and Data Entry View in the data workbench if the object was locked and the user had no edit permissions. Users were thus not able to change to the the Analysis View if the Data Entry View was used as the first entry point to the object. The switch between both views has also been enabled for locked objects. Users can access both views but will not have edit permissions in any of the views.
Strings in Categorized Visual Items were not consistently translated when the UI was rendered in a language other than English.
Category headings in the drop-down list of results for the global search were not translated when the UI was rendered in a language other than English. The fix of this issue is a resolution for ticket ASD-10707.
The user permissions for deleting content pages from content areas were ignored when the content area was opened from an explorer and the user had edited the object. The fix of this issue is a resolution for ticket ASD-10622.
An error occurred when creating a data capture template for the class stereotype AI Feature if the property Name was included in the data capture template.
If data was updated from a data capture template and extended attributes were set only for a subset of updated objects, the empty values were filled with values set for other imported objects. The fix of this issue is a resolution for ticket ASD-10351.
If the Enable for Data Capture Templates attribute was not specified for a class setting, the system did not fall back to the Enable for Data Capture Templates setting in the class model. This has been fixed and the Enable for Data Capture Templates attribute specified for the object class property will be used if the Enable for Data Capture Templates attribute is empty for the corresponding property on the class setting.
An error occurred when a user tried to equally distribute benefits in the Benefits Tracking view for projects. The fix of this issue is a resolution for ticket ASD-10490.
When the width of a standard graphic view or configured report was modified, it was not possible to revert to the default layout. A new Reset to Default option is now available in the three-dot menu for standard graphic views, configured reports, and business functions that embed graphic views. This option restores the view to its original default settings. When selected, a confirmation message is displayed indicating that filters and column structures will be reset to their original configuration.
When a user resized a wizard window and then changed to another wizard step, the wizard returned to the default size.
The 50-object limit in data workbench visualizations was implemented even if the graphics showed aggregated values with only a small number of visual elements. This has been corrected and the number of objects displayed will only be reduced if the visualization would result in an exceedingly high number of graphic elements.
If the database contained indicators without assigned values for an object (for example, due to data imports via data capture templates), setting the indicator in the data workbench resulted in a duplicate entry being created. The fix of this issue is a resolution for ticket ASD-10884.
In relation selectors that allow linking a base object to different target object classes, changing the target class removed the base object context. The fix of this issue is a resolution for ticket ASD-10956.
If a selector other than the standard user selector was implemented via the class settings for the object class Person, the Users Administration (ADMIN_UsersOverview) view could not be opened. The fix of this issue is a resolution for ticket ASD-10105.
The Service Product Items view did not show any objects when rendered in a language other than the default language. The fix of this issue is a resolution for ticket ASD-10454.
A check for unallowed special characters was missing for user profile and object class property group definitions. The resulting names led to rendering issues and error messages. New objects are now scanned for special characters like '&', and new objects cannot be created if the name contains a special character. Existing objects are not checked. Customers are advised to check their configuration for no-permissible characters in technical names of user profiles and object class property groups. On migration to Alfabet release 11.12, customers can check whether issues with duplicate user profile names exist in their database. User profile name duplications will be listed in the Microsoft Excel® log file created during update of the meta-model. This fix is a resolution for ticket ASD-10553.
If the Responsibilities view was embedded in a wizard, closing the error message about incorrect role setting erroneously closed the entire wizard. The fix of this issue is a resolution for ticket ASD-10568.
The Reports Administration view could not be opened when filters had been set. The fix of this issue is a resolution for ticket ASD-9669.
The Role Types view of the Class Configuration explorer included a non-functional Allow Duplicate Roles setting. This setting has no effect and was removed from the view.
When an error occurred during authentication via an IDP service provider, the error message was misleading. It informed the user about a wrong configuration instead of an issue with the IDP service provider. The content of the error message has changed. It is not possible for the system to distinguish at the time the error occurs whether the error is caused by a false configuration or a general system issue. Therefore, the error message now lists both as potential reasons for the failure of authentication. This fix is a resolution for ticket ASD-8836.
Alfabet sessions were terminated although the user was active. The fix of this issue is a resolution for ticket ASD-8459.
Performance issues caused by recalculating all data quality rules affecting a view’s base object have been resolved. Recalculation is now limited to data quality rules where the view the user is currently working with is the resolution view defined in the data quality rule.
The Data Quality Score (DataQualityScore ) and Data Quality Severity (DataQualityMaxSeverity ) object class properties which are available for all relevant object classes were also added to the Data Quality Violation (ObjectDataQualityFinding) object class. This object class is a technical object class for storing the findings resulting from data quality violations. It is not subject to data quality checks and the two object class properties for storing data quality violations have therefore been removed.
Performance issues with Gantt charts showing milestones have been resolved.
The display of custom editors in wizards has been fixed to honor the tab index and tab order in the custom editor definition. This fix is a resolution for ticket ASD-9996.
For some object classes, configuration of class settings to use runtime editors for an object class resulted in errors when the user tried to open an object of the object class. The fix of this issue is a resolution for tickets ASD-10706 and ASD-10955.
Setting a visibility condition on a group box caused the custom editor tab to load endlessly. The fix of this issue is a resolution for ticket ASD-10441.
List box controls were never supported for data entry in custom editors or custom filters. The list box control icon has therefore been removed from the editor for customer editor or configured report filter design.
A range query has been added to the CostType object class property of the SkillRequest object class. At the same time, the accessibility of the object class property was set from Protected to Private and cannot be changed by customers. The accessibility of the Auto object class property for the CostType object class which specifies whether the cost type is to be available for skill requests in the context of project management has been changed from Private to Protected. Customers can change this object class property to add or remove cost types without changing the range query for the skill request.
Tags set in Alfabet Expand for object class property groups were ignored. This has been corrected and object class property groups can be included in AMM files based on tagging. This fix is a resolution for ticket ASD-10641.
Diagronal label orientation in configured bar chart reports did not functioning correctly.
ADIF import from CSV files has been fixed to honor the setting of the Import Column Binding attribute of the import entry. If the Import Column Binding attribute is set to ByName columns are not imported in the order specified in the import file but according to the column name in the attribute definitions for the ADIF entry.
IDOC downloads via ADIF were not logged.
If the number of requests to a third-party API via the generic API integration interface exceeded 100, only the most recent 100 requests were processed. Responses from earlier requests were ignored, leading to incomplete data handling. This issue has been resolved. The system now correctly processes and stores all API requests, regardless of volume. For example, payload reports containing large numbers of calls (e.g., 2,000 or more) will now have all corresponding data accurately persisted in the temporary tables.
Update of the meta-model including role type configurations merged the role types to the target database, but completely overwrote the class configuration for role types instead of merging changes to the existing class configuration. The fix of this issue is a resolution for ticket ASD-9158.