Debugging

In case of something doesn't work as expected please check the server log file .out.log. Also it might be helpful to enable DEBUG logs for everything related to parsing the XML files. This can be done in log4j.xml in server configuration folder by adding these lines:

Referencing Fields and Logical Keys

When referencing a field or an entity type, always use the identifier from the custom section of Product 360 repository. Only for logical keys, the type name is needed.

Please also note, that logicalKey element is only needed if

• No default value is provided in repository

• A different value than the default value should be used

For example the following list definition references a price field:

Although the price field as multiple logical keys, this is a valid expression as all logical keys have a default in the repository. In this case, the net customer price for EUR with the validity of "now" will be displayed.

To display a price of another type, only the deviant logical key needs to be specified, e.g.

Display Media Asset Thumbnail in Table

The default installation contains the list definitions FULL (EN) and FULL (DE) where the first column displays a thumbnail of the item/product. If the thumbnail is not displayed as expected, please check the corresponding XML file article.listmodel.xml or product.listmodel.xml.

For the thumbnail column, all three logical keys (language, quality and media asset type) need to be set correctly. The default definition references only language and quality and uses the default media asset type from the repository. To specify an alternative media asset type, the field definition should look like this:

Display Media Asset Thumbnail in Form

Entity thumbnail can be specified like this (possible logical keys same as in table definition):

Possible values for thumbnailType attribute is small, normal, big, preview, original(default value).

Display tool-tip in Table

The default installation contains tool-tip enabled for the fields which have rich-text and/or multi-line enabled. For example, Long description fields.

It is also possible to enable or disable tool-tips for other fields. An optional Field Param can be added in the repository to enable or disable the tool-tip for a particular field. The Field Param name is showTooltipInWebTable and it can accept true or false.

Renaming the localization strings

In-order to rename Lists Views, Detail Tabs and Action Menus, it is important to understand the relationship between the Lists Views, Detail Tabs and Action Menus xml and their corresponding i18n properties file.

E.g. Detail Tabs

• product.detailtab.xml → ProductDetailtab.properties, ProductDetailtab_en.properties, ProductDetailtab_de.properties, etc

  • Such *.detailtab.xml holds any tab created using form definition, like "All texts", "Change information", etc.

  • Renaming of such tabs needs to be done in (*)Detailtab.properties and more language specific files

• product.detailtab.custom.xml → ProductDetailtabCustom.properties, ProductDetailtabCustom_en.properties, ProductDetailtabCustom_de.properties, etc

  • Such *.detailtab.custom.xml holds any tab created using custom tab definition, like "References", "Items of the product", etc.

  • Renaming of such tabs needs to be done in (*)DetailtabCustom.properties and more language specific files.

• product.detailtab.parameterized.xml → ProductDetailtabParameterized.properties, ProductDetailtabParameterized_en.properties, ProductDetailtabParameterized_de.properties

  • Such *.detailtab.parameterized.xml holds any tab created using parameterized tab definition, like "Characteristics", "Preview", etc.

  • Renaming of such tabs needs to be done in (*)DetailtabParameterized.properties and more language specific files.

Similarly, the list views and action menus are also localized in similar naming convention.

Setting default 'Filter By' field to 'All Columns ' in the main table search of Web UI

In general, the default 'Filter By' field is selected as the field which is the first column of the List view.

There is also an option in 'Filter By' drop-down stating "All columns" which the users can select. It will run the search across all fields present in the List view.

In order to have "All columns" as the default on the web client, we have introduced new preferences quickSearch.allColumns.preSelected =false

By default, preference is set to false. In case the user wants to see the default as "All columns" then this preference needs to be set true.

You can change it by going into plugin_customization.ini and changing com.heiler.ppm.web.common/quickSearch.allColumns.preSelected