Third level hierarchy

In our example ArticlePackagingMaterial is a third level hierarchy entity (Article → ArticlePackaging → ArticlePackagingMaterial). When having a third level hierarchy in the repository it is necessary to use another value at the class text field because the content which is shown in the ArticlePackagingMaterial view should depend on the selection made in the ArticlePackaging view.

The TableView which we have to use is: com.heiler.ppm.article.ui.view.ArticleDomainBasedThirdLevelTableView

So the configuration for the third level hierarchy view looks like this:

Adding views to a perspective

To add a view to an existing perspective you have to add a contribution to the perspectiveExtensions extension point.

1. The target id of the contribution perspectiveExtension has to be the id of the perspective where you want to make the modifications. In our example we want to add a view to our "ArticlePackagingPerspective" we created in the section above. So we use the id com.custom.perspectiveandview.ArticlePackagingPerspective. We can then right click the perspective extension contribution and add a view.

2. In the "Extension Element Details" (2) we can then fill the values for the view. More information about the creation of perspective extensions can be found in the "Creating custom perspectives" section (chapter "Customizing") in the document "Informatica MDM - Product 360 - <VERSION>- Knowledgebase, Installation and Customization".

Adding standard views to a custom perspective

When creating a new perspective most of the time it is necessary to add standard views like the Article table (Items #1) or the Context selection view to it. To do this, the same procedure for adding views in the perspectiveExtension has to be done.

The view ids can be found in the plugin.xml of standard com.heiler.*.ui plugins.

Extend a standard GDSN perspective with custom views

It is possible to add a view to a standard GDSN perspective. To do this the same procedure like adding views to perspectives is used. That means only a contribution to the perspectiveExtensions extension point is needed. To add for example a view to the GDSN core perspective, the id "hlr.gdsn.ui.perspective.GDSNCore" has to be declared in the relative value in the "Extension Element Details".

All perspective and view ids from GDSN can be found in plugin.xml of the com.heiler.ppm.gdsn.ui plugin.

Adding a new field

When only adding a new field to an existing module just add the tag field with the identifier of the new field to the already existing field group or table group.

Adding a new module

Depending on the module, you can choose between a field group and a table group.

A field form group can be seen as a single field list. We will use the fieldGroup for the ArticlePackaging and ArticlePackagingUOM entity.

Make sure to use the field identifier from the custom area of the repository.

The result will look like this:

For the sub entity ArticlePackagingMaterial we will use the tableGroup to show the fields in a table.

The result will look like this:

Note that the action panel, marked in red, has to be explicitly declared in the XML as actionButton to be shown.