Installation of Alfabet 11.13 installation deviates from previous Alfabet 11 releases:

  • The ContentSecurityPolicyValue setting in the alfasettings.json configuration file of the Alfabet Web Application has been amended with form-action: 'self'; base-uri: 'self'; in all example files delivered with the Alfabet Web Application. It is recommended to take this setting over for the alfasettings.json file in the config directory of the Alfabet Web Application to enhance security.
  • Duplicate entries for class configurations were written to the CLASSCONFIGURATIONS table because the unique key configuration did not take class stereotypes into account. The unique key has been changed to include the stereotype name. During the migration to Alfabet 11.13, the CLASSCONFIGURATIONS table will be scanned for duplicates and the older entries will be removed. The respective entries in the ROLETYPECONFIG table storing the role type configuration for the class settings will also be removed. Warnings are written to the meta-model update log file.
  • While it has not been possible to manually create multiple user profiles with the same name, validation for duplicate user profile names was missing in certain import mechanisms. A database-level uniqueness constraint has been introduced for user profile names to strengthen data integrity. During the update to Alfabet 11.13, any duplicate user profile names detected are automatically renamed with the suffix _dup. All affected profiles are documented in the meta-model update log.
  • The storage location for configured report button overrides has been moved from the Presentation Objects node to the Reports node of the class settings. Existing report button overrides have been automatically migrated to the new location to ensure consistency and preserve all existing configurations. The Configure Buttons functionality has also been updated to store and maintain button overrides in the Reports section, ensuring that changes made through the user interface persist correctly.
  • Stereotypes have been introduced for data-triggered action rules. The View-Based Data-Triggered Action Rule rule type enables the execution of data-triggered actions in standard views in response to button and inline editing interactions. For button-based actions, the data-triggered action is executed in the context of the object on which the button operates. For inline editing scenarios, the action is executed in the context of the base object of the class-based content area in which the view is embedded. This enhancement enables automated processing and validation logic to be applied directly during user-driven data changes.

    The Operation-Based Data-Triggered Action Rule stereotype has been introduced for existing data-triggered action rules targeting data workbenches and content areas. On migration to Alfabet 11.13, all existing data-triggered action rules will be automatically migrated to the Operation-Based Data-Triggered Action Rule stereotype.

The Alfabet components must be installed in an empty directory. If you have already installed a prior release or patch release of Alfabet and want to install the components in the same location, the existing files must be removed from the installation directory prior to the installation of Alfabet. It is recommended to save a backup of the configuration files in another location, empty the Alfabet installation folder, install the new release via the installer, and add the stored configuration files to the new installation.