Actions Check

The 'Actions' part of Metamodel check checks if no node properties exist for a node that is not marked as 'customizable' (this could happen if node properties had been created for a previously customizable node which was then made 'non-customizable'). In such a case, node properties are deleted (if metamodel check 'Repair' is enabled, otherwise deletion is suggested in the metamodel check log).

Similarly, node properties are checked for duplicates. For each node/action combination, no more than one instance of node properties can exist. If duplicate node properties are found during metamodel check, only one instance is kept and the rest deleted (or deletion suggested, same as above). This can be used, for example, to fix duplicate action assignments resulting from running the 'catalog copy' operation (with action copying enabled) on a catalog with nested action assignments.

About duplicate action assignments

Duplicate action assignments may occur when a catalog whose action assignments formed sub-menus (e.g. catalog right-click context menu item 'Print' contained actions 'Print', 'Print to PDF' and 'Print with') is copied with action assignments and the copies of action assignments in the sub-menus remain assigned to the original catalog, thus representing duplicates in the original catalog and missing in the new catalog. Metamodel check makes sure that all action groups contain actions from the same action set. If the nested action is in a different action set, it is updated to be in the same action set as the group.