Changes to the configuration of the class model
- The XML object ObjectStateManager has been removed. Object state values are now defined in the protected enumeration ObjectState. You can now add object states, change the caption of the object state, and provide a hint, icon and background color for the visualization of the object state.
- A new Access in User Interface attribute is available for object class properties. It defines whether the object class property can be set by the user, is ReadOnly or hidden on the user interface. The setting of the Access in User Interface attribute can be overwritten in the class settings.
- The Access in Data Workbenches attribute has been removed from object class properties. Data workbenches do not have specific access permissions but obey the access permissions set for the property in general with the Access in User Interface attribute.
- The Access in User Interface attributes of the object class properties of the DataQualityRule and DataQualityRuleGroup object classes have been set to ReadAccess. Only administrative users define new data quality rules and data quality rule groups. Restricted ReadOnly access is therefore the standard for most user profiles. The access permissions can be changed for administrative user profiles in the class settings used for these user profiles.
- A standard set of buttons is available for data workbenches and content areas, like the button to create a new object and the the buttons for structuring and visualizing the content of a data workbench. If other class specific buttons are available for an object class, these are listed in the object class model in the Generic Operations sub-folder of the object class. The buttons cannot be edited or deleted. You can only change the user access permissions for each button with the Access in User Interface attribute. The permissions and captions defined in the object class model are the default for all user profiles. For individual user profiles, the settings can be overwritten in the class settings. Click for detailed information.
This feature is not fully implemented with Alfabet 11.6. The buttons are only available as generic operations for a subset of the object classes. In the transition phase, the buttons defined via the object profile specified in the class settings is used for display of buttons for operations not yet available in the class model. For class-based content areas, buttons from an object profile can also be added by assigning the object profile to the content area.
- Object class properties can be assigned to object class property groups with the new Property Group attribute. Click for a detailed explanation of the concept of property groups and a description of the required settings.
- The object class properties Is Variant (Variant ) and Variants (Variants ) have been removed from the object class Application. The definition of variants is exclusively stored in the remaining Variant OfVariantOf object class property linking to the application the current application is a variant of.
- The object class attributes related to the AlfaBot usage have been removed from the object class attribute window.
- In the ALFA_MM_CLASS_INFO table the AlfaBot related attributes of object classes have been removed.
- The ALFA_PM_* classes storing information about the current configuration have been removed from the meta-model. The ALFA_PM_* object classes storing information about the current configuration of the Alfabet solution have been removed. The functionality to generate the information in the object class database tables has also been removed. This also includes the ability to configure the server alias to perform automatic update of these tables during restore of t database or update of the meta-model.
- The following object classes are related to obsolete functionalities and have been removed:
- ALFA_COMPONENT_CTG_DEF
- ALFA_DEMANDMANAGER_DEF
- ALFA_EXCEL_INTEGRATION_DEF
- ALFA_EXTERN_REPORT
- ALFA_USER_EXTERNREPORT
- ALFA_INSTANCE_EXPORT_DEF
- ALFA_OBJECTMAP_DEF
- ALFA_OLD_AUDIT
- ALFA_PATCH
- ALFA_ROLEMANAGER
- ALFA_STANDARD_IMPORT
- ALFA_STATEFLOW
- ALFA_USER_SQL
- ALFA_CHATBOT_PROCESSED_PHRASES
- ALFA_CHATBOTCONVERSATION
- The maximum allowed number of columns in the database table of an object class has been changed from 255 to 512. This number is not identical to the maximum number of allowed object class properties. If translation is activated, definition of a single string property will result in multiple database table columns to be created, one for each language.
- The new object class ALFA_CONTENTAREA_USAGE stores the user configuration of the content area. The user configuration of data workbenches is stored in the database table ALFA_VIEW_CONFIG . The concept behind this is to obsolete ALFAOBJECTUSERSETTINGS in the future and store the user specific configuration in a different database table for each type of configuration object.