Data

2. Tick on thebutton in the footer to access the action menu.
3. Move the mouse cursor over the option “Data” to show the corresponding submenu.
4. Click on the option “Assign item to other product” to call up the corresponding dialog box.

5. Enter the product number of the target product in the input field “Product number” and click on the SEARCH button. If the search was successful, the product will be shown on the right side of the dialog box.
6. Tick the target product.

• In order to finish the process, click on the ACCEPT button. A success message is shown. The selected item is now assigned to the target product.
• In order to cancel the process, click on the CANCEL button.

The “Assign items to other product“ action can only be used if the data view “Items“ is selected.

Assign multiple items to other product

Using the action “Assign multiple items to other product” you can detach multiple items from one or several products and assign them to a particular target product. To do so, proceed as follows:

1. In the respective product table, tick the product(s) whose items you want to assign to a particular product.
2. Tick on thebutton in the footer to access the action menu.
3. Move the mouse cursor over the option “Data” to show the corresponding submenu.
4. Click on the option “Assign multiple items to other product” to call up the corresponding dialog box.
5. On the left side of the dialog box, the items of the selected product(s) are listed. Tick the items which you want to assign to the target product
6. Enter the product number of the target product in the input field “Product number” and click on the “SEARCH” button. If the search was successful, the product will be listed below the search mask.
7. Tick the target product.

• In order to finish the process, click on the APPLY button. A success message is shown. The selected items are now assigned to the target product.
• In order to cancel the process, click on the CANCEL button.

The “Assign multiple items to other product“ action can only be used if the data view “Products“ is selected.

Merge products

Using the action “Merge products” you can merge multiple products into a specified target product. To do so, proceed as follows:

1. In the product data table of, for example, the “Worklists” app, tick the products you want to merge.
2. Tick on thebutton in the footer to access the action menu.
3. Move the mouse cursor over the option “Data” to show the corresponding submenu.
4. Click on the option “Merge products” to call up the corresponding dialog box.
5. Select the target product from the menu.

• In order to finish the process, click on the APPLY button. A success message is shown. The items of the source items will be assigned to the target product. The source products still exist. But they don’t have items anymore and their name bears the prefix “Merge_”.
• In order to cancel the process, click on the CANCEL button.

Delete selected items / Delete selection resp. Delete product

The following section is version-specific. From version 5.7.1 onwards, the name of the action has changed and varies depending on the context. Furthermore, the action is now limited to specific apps and tabs. You can use the drop-down menu to view the content for the relevant version.

1. For example, to delete a product, tick the checkbox next to the product in the relevant table .
2. Click on the button in the footer access the action menu.
3. Click on the option "Data" to expand the corresponding submenu.
4. In the submenu, click on the option "Delete selection" to call up the corresponding dialog box.

5. Click on the APPLY button to complete the deletion of the product. A success message is shown.

In the dashboard of the “Product Details” app, the action is called “Delete product”.

3. Click on thebutton in the footer to access the action menu.
4. Move the mouse cursor over the option “Data” to show the corresponding submenu.
5. Click on the option “Generate digital product passport” to call up the corresponding dialog box.

6. From the “Attribute Profile” menu, select an attribute profile*. Following this, the corresponding attributes are shown in the lower area of the dialog box.
7. From the “Locale” menu, select a data locale to determine which language level of localized attributes is taken into the product passport. You can also tick multiple data locales.
8. From the “Partner” menu, select a supplier** to determine which supplier level of supplier attributes is taken into the product pass. You can also tick multiple suppliers.

• In order to In order to trigger the digital product passport creation, click on the ACCEPT button.
• In order to cancel the process, click on the CANCEL button.

• This action requires a project-specific configuration.
• The menu only shows partners if a least one supplier attribute is related to a Narravero attribute profile. And the attribute needs to maintained on at least one supplier level. Additionally, the menu only shows partners which were added to the “Supplier” menu which is situated above the product data table.

• *In order to assemble an attribute profile, you need to go to the attribute configuration of iPIM CC, assign the attribute property Narravero profile to the individual attributes and assign the name of the respective attribute profile to the property as its value.
• **In order to include a digital asset type in an attribute profile, go the “Types” area of iPIM CC and assign the attribute profile name as the value to the type property Narravero asset profile.

3. Click on thebutton in the footer to access the action menu.
4. Move the mouse cursor over the option “Data” to show the corresponding submenu.
5. Click on the option “Create item” to call up the corresponding dialog box.

7. Configure the new item as desired. Menus and input fields marked with an “*” are mandatory.

• In order to create the new item, click on the CREATE button. If the process is successful, a corresponding message will appear.
• In order to create the new item and create further items directly afterwards, click on the CREATE AND CONTINUE button. If the process is successful, a corresponding message will appear.
• In order to cancel the process, click on the CANCEL button.

• If you work with three-stage product structure, the dimensioning attribute (variant attribute) is one of the options to select. If you select an attribut for the product already has a variant, the new item is assigned to this variant. If you select an attribute for which the product does not possess a variant, an appropriate new variant is created and the new item is assigned to this variant.
• If a default unit of measurement is specified for a dimension attribute that has a base unit, the default unit is preselected. Since version 5.5.2: If a category-related unit of measurement is specified for a dimension attribute, this unit of measurement is preselected when creating an item in the respective category.

• This action can only be applied to the initial product. It cannot be applied to a copy of a product.
• The product description (shortDescription) is not copied.

The product number of a copy corresponds to the product number of the initial product, whereby the product number of a copy has a suffix that consists of a consequtive number (-1, -2, -3)..

4. Click on thebutton in the footer to access the action menu.
5. Move the mouse cursor over the option “Data” to show the corresponding submenu.
6. Click on the option “Apply product version” to call up corresponding dialog box.

7. Select the source context from the menu.

• In order to finish the process, click on the ACCEPT button. A success message is shown. The attribute values from the source context are now taken over to the target context.
• In order to cancel the process, click on the CANCEL button.

The “Apply product version” action affects every attribute whose value can be changed. There is no option to select particular attributes.

2. Click on thebutton in the footer to access the action menu.
3. Move the mouse cursor over the option “Data” to show the corresponding submenu.
4. Click on the option “Copy from” to call up the corresponding dialog box.

5. In the “Product number” field , enter the product number of the product whose product data you want to copy.
6. Click on the SEARCH button . Following this, the corresponding product will be shown on the the right-hand side of the dialog box.
7. Tick the product .
8. Click on “Select data” in the upper right corner of the dialog box. Following this, you will be directed to another slider where you can select the data areas which you want to copy.

9. Select a context level from the “Context” menu . This is the context level on which product data is copied.
10. Select a locale from the “Locale” menu . This is the locale level on which product data is copied.
11. Select the data area(s):
    • In order to select a data area, transfer it from the left column  to the right column . To do so, click on the respective data area .
    • In order to deselect a data area, transfer it from the right column to the left column. To do so, click on the respective data area.

• To finalise the copying of product data, click on the ACCEPT button .
  The dialog box closes and a success message is shown.
• To cancel the process, click on the CANCEL button .

By default the property ipim.core.rest.copy.scopes is set to “ALL” which effects that only standard attributes are copied. For example, in order to copy also category attributes you need to set the property to “ALL,CATEGORY”.

• Since version 5.4.3: If this action is applied to an item, it is now possible to select items in the corresponding dialog box.
• Since version 5.5.2 this action can also be used to transfer taxonomies from one product to another.
• The option to select a locale and a contextlevel was first introduced in version 5.7.

Execute report action

Using the action “Execute report” you can apply a report action to the selected product. To do so, proceed as follows:

1. In the respective product data table, tick the products to which you want to apply a report action.
2. Click on thebutton in the footer to access the action menu.
3. Move the mouse cursor over the option “Data” to show the corresponding submenu.
4. Click on the option “Execute report action” to call up the corresponding dialog box.
5. Select a report action from the menu. Then the selection menu “Attributes” and the input field “Value” will appear.
6. Select an attribute from the selection menu “Attribute” and enter a value in the input field “value”.

• In order to finish the process, click on the RUN ACTION button. If the process is successful, a corresponding message will appear.
• In order to cancel the process, click on the CANCEL button.

The “Execute report” action cannot be applied to every attribute scope.

7. Select an attribute from the “Attribute” menu . The generated attribute value is written on this attribute. You can also select multiple attributes.
   • Possibly use the text search to filter the list of attributes by a search term.
8. Select a locale from the “Locale” menu . The generated attribute value is stored on this locale. You can also select multiple locales.
9. Select a context from the “Context” menu . The generated attribute value is stored on this context level.

Before the feature can be used, it is necessary to create an AiHub profile including users with access to the profile. In addition, the corresponding workflows and services must be created along with the respective properties. Regarding this, contact your project manager.

• The right “ipim-portal.actions.texts.generateAiText” is required to use this action.
• Supplier attributes are not taken into consideration when generating attribute values.

It is possible to define taxonomy- resp. category-specific prompts for the AI-supported text generation. For this purpose, you can also define attribute profiles that are used as the basis for the text generation. Click here to learn more.

4. Click on thebutton in the footer to access the action menu.
5. Move the mouse cursor over the option “Data” to show the corresponding submenu.
6. Click on the option “Text generation via AI” to call up the corresponding dialog box.

7. Select a text type from the “Text type” menu. You can also select multiple text types**.
8. Select a text locale from the “Locale” menu. You can also select multiple locales.
9. Select a context from the “Context” menu**.

• In order to finish the process, click on the ACCEPT button. A success message is shown. The text is now generated.
• In order to cancel the process, click on the CANCEL button.

Before the feature can be used, it is necessary to create an AiHub profile including users with access to the profile. In addition, the corresponding workflows and services must be created along with the respective properties. Regarding this, contact your project manager.

• **The option to select a text type and a context was first introduced in version 5.4.3.
• As of version 5.6, the right “ipim-portal.actions.texts.generateAiText” is required to use this action.
• By default, only attribute values on the product level are taken into account for the text production.

• In order to make a text type selectable for the AI text generation, for this text type the type property REST-API: KI-Generierter-Text needs to be set to “YES”. This setting can be done in the “Types” area of the “System setup” section of iPIM CC.
• First introduced in version 5.6.1: The property property ipim.web.generate-ai-text.locales.display can be used which locales are available for this action. The desired locales can be assigned to the property as comma-separated values (e.g. en-GB,de-DE). By default, the property does not possess a value so that the selection of locales is not limited.

*The category attributes of the respective product are used for the text production. Additionally, further attributes can be specified using the property attribute.identifier.textgen. Since version 5.7.1 also attributes on the product level are used to generate texts on the variant or item level.

Since version 5.6 it is possible to define taxonomy- resp. category-specific prompts for the AI-supported text generation. For this purpose, you can also define attribute profiles that are used as the basis for the text generation. Click here to learn more.

7. From the “AI-Template” menu , select a template.
8. From the “Locale” menu , select a data locale. This setting specifies on which language level the generated content is stored.
9. From the “Context” menu , select a context. This setting specifies on which context level the generated content is stored.
10. From the “Text types” menu , select a text type.

• To trigger the content generation, click on the ACCEPT button .
  The dialog box closes and a success message is shown. The product content is now generated.
• To cancel the process, click on the CANCEL button .

Before the feature can be used, it is necessary to create an AiHub profile including users with access to the profile. In addition, the corresponding workflows and services must be created along with the respective properties. Regarding this, contact your project manager.

• Using this action requires a project-based configuration. Regarding this matter, contact your project manager.
• As of version 5.6, the right “ipim-portal.actions.generateAiContent” is required to use this action.

Translation service

You can use an external translation service such as the Google or DeepL to have texts translated. To translate a text dataset of a particular product, proceed as follows:

1. Access the “Product details” app and go to the “Texts” tab.
2. In the product search mask, tick the product or one of its variants or items. Then the corresponding text datasets will be listed in the “Text list” table.

3. In the “Text list” table, tick the text dataset you want to translate.
4. Click on thebutton in the footer to access the action menu.
5. Move the mouse cursor over the option “Data” to show the corresponding submenu.
6. Click on the option “Translation service” to call up the corresponding dialog box.

7. Select the desired target language from the “Locale” menu . Since version 5.6.3 you can select multiple target languages.
8. Select the desired translation service from the “Service provider” menu .

• To trigger the translation, click on the ACCEPT button .
  The dialog box closes and a success message is shown. The selected text is now translated and the translation appears as a new dataset in the text list.
• To cancel the process, click on the CANCEL button .

Before the feature can be used, it is necessary to create an AiHub profile including users with access to the profile. In addition, the corresponding workflows and services must be created along with the respective properties. Regarding this, contact your project manager.

Since version 5.5.1 ChatGPT is available as a service provider. In order to use it, the property aihub.openai.translation.workflow needs to be maintained with the value “openai_translation”.

• *The “Translation service” action can be applied to products, variants as well as items.
• Using this action does not require any further rights.

FAQ

What is the difference between “Assign item to other product” and “Assign multiple items to other product”?

With “Assign item to other product”, one or multiple items are directly ticked in the product data table and assigned to a target product. With “Assign multiple items to other product”, one or several products are ticked first, and the desired items can then be selected from their items in the dialog box for assignment to the target product.

What happens to products when the “Merge products” action is used?

The items of the source items will be assigned to the target product. The source products still exist, but they don’t have items anymore, and their name bears the prefix “Merge_”.

How can a new item be created for a product?

To do so, the desired product is called up in the “Attributes” tab of the “Product details” app, and in the action menu the option “Data” and then “Create item” is selected. The item is then configured; menus and input fields marked with an “*” are mandatory.

What does the “Attribute generation via AI” action do?

This action can be used to trigger an AI-supported attribute value generation, whereby the generated attribute value is written on selected standard attributes of the localized string type. For this purpose, standard and category attributes of the respective product are used.

In which data view can the “Assign item to other product” action be executed?

This action can only be used if the data view “Items” is selected. The “Assign multiple items to other product” action, on the other hand, can only be used if the data view “Products” is selected.

Why can’t “Create new product version” be applied to the same copy repeatedly?

This action can only be applied to the initial product. It cannot be applied to a copy of a product.

Why are category attributes sometimes not included when copying product data?

By default the property ipim.core.rest.copy.scopes is set to “ALL” which effects that only standard attributes are copied. For example, in order to copy also category attributes you need to set the property to “ALL,CATEGORY”.

Which attributes are used for text generation via AI?

The category attributes of the respective product are used for the text production. Additionally, further attributes can be specified using the property attribute.identifier.textgen. Since version 5.7.1 also attributes on the product level are used to generate texts on the variant or item level.

Why can’t every text type be selected for AI-supported text production?

In order to make a text type selectable for the AI text generation, for this text type the type property REST-API: KI-Generierter-Text needs to be set to “YES”. This setting can be done in the “Types” area of the “System setup” section of iPIM CC.

How is an attribute profile assembled for the digital product passport?

In order to assemble an attribute profile, you need to go to the attribute configuration of iPIM CC, assign the attribute property Narravero profile to the individual attributes and assign the name of the respective attribute profile to the property as its value.

What is required to use ChatGPT as a translation service?

In order to use it, the property aihub.openai.translation.workflow needs to be maintained with the value “openai_translation”.

Can the selection of available data locales for text generation via AI be restricted?

First introduced in version 5.6.1: The property ipim.web.generate-ai-text.locales.display can be used to determine which locales are available for this action. The desired locales can be assigned to the property as comma-separated values (e.g. en-GB,de-DE). By default, the property does not possess a value so that the selection of locales is not limited.

Rights

The identifier of rights are not shown correctly here as hyphens are shown as half square dashs. In order to search for a particular right in iPIM CC, copy the key to the clipboard and search for the key.