Fixes

Performance problems have been resolved:
- The load time for portfolio charts, matrices, and gantt charts has been reduced.
- Loading of content area items has been improved to speed up rendering of content areas.
The error which occurred in global search on attempt to view all search results or filter the results has been fixed.This fix is a resolution for ticket ASD-7032 and ASD-7326.
After a favorite has been assigned to a favorites folder, it was not possible to change its location to the root level of the Favorites menu. The editor has been corrected to enable detaching of favorites from favorites folders.
Email addresses of users are correctly displayed in data workbenches. This fix is a resolution for ticket ASD-6828.
In data workbenches, the information about the number of returned objects has been corrected for date filters and shows the correct returned number of objects. This fix is a resolution for ticket ASD-6853.
Rearrangement of columns in data workbenches via the Structure button has been fixed and filter values are maintained after restructuring. This fix is a resolution for ticket ASD-6587.
Content areas are no longer double refreshed when matrix reports are embedded as content items. This fix is a resolution for ticket ASD-6863.
User created content pages are deleted if they are hidden by the user prior to adding them to the content repository. The names of these deleted content pages are no longer stored in the background and users can later create a new page with the same name. This fix is a resolution for ticket ASD-7241.
String array properties are now stored when set via inline editing. This fix is a resolution for ticket ASD-6402.
The sort order in drop-down lists has been fixed to follow the sort order defined in the enumeration or in the range query defined for the object class property. This fix is a resoltuion for ticket ASD-6785.
The missing operation to detach components from applications has been added. The button is visible in data workbenches for assigning components to applications. While the assignment of a component to an application creates a local component object in the background, the detach operation will delete the local component. The component itself is not deleted but detached by this activity. This fix is a resolution for ticket ASD-6919.
The standard functionality to block out calendar days which is available in Alfabet 10.15.x has been re-established for Alfabet 11. It is now possible to create, edit and delete blocked out dates one day at a time.
The object class icon for standard platforms is shown correctly in map reports. This fix is a resolution for ticket ASD-6283.
The rendering issue in the assignment editor has been fixed. This fix is a resolution for ticket ASD-6949.
In explorers, the option to open a view in a new tab has been deactivated for explorer nodes with no view behind them. This fix is a resolution for ticket ASD-7157.
The legend of bar charts has been corrected to show only coloring of bars which represent values other than zero and are therefore displayed in the chart. The coloring is consistent in bar chart and legend. This fix is a resolution for ticket ASD-7163.
Rendering of doughnut charts in content areas has been fixed to show the total number within the doughnut chart reliably in all doughnut charts it is implemented for. This fix is a resolution for ticket ASD-7222.
Issues with data quality rules have been resolved:
- Issues with rescan of data quality rules have been corrected.
- The execution of the RescanDataQualityRules ADIF job will no longer lock the database during generation of temporary tables. The asynchronous execution will no longer prevent users from working with Alfabet when rescanning complex data quality rules.
- Export of the My Data Quality Issues view to Microsoft Excel® file has been fixed. This fix is a resolution for ticket ASD-6711.
- The limit of maximum 50 objects in bar charts derived from content areas is no longer applied to the data quality bar chart displayed in the Data Quality visualization of the data workbench. The limit is only applied to user generated visualizations.
The issue with filtering of the Organizations view (ORGG_Organizations) has been fixed. This fix is a resolution for ticket ASD-6163.
Filters for diagram reports were displayed in the Global Filters filter section of the diagram filters and the Page Filters section of content areas including the diagram report. This has been corrected, and filters are shown in the Report Filters section where they belong. This will change the filter behavior on the content page containing the diagram, as these filter fields are no longer available on the page level.
The issue with the search for providing applications in the Business Architecture content page of business capabilities has been fixed. This fix is a resolution for ticket ASD-6559.
In the data capture editor, generic attributes with a range definition are added correctly to the Extended Attributes tab. This fix is a resolution for ticket ASD-6041.
The editor for creating workflow releated job schedules has been fixed to allow all types of actions to be selected. This fix is a resolution for ticket ASD-7234.
Registering of user login and logout for the Alfabet components has been corrected to enhance the security with better GUID Id generation mechanisms and to fix the problems with wrong user information in audit tables. This fix is a resolution for ticket ASD-7027.
The Technopedia® product selector was fixed to show complete captions for all filter fields. This fix is a resolution for ticket ASD-6782.
Information about the Technopedia® ID has been added to all selectors used to import objects from Technopedia.
Breadcrumbs shown in Alfabet have been enhanced to process browser back button interactions. If a user is going back to the previous view via the browser back button, the previous view is no longer added again to the breadcrumbs, but the breadcrumbs are reduced to end with the view the user has gone back to. This fix is a resolution for ticket ASD-7156.
Opening of the workflow explorer from a link in a workflow notification email was fixed to set the focus on the correct workflow step in the explorer. This fix is a resolution for ticket ASD-7121.
The way changes are saved in Alfabet Expand has been corrected to speed up the saving process and avoid database connection outages for other Alfabet components. Instead of saving the complete meta-model each time, only the changed part of the configuration is saved. This fix is a resolution for tickets ASD-6871 and ASD-6955.
The copy and paste functionality for the menu items in user profile configuration has been adjusted to accept the new option to create a three-level menu. This fix is a resolution for ticket ASD-6083.
Skype® has been deprecated. The SkypeId and SkypeDomain object class properties have been removed from the object class Person and from all relevant User editors.
In the class settings, the object selection for the Modify Button functionality of the Presentation Object node and all functionalities to add items to the System Content Repository has been corrected to show only items for selection which have not been selected previously. This fix is a resolution for ticket ASD-6074.
The Access in User Interface attribute of object class properties related to Technopedia® integration has been set to ReadAccess to enable display of the information on the Alfabet user interface.
The way Edit buttons are handled in content areas has been fixed:
- If a custom editor is defined in the class settings of the object class, the custom editor opens as part of the editor.
- Buttons defined directly in the content area are available in the content area.
This fix is a resolution for ticket ASD-6307.
The new XML attribute MaxLayoutCalculationDuration has been added to the XML object SolutionOptions. The default value is 30 seconds. If rendering of a view requires more than the set layout calculation duration, rendering of the report is cancelled and the user is informed that the view cannot be rendered. The user is also informed that the problem can be fixed by reducing the number of objects to be displayed if filters are available. The maximum layout calculation is not applied to publications.
The user interface style group Error Level has been corrected to also include border color and text color definitions.
Drop-down fields for object selection in custom editors and wizards for which a lookahead query has been defined are corrected to show only values corresponding to the query results. This fix is a resolution for ticket ASD-6771.
If the default stereotype set for an object class is not matching the defined stereotypes, it is nevertheless set for the object class if the user creating the object does not explicitly choose a stereotype. To avoid issues with wrong stereotype settings, the private meta-model has been scanned for correctness and cleaned from offending default stereotype settings. In addition, a script will be run during update of the meta-model to the Alfabet 11.9 release which scans the customer defined settings in the meta-model. If a default value is incorrect, it will be removed, and a message is written about the removal in the log file generated during update of the meta-model. This fix is a resolution for ticket ASD-6520.
If a default stereotype is set for an object class, the default will be added automatically to the stereotype selection fields in the user interface and users only need to select a stereotype if the stereotype shall deviate from the default. This fix is a resolution for ticket ASD-6963.
Visibility conditions defined for content items in a data workbench are not only applied to the visibility of content items in the content pages, but also to content items in the content repository. This fix is a resolution for ticket ASD-6288.
If a content item with the same content has been added to two content pages of the same content area, these content items can now be deleted independend of each other. If one content item is deleted, the content item showing the same content on the other content page is persistent. Addition of the same content item to the same content page twice has been disabled. This fix is a resolution for ticket ASD-6860.
If an object profile is assigned to a class-based content area and an edit operation is also available in the generic operations of the object class, all edit buttons from the object profil were hidden and only the generic edit operation was displayed as button. This behavior has been adapted to hide only edit buttons for standard editing of the object. Buttons for editing specific attributes, like changing the object state of the object, are still added to the class-based content area. These buttons can be hidden via the class settings, if they should not be included. This fix is a resolution for ticket ASD-6172.
The rendering of custom explorer root nodes has been fixed to display the view assigned to the root node. In addition, content areas can now also be added to custom explorer root nodes as views of the type ObjectView.
The issue with the advanced mode of Alfabet Expand activating not only button creation for configured reports, but also for Alfabet standard graphic views has been resolved. The standard graphic views are private objects that must not be customized.
The behavior of the Technopedia® selector opened from a configured report based on the Capture_Components template has been adapted to the behavior of the selector in standard views. If the report is embedded in the content area of an ICT object, component category or vendor linked to Technopedia, the relevant data about this object is prefilled in the selector and cannot be changed by the user.
During update of the meta-model with a customer configuration including ADIF scheme update failed if ADIF schemes existed in the AMM file and the target database with names only differing in case sensitivity. The update meta-model mechanism has been changed to identify ADIF scheme names case insensitive. ADIF schemes will be overwritten when the name of the ADIF scheme in the target database is the same as the name of the ADIF scheme in the AMM file except for the use of capital and non-capital letters. As ADIF scheme handling has been made case insensitive, it is no longer possible to create two ADIF schemes with names only differing in case sensitivity in one database. This fix is a resolution for ticket ASD-6624.
Restore of databases from ADBZ file failed if the database contained exceedingly large tables, for example for audit information. To resolve this issue, the timeout for index generation for database tables has been made configurable. The timeout is now read from the Database Settings > Command Details > Default Execution Timeout setting of the server alias the restore is performed with. This setting also defines the timeout for any other server related processes.
The link to the help center defined in the Overview > Help Server field of the server alias can be defined with or without a slash at the end.
IT-Pedia® integration failed if server variables for other integration solutions were missing in the server alias of the Alfabet Web Application. The way server variables are evaluated for IT-Pedia has been corrected to exclude checks for other integration solutions.
Restore of audit data has been fixed for database restore using the AlfabetAdministratorConsole.exe. Audit data is taken over from the source to the target database if -IncludeAudit true is added to the command line. This fix is a resolution for ticket ASD-7131.
When the definition of workflow names in the command line of a job to start workflows with AlfaAdministratorConsole.exe is not correct, an error is returned, and the job will not start any workflows instead of starting all available workflow which are configured to start automatically.
The API Permissions tab of the user editor is no longer deactivated when ADIF is not licensed by the customer. An ADIF license is no longer required to use the Alfabet RESTful services, and the tab is required to set the RESTful service access permissions for users.
Upload of documents to the internal document store of the Alfabet database via the endpoint idocupload of the Alfabet RESTful services has been corrected. If documents already exist, they can be updated. This fix is a resolution for ticket ASD-7560.
If the saml.json file is missing in the SAML configuration, user access is blocked instead of opening the standard SAML login screen which offers insufficient authentication security.