New
The following enhancements to the Alfabet platform are available with this release.
The context-sensitive help has been extended to include a search field based on a full-text search of the online help. If the standard context-sensitive help topics don't answer the user's question, a search term can be written in the new search field at the top of the help panel. The topics returned by the search are shown in a drop-down list and the topic that the user selects is displayed directly in the help panel. Available links go to the topic in the browser-based online help where users can easily navigate to related topics.
For on-premise customers: During installation, specify the directory to install the index files required for the full-text search functionality. The search index files provided by Alfabet must be placed in this folder. After installation, configure the server alias to access the folder to find the search index files. Specify the Search Index Directory attribute with the full directory name of the search index directory specified during the installation. The Help images must be added to the Help Content Images icon library.
Milestone dates can now be changed in a timeline via drag-and-drop. If a user has edit permissions to an asset in the Gantt chart, they can drag any of its milestone to a new point in time. While dragging the milestone, a date indicator is displayed to support the definition of the new milestone data. This is supported in all Gantt charts where milestones are available.
A new diagram template is available to support modeling business processes using the Business Process Modeling Notation (BPMN). The new diagram definition BPMNDiagram can be used to configure custom diagram templates.
Content pages can be exported to PNG or SVG format. A new Export Page option has been added to the three-dots menu of a content area. The export includes all content items currently displayed in the page as well as context information about the exported page. If the exported page is in a class-based content area, the file will include the ID and name of the asset and the page name. For pages exported from content areas that are not class-based, the file includes the content area name and the page name.
The set of assets that a user can choose from when defining an attribute in the data workbench or content area can be configured. For example, a solution designer could specify that only applications that are cloud relevant may be assigned to an application group based on a specific application group stereotype.
Solution designers with access to the configuration tool Alfabet Expand can customize the range of objects that a user can select as the target of a reference property. The range definition can either limit the target of the relation to a defined object class or object class stereotype or to a range of objects defined via a query. The allowed range can be defined either on the object class property defining the reference or in the class settings for the object class or object class stereotype that the range definition shall apply to.
In Alfabet 11.7, the elements in the user interface and the meta-model configuration objects that they are based on differ considerably from Alfabet 10.15. Migration of an existing Alfabet implementation is therefore very complex. It is strongly recommended that you consult Software GmbH for help in order to migrate the configuration of your Alfabet installation.
If you have implemented the Enterprise solution configuration (Accelerator), it is recommended that you use the preconfigured solution provided with Alfabet 11.7 as a starting point and adjust it to include the custom configurations that you have made. This may also be a more efficient method to migrate if you are an Enterprise customer with considerable customization of your solution.
If the existing user interface and meta-model configuration should be migrated as-is, the update of the meta-model via the AMM file will automatically update part of your configuration. Documentation of the changes is available under Migration from Alfabet 10.15 to Alfabet 11.7.
Please note that typically the automated migration process does not result in the complete migration of the Alfabet 10.15 user interface configuration. For example, widget reports must be re-implemented by defining cards using the new card definition capabilities available in data workbenches and the views to configure indicator types and evaluation types.