Skip to end of metadata
Go to start of metadata

Customizations to a metamodel first need to be validated and then previewed before they can be applied to a tracked or shared model package, or exported to the tool configuration. You can choose to skip validation before implementing the customizations, but if you do, validation will automatically be performed when you start to apply or export the customizations.

During validation, there is the opportunity to assign your customized metamodel a version, in addition to the standard base version of the metamodel. Assigning a custom version is optional. If you validate without assigning a version, a warning message will appear to make you aware, but it is not blocking.

To illustrate the validation procedure, the following example is used:

Example

You have modeled a custom profile definition "organization unit" for the business actor concept, including an attribute for the number of staff.

Validating customizations

  1. On the Metamodel tab, in the Check group, click Validate.

  2. If your metamodel does not have a custom version assigned, a message window appears asking you if you want to set a version.

    Click Yes if you want to assign a version. In the window that appears, enter a custom version, and click OK.

    Click No if you do not (yet) want to assign a version. You can always assign a version after validation if desired.

    If your metamodel already has a custom version, the message will not appear. To update your custom version, you can change it later via the metamodel package's Properties window.

  3. Validation is performed. Depending on the result, do as follows:

    • If validation is successful, the following message appears:



      Click OK, and proceed to previewing the customizations.

    • If validation fails, a message appears showing the number of errors and warnings. Example:



      Click OK, and check the Messages window for error messages  and/or warnings . Example:



      Select a message line in the window to navigate to the element causing the problem. Enterprise Studio will show you the corresponding element in the view. For more information about navigating the Messages window, please refer to Navigating the Messages pane.

      Fix the problems in your customizations and validate your changes again. Errors need to be fixed before you can continue. Warnings are not blocking, but you need to be aware of them if you decide to continue.

      Outdated metamodel version

      If the validation message indicates that the metamodel is based on an older tool version, as shown in the above example figure, it means that your configuration has not been upgraded. In that case, apply your changes to the Team Server model package, and close the metamodel package without saving it. After that, upgrade the configuration of the Team Server model package. If you want to continue customizing, you can open the metamodel again via the Manage Configuration tab.

Previewing customizations

After your customizations have been validated, check if they meet your expectations by previewing your customizations. If they don't, make adjustments and revalidate and preview the customizations.

  1. On the Metamodel tab, in the Check group, click Preview. A new, empty "Test Model Package" is added to your model browser.

    Enterprise Studio may first request you to close the model package you started with when opening the metamodel. Once you have closed this original model package, and then close the message window, the new test package is opened.



  2. In the test model package, create a new model with a view or diagram in which you can try out the customizations. A few examples:

    • Create an object and check if the profile is available that has been created for it.
    • Check if the attributes of a custom profile work as expected.
    • Verify that you can set the correct values for an attribute.
    • Verify that the custom documentation field is present for the object it is defined for.

  3. If you are satisfied with the results, close the test model package without saving the changes.


Now you can apply or export the customizations.