Change Detail Preview Area

The preview area next to the thumbnail can be changed. This example removes the status field and adds the last change user instead.

Example Screen:

Definition (product.detailoverview.xml)

Two column layout with language picker

Example screen:

Definition (product.detailtab.xml):

Two column layout with fixed language

Example screen:

Definition (product.detailtab.xml):

Variables support for detail tabs

${user.language} variable could be used as logical key to specify UI language for details tabs.

Definition (product.detailtab.xml):

Detail Tab with specific attributes

Instead of showing all attributes you can also add a fixed list of attributes to a tab. You can also mix attributes with normal fields by adding them to different field groups. If the attribute doesn't exist for the selected item or product, the widget is not rendered. That means, that users can create or edit attribute values but cannot create new attributes by themselves.

Example that shows the attributes Width and Height (product.detailtab.xml):

Detail Tab and editing multi-value attriubte values

There is an an "extra editing mode" for multi attribute values in web, which loads them in an single attribute editor to be able to edit an single value of the list of values identified over an logical key identifier enum. To trigger the new multi attribute in single editor mode, specify an identifier enum with the attributes values identifier logical key, this activates the new mode, if no enum is specified than the standard multi attribute editor in multi mode is used. Don't forget to change the default value of the logical key to an value from the enumeration.

Activating the multi-value attribute editor by specifying an identifier enum in the repository. In the example below the Currency enum was used.

Additionally you need to specify a logical key combination to refer to an attribute value in the webs detail tab definition XML, this can be done by using an enum grouping for the identifier enumeration and set the identifier logical key to selectable="true". Another possible option is to specify each logical key combination as an extra field group.

Using an enum grouping to handle all combination of logical keys by an combobox.

Alternatively using extra field group for each combination of logical keys.

Logical Keys exploded

Example screen:

Definition (product.detailtab.xml):

Logistic Extension Data with multiple Logical Keys

Use Case:

• Logistic Extension Data has 5 logical keys and can be used to store data to a (sub)set of these keys, e.g. language and customer specific.

Example Screen:

Definition (article.detailtab.xml):

Fullqualified Purchase Prices

Use Case:

Allow viewing and editing of full qualified prices. Note: Listing of all available prices is not possible using XML definitions.

Example Screen:

Definition (product.detailtab.xml):

Editable Item Preview Panel

Use Case:

Allow fast editing of very often needed fields without having to switch tabs, e.g. Status field.

Example Screen:

Definition (product.detailoverview.xml):

Display Structure Group Assignment

Use Case: Display the structure group assignment of a given structure system.

Example Screen:

Definition (product.detailtab.xml):

Editable List of Sub Entities

Use Case: Show a list of all available subentities to an entity (e.g. item) and provide CRUD functionality.

Example Screen:

Definition (article.detailtab.xml)

Editable List of Retail Prices for Items

Please note that only basic editing functionality for prices is supported. As of version 7.1, the following restrictions exist:

• Price tiers are not handled correctly, ie. price list doesn't automatically show all available price tiers as columns like in Product 360 Desktop. Hence, only a single price tier is supported.

• Custom fields cannot be edited due to a bug.

Example Screen:

Definition (article.detailtab.xml):

Display Transition Fields in Detail Tab Lists, e.g. Short Description for References

Lists within detail tabs also support transition fields. This is especially useful for the list of referenced items.

Example:

This example requires to create two new transition fields in repository (3 in case of 3-tier product paradigm). Please see the screen for details.

product.references.listmodel.xml

Single Logical Key Selector for Multiple Subentities

Use Case:

In some cases, multiple fields from different sub entities should be displayed on a single detail tab. If these fields belong to the same entityType, the user wants to select the logical key only once instead of multiple times. This also makes sense, if different subentities share the same logical key, e.g. a qualification by language.

Per default, logical key selectors are generated per fieldFormGroup. Fields from different subEntities need to be grouped in seperate fieldFormGroups. Using the syntax "enumGrouping" allows to extract the logical key selector from the fieldFormGroup level to the column level.

Example:

Two price values from ArticlePriceValuePurchase and ArticlePriceValueSales subentity with shared Currency selector:

article.detailtab.xml:

List of all references to items, but not to other entities (with optional filter)

Shows a list of all references to other items together with GTIN and ShortDescription using transition fields.

Example Screen:

article.detailtab.xml:

List of references to products, that is additionally filtered to show only references of type "accessories":

Example Screen:

product.detailtab.xml:

Example for combination of <fieldGroup> and <tableGroup> in one custom tab

In the case, that the page length of the defined table will be around 100 and you want to use fieldGroup and tableGroup as a combination in the same custom tab together a fetchSize should be defined for the table that roughly matches the table records. This will allow the table to grow to the max of records stored and up to the defined fetchSize number.