Familiarizing Yourself with Verify Options

An abstract stereotype should not be used for a real element. Create templates and menus should not exist for abstract stereotypes within the configuration. A permissible stereotype should be used for the element. The reported elements should be deleted within the configuration or the stereotype should be marked as not abstract.

Views: Templates, Menus

Description: an abstract stereotype should not be used for a real element. This means that there are also no templates for an abstract stereotype. All menus below abstract stereotypes are also superfluous as a diagram should not exist for this stereotype. Either the menu or the create template is marked.

Troubleshooting: deleting reported elements or marking stereotype as not abstract.

The configured display options are verified for stereotypes of diagrams. If this produces a verify message, the stereotype in the profile currently being viewed is selected and the profile is listed as a name. The Edit/Display Options dialog can be opened for this selection. All display options with errors are delivered in the Verify Messages tab (or root tab for an element which is similar to diagrams); these can then be jumped to using an icon.

Views: Stereotypes

Description: the configured display options are checked for the stereotypes of diagrams and elements which are similar to diagrams (e.g. activities). If this produces a verify message, the stereotype in the profile currently being checked is selected and the profile is listed using names.

Troubleshooting: Jump to stereotype and open the Edit/Display Options dialog. All display option components with errors are delivered in the Verify Messages tab (or root tab for elements which are similar to diagrams); these can then be jumped to using an icon.

Only one element can be created for a non-abstract stereotype if at least all configurable existence prerequisites are also configured. Each stereotype is only viewed in the owning profile. However, configurations can be distributed to any number of profiles. The stereotype should be marked as abstract if it is only used for structuring properties. The relationship role given should be configured before you can use the stereotype. If it is not, then the stereotype can also be deleted; the root stereotype can never be deleted.

View:Relationships

Description: only one element can be created for a non-abstract stereotype if all configurable existence prerequisites are also configured. Only the non-abstract stereotypes which are in the current profile as its own contents are taken into consideration. However, the configuration can be in any number of profiles.

Troubleshooting: the stereotype can be deleted if it should not be used. Root stereotypes cannot be deleted.
The stereotype should be defined as abstract if it is only used for structuring properties. Checks are not carried out for abstract stereotypes.
The relationship roles named in the message need to be configured if the stereotype is to be used. Otherwise it is not possible to create an element with this stereotype.

Note: only stereotypes which are in the current profile are examined. Imported stereotypes from other profiles are not examined. This means that stereotypes are only evaluated once and pre-defined root stereotypes do not report missing configurations even though you may not wish to work with the element types.
The relationship roles being searched for can be configured in any profiles. Do not generally assume that all relationships are always created in the same profile.
If the profile is not imported properly it is still possible for the configuration to be incomplete in a model package, despite the fact that no verify message appeared.

Special cases:

• Diagram contents is also required for stereotypes of diagrams, even though it is not an existence prerequisite. However, diagrams without permissible diagram contents serve no purpose.
• Constraints require configuration of constrained elements, otherwise they also serve no purpose.
• Instances require configuration of classifiers, otherwise instances cannot be created by classifiers.
• The exception handler requires exception types to be configured, otherwise the handlers cannot be used.

You can set a maximum file size for file extensions in the configuration.

Views: Stereotypes

Description: you can set a maximum file size and file as template for every file extension of artifact stereotypes. The verification finds the files extensions which exceed the maximum value for the file size.
This can normally only occur if the file is initially imported and then the size is limited.
A maximum size of 0 means that there is no size limit.

Troubleshooting: import a smaller file or customize the size limit.

Mapping between two types is always stored for the type which is lower down in the profile's import hierarchy. If this procedure is not adhered to, a message appears. Reverse the import relationship direction to fix this.

Views: Type Systems (only relevant for Innovator for Information Architects)

Description: mapping between two types when configuring Innovator for Information Architects is always stored for the type which is lower down in the profile's import hierarchy. If this procedure is not adhered to, a message appears.

Troubleshooting: reverse import relationship.

Mapping between two types can only connect types which have profiles which are linked using import hierarchy. Erroneous mappings should be deleted or extended to include the missing profile imports.

Views: Type Systems (only relevant for Innovator for Information Architects)

Description: mapping between two types when configuring Innovator for Information Architects can only connect types which have profiles which are linked using import hierarchy.

Troubleshooting: delete mapping or extend to include missing profile import.

Elements from various profiles are often used in the configuration. e.g. stereotype as basis for a create template that will then be used as a menu command. You need to ensure that all elements used can also be accessed by importing profiles.

Views: Stereotypes, Relationships, Templates, Verification Routines, Menus

Description: ensure that elements used in a profile are also recognized in all views.

• Stereotype: super stereotype
• Description: stereotype on the other side of the relationship
• Templates: stereotype, stereotype property, labels and texts
• Verification routines: stereotypes
• Menus: stereotypes of the menus and all menu commands

Troubleshooting: extend import between the profiles or delete elements containing errors.

All menus included are checked to see whether they have at least one menu command. If a menu does not have a menu command, it is selected. Empty menus are not available in any interfaces and are, therefore, superfluous. Empty menus can be deleted or filled with menu commands.

Views: Menus

Description: all menus included are checked to see whether they have at least one menu command. If a menu does not have a menu command, it is selected. Empty menus are not available in any interfaces and are, therefore, superfluous.

Troubleshooting: delete empty menu or assign menu commands.

A post-processing command is not possible for the preview window and docu repository output formats. The post-processing command should be deleted or the output format changed.

Views: Documentation

Description: a post-processing command is not possible for the preview window and docu repository output formats.

Troubleshooting: delete post-processing command or change the output format.

The menu commands are given unique names internally but the name shown is localized and not automatically given a unique name. The menu commands could also have been adopted in various profiles in menus of the same name. The verify option collects all menu commands as if they were offered for one diagram. Menu commands of menus with the same name are combined into one menu. If there are then various menu commands in a menu with the same name, a message appears for each menu command assigned in this profile and the menu command is selected. The verify option checks both the English and German menu commands in the interface, regardless of which language is being used in the configuration editor. The affected menu commands should either be renamed so that they are unique or removed from the menu.

Views: Menus

Description: the menu commands are given unique names internally but the name shown is localized and not automatically given a unique name. The menu commands could also have been adopted in various profiles in menus of the same name.
The verify option collects all menu commands as if they were offered for one diagram. Menu commands of menus with the same name are combined into one menu. If there are then various menu commands in a menu with the same name, a message appears for each menu command assigned in this profile and the menu command is selected.
The verify option checks both the English and German menu commands in the interface, regardless of which language is being used in the configuration editor.

Troubleshooting: either rename the menu command so that it is unique or remove the menu command.

All create templates' menu commands are checked to see whether the menu's contents is allowed. If this is not the case, the problematic menu command is selected. The message may appear because a menu command is no longer allowed due to a change in the contents configuration.

Views: Menus

Description: the create templates' menu commands are checked to see whether the menu's contents is allowed. If this is not the case, the problematic menu command is selected.
The message may appear because a menu command is no longer allowed due to a change in the contents configuration.

Troubleshooting: check whether the contents configuration still allows the respective element. The contents configuration might have e.g. been changed by a profile import being deleted.

Relationships can be configured for a selected stereotype in every profile. Combining both the stereotypes and relationship roles involved within a profile is unique. If configured relationships are recognized due to the profile import, these are no longer provided when creating within the profile being viewed. Relationships may appear twice if you configure relationships in the current profile and then import another profile. These verify options detect these double relationships. Relationship multiplicities are not evaluated during verification. These can therefore sometimes be different. Relationships which are configured twice are superfluous; you can delete one of the relationships.

Views: Relationships

Description: relationships can be configured for a selected stereotype in every profile. Combining both the stereotypes and relationship roles involved within a profile is unique. If configured relationships are recognized due to the profile import, these are no longer provided when creating within the profile being viewed.

Relationships may appear twice if you configure relationships in the current profile and then import another profile. These verify options detect these double relationships.

Troubleshooting: relationships which are configured twice are superfluous; you can delete one of the relationships.

Note: relationship multiplicities are not evaluated during verification. These values, therefore, vary.

The Details configuration is evaluated at all levels and components. A message appears if corresponding Details configurations exist. Verification is not limited to the profile imports available; it always verifies all existing profiles. You should check whether you can merge duplicate configurations into a common imported profile.

Views: Documentation Structures

Description: the Details configuration is analyzed at all profiles, levels and components. analysis is carried out on the selected profile to determine whether its Details configurations occur more than once in the model. Duplicate Details configurations are merged upon evaluation. Editing may lead to differing Details configurations even though you meant to make this general change. The differences which occur mean that the configurations are no longer considered duplicates and may be displayed differently in Details.

Troubleshooting: move duplicate Details configurations in one common used profile.

The structure is checked for the configured relationships. If a relationship was not configured, a message appears. Non-configurable relationships are ignored. You either need to adapt the documentation structure or the configuration for the relationships to fix this problem.

Views: Documentation Structures

Description: the structure is checked for the configured relationships. If a relationship was not configured, a message appears. Non-configurable relationships are ignored.

Troubleshooting: either the documentation structure or the configured relationship is right. Depending on which, customizations need to be made.

The structure is checked for the configured relationships. If a relationship was not configured, a message appears. Non-configurable relationships are ignored. The filter used is also verified. You either need to adapt the documentation structure or the configuration for the relationships to fix this problem. If necessary, correct the filter.

Views: Documentation Structures

Description: see previous verify option; the only difference is that the set filter is also checked here.

Troubleshooting: correct the filter.

One value should be set for each the name property, text property, icon property, stereotype property and all font entries in the configuration for display options. Properties with no value can be deleted or a value can be entered for them.

Dialog for Display Options

Description: the value range for display entries, such as display name, text property, icon property, stereotype property and all font entries, is derived from other components of the configuration or model. When creating such an entry, a value is not automatically assigned and no default value to be used is set. You can jump to the entries with errors in the dialog.

Troubleshooting: set value or delete entry.

Note: the verify option is called within the "The display option in the 'Name' profile is inconsistent" verify option to ensure display option consistency.

A message appears for non-abstract stereotypes if a create template does not exist for this stereotype in any profile. Elements cannot be created with this stereotype if there are no create templates which could make the stereotype superfluous. Create a create template so that this message no longer appears. The stereotype should be defined as abstract if it is only used for structuring.

View:Templates

Description: a message appears for non-abstract stereotypes if a create template does not exist for this stereotype in any profile. Only the stereotypes which are in the current profile as its own contents are taken into consideration. However, create templates can be in any number of profiles.

Troubleshooting: you first need to decide whether this stereotype is necessary or not. This stereotype can be deleted if you no longer need it. Please note that it is not possible to delete the root stereotype.

Maybe the stereotype is only used for structuring properties and should, therefore, be described as abstract. This check is not carried out for abstract stereotypes.

If the stereotype is to be used it is assumed that you want to create elements with this stereotype. This is only possible with create templates. The message can be resolved by creating a create template.

Note: only stereotypes which are in the current profile are examined. Imported stereotypes from other profiles are not examined. This means that stereotypes are only evaluated once and root stereotypes pre-defined by MID do not report missing create templates even though you may not wish to work with the element types.
Create templates being looked for can be in any number of profiles. Do not generally assume that create templates are always created in the profile which the stereotype was also created in.

Action sequences are always initially created with an engineering action. Any number of further actions can be created or deleted within a sequence. A sequence without actions does not really serve a purpose as the actual function of the sequence is set using actions. The action sequence can be deleted or a new engineering action can be created within the sequence.

Views: Actions

Description: an engineering action which can be called using a menu command is an action sequence which is made up of one or more actions. An action sequence is always initially created with an action. Any number of further actions can be created or deleted within a sequence. a sequence without actions does not really serve a purpose as the actual function of the action sequence is set using its actions.

Troubleshooting: delete the action sequence or create actions within the action sequence.

Verifications can be activated for each chapter. A verification routine needs to be given in these verifications. If this verification routine is missing, this message appears and the verification chapter is selected. A verification can be assigned to the verification chapter to fix this problem or the verification chapter can be removed.

Views: Documentation Structures

Description: verifications can be activated for each chapter. A verification routine needs to be given in these verifications. If this verification routine is missing, this message appears and the verification chapter is selected.

Troubleshooting: assign a verification to the verification chapter or remove the verification chapter.

You first need to configure some existence prerequisites to be able to use a stereotype for an element. It is also necessary to fulfill certain other constraints for some element types; this then causes a special message to appear. Other relationship roles need to be configured to fix this problem.

View:Relationships

Description: if a stereotype did not get a message for the "The 'Name' value is not permitted [VFY418]" verify option, this check can also be carried out. Depending on the element type, configuration of relationship roles is examined more closely and a special message appears if there is a problem.

Troubleshooting: the problem stated in the message which appeared can be resolved by proper configuration of the relationship roles.

Special messages for certain element types:

• CLGeneralization element type

  • "Name" 'Owner' cannot specialize any of the stereotypes defined as 'target'.

    A stereotype which can be specialized should be given as target for each configured owner. Stereotypes of the same or generalized element types can be specialized.

  • "Name" 'Target' cannot specialized by any of the stereotypes defined as 'Owner'.

    As above; the only difference being that the configured targets are checked.

• CLAssociation element type

  • Attributes are not permitted for 'Assigned Elements'.

    Attributes need to be assigned to associations as roles using assigned elements.

  • No 'type' is permitted for "Name" 'assigned elements' of the attribute element type.

    Types need to be assigned to the associations' roles.

  • Association with actor as 'type' of a permissible role needs to have classes, components or use cases as other 'types'.

    Associations to actors can only be created with binary and need to be connected with classes, components or use cases.

  • A specialization of nodes as a 'type' of a permissible role needs to be defined for the communication path.

    Communication paths can only be created as binary between node specializations.

• CLInstanceSpecification element type

  • Is defined as instance specification of "Name" association but no slot is permitted for 'Assigned Elements'.

    Slots need to be configured as contents for instances of associations, otherwise the association cannot be created as an instance.

• CLConnector element type

  • Connector ends are not permitted for 'Assigned Elements'.

    Connector ends need to be assigned to connectors using assigned elements.

  • No 'role' is permitted for "Name" 'Assigned Elements' of the connector end element type.

    Types need to be assigned to the associations' roles.

• IMKey element type

  • Features are not permitted for 'Assigned Elements'.

    Features need to be assigned to both unique and foreign keys as contents, otherwise the keys cannot be linked with attributes or table columns.

• ERRelationship element type

  • Roles are not permitted for 'Assigned Elements'.

    Roles need to be assigned to relationships using assigned elements.

  • No 'type' is permitted for "Name" 'Assigned Elements' of the role element type.

    Types need to be assigned to the relationships' roles.

• SMStateMachine element type

  • Regions are not permitted for 'Assigned Elements'.

    State machines need to permit a region as contents.

• ANAction element type (specialization)

  • Input pins are not permitted for 'Assigned Elements'.

  • Some actions' types require input pins and should allow these as contents.

  • Output pins are not permitted for 'assigned elements'.

  • Some actions' types require output pins and should allow these as contents.

  • Triggers are not permitted for 'assigned elements'.

  • Some actions' types require triggers and should allow these as contents.

All of a profile's content should be used in one way or another. If not, then the content may be superfluous and should be deleted. Stereotypes, stereotype properties, labels and texts are used so that a value should be set for an element. At least one occurrence should exist as a menu command for create templates, verification routines, engineering actions and documentation commands. Please note particularly for create templates that uses in dialogs cannot be verified. Engineering actions that should be used for the search are not reported.

Views: Stereotypes

Description: all stereotypes, stereotype properties, labels, texts, font-color elements and selection filter which were defined within the profile being viewed are checked. Each entry being viewed is checked to see whether there is an element which uses this entry.
If this is an abstract stereotype there will obviously not be an element. The message appears regardless of whether an abstract stereotype was specialized or not.
The use of the individual values are also checked for labels and stereotype properties with enumeration types.
An entry is recognized as being used if it an instance within a create template.
The fixed predefined root stereotypes are not included in this verification.

Troubleshooting: entries not used may be superfluous. However, you should take into consideration the fact that the configuration is constructed in such a way that the model itself is still fairly empty.

Views: Templates, Verification Routines, Actions, Documentation

Description: create templates, verification routines, engineering actions (action sequences) and documentation commands are checked to see whether they are used as menu commands. They don't necessarily have to be used in the same profile.
Action sequences can be identified for use in the search. These sequences are not reported.

Troubleshooting: if they do not exist as menu commands you need to find out whether the element affected is really needed or not. Perhaps you only forgot to create the menu command. Take into consideration for create templates that a template won't be used as a menu command but e.g. is assessed when creating a new entry via the Edit/Properties dialog. This dialog appears e.g. for parameters below operations.

The element is only included in the model as a dummy element Linked elements often need to be created as dummy elements when importing version objects. This is to ensure that all connections are correctly created. These dummy elements are only created as incomplete. The dummy element's version object needs to be imported to fix this problem. It may be enough to reset the corresponding property for this. You need to be aware that the element probably is not complete.

Views: Stereotypes, Templates, Verification Routines, Actions, Documentation

Description: profile contents can be created as incomplete when add-on templates are loaded or version objects are imported. This can occur for stereotypes, stereotype properties, labels, texts, documentation components or all entries which can be used as menu commands.

These elements can be identified by a special icon (general danger area) in the configuration editor.

Troubleshooting: the profile affected can be loaded as an add-on so that the incomplete entries can be extended.
It is sometimes sufficient to reset the placeholder marker for the respective element using the properties dialog; it is, however, not recommended.
By doing so, you can also delete incomplete checked-in elements. Please not that a stereotype cannot be deleted until all places where the stereotype is in use in the model are deleted.

Profiles can import any number of other profiles. All contents of the imported profile are recognized in the current profile upon import. This also applies for transitively importing profiles. If a profile imports another profile both directly and transitively, direct importation is superfluous and can be removed.

View: all

Description: profiles can import any number of other profiles. All contents of the imported profile are recognized in the current profile upon import. This also applies for transitively importing profiles.

If a profile imports another profile both directly and transitively, direct importation is superfluous.

Troubleshooting: direct import can be removed using the dialog. There are certain prerequisites which make it necessary to remove the profile's import which transitively imports the other package. However, it is then mandatory that no contents from this profile is used.

If a verification routine is called for a diagram in the model editor, then the 'is inconsistent' message appears if there is an error. If you select this message, the diagram opens and the verification is listed again with detailed messages. This process requires a verification routine that would cause messages to appear in diagrams in the model editor to also exist in the diagram as a menu command.

Views: Menus

Description: verification routines can be set as menu commands in the Innovator model editor engineering menu If a message were to appear for a diagram during the verification routine, this routine would then also be set as a menu command for the corresponding diagram stereotype. If such a verification routine is set as a menu command for the model editor, it should also be set as a menu command for the diagram stereotype. If this is not the case, the message appears and the diagram stereotype is selected.

Troubleshooting: include menu commands in the diagram's engineering menu or modify the verification routine so that it is not longer offered for the diagram.

Background: if a verification routine is called for a selected diagram in the model browser and a message appears for this diagram, the following occurs: instead of all messages appearing, only 'Diagram 'xy' is inconsistent" appears. If you then click on the message, you jump to the diagram, it is opened and the verification routine is then run in the diagram. All messages which lead to inconsistencies then appear in the diagram.
This procedure was selected because errors which result from the diagram's graphical situation can be hardly unavoidable in the dialog in the model editor. It is, therefore, not a good idea to send all messages in the model editor.

it is possible to set your own icon for some elements (stereotypes, values of stereotype properties, create templates, verification routines, engineering sequences, documentation commands, menus). The icons which are available in the interface's corresponding $INODIR/icons icon directory can be found in the dialog. Erroneous file names might creep in due to misspelling in dialogs or migrating from older versions. You need to determine whether it was misspelled or whether the file no longer exists to fix this problem. Note that the server and interface sometimes access different directories.

Views: Stereotypes, Templates, Verification Routines, Actions, Documentation, Menus

Description: it is possible to set your own icon for some elements (stereotypes, values of stereotype properties, create templates, verification routines, engineering actions, documentation commands, menus). The icons which are available in the interface's corresponding $INODIR/icons icon directory can be found in the dialog.
It is also possible to directly enter a name in the dialog; please note that this may lead to typing mistakes. It is also possible that icons were renamed when an update occurred. If an older version is migrated, references are made to icon names which no longer exist. The same thing occurs if your own icons were not transferred during the migration.

Troubleshooting: if a verify message occurs, you must decide whether the icon's file name was written wrong or whether the icon no longer exists in the directory. In the first case, change the name so that it is right; in the second case, either copy the icon file into the directory or select another icon.

Note: the directory used for icon files depends on the value of the INODIR environment variables for interface and server. If the interface and server use different directories here, an error message may occur for the server even though the icon can be shown correctly in the interface. All icons in the $INODIR/icons/default directory are evaluated.

Options can be created in create templates of DB tables and other option-capable element types. Only options which are also defined in the profile of the template being viewed are allowed. The options are no longer available once a create template is moved into another profile. The options used can either be deleted or made accessible to the type system.

View: Templates (only relevant for Innovator for Information Architects)

Description: options can be created in create templates of DB tables and other option-capable element types. Only options which are also defined in the profile of the template being viewed are allowed. The options are no longer available once a create template is moved into another profile.

Troubleshooting: delete the options used or move the type system which contains the options into the new profile.

Erroneous values have been detected in the configuration for display options. These may be invalid stereotypes in rules or values of properties. The values may be invalid if the structuring for stereotypes or the configured relationship roles have been modified.

Dialog for Display Options

Description: invalid stereotype can occur in a rule if profile imports are changed or contents' configuration or other relationships is changed.
Invalid values can also occur for properties as e.g. a generalization between two stereotypes was deleted which made a stereotype property unknown.

Troubleshooting: if the contents configuration is OK, the values of the display options need to be adapted.

Note: the verify option is called within the "The display option in the 'Name' profile is inconsistent" verify option to ensure display option consistency.

An XSL stylesheet is only required for the XML output format in a documentation command. The stylesheet should be deleted or the output format changed.

Views: Documentation

Description: an XSL stylesheet is only required for the XML output format in a documentation command.

Troubleshooting: delete stylesheet or adapt output format.