Configuratorware Transmitter

We provide a full configured station template with the necessary datamap and jobs for theDynamic JSON Transmitter!

Setup the transmitter

In the transmitter settings you need to configure the following fields:

• The API Url to your configuratorware system
• The API Token (selectable from contentserv passwords)

Configuring the datamap

The datamap is split into two nodemaps which will be explained in detail. It is important for translation that only language keys are used that are maintained in configuratorware. Ensure that the right key is selected in the language settings.

product-Nodemap

The product nodemap represents the whole configuration item. The important row for identifying the configuration in Configuratorware is “itemIdentifier” which is required in the export.

Additionally you can maintain texts or custom attributes on the product with the row “texts|” and “attributes|”. All of these rows are part of the template.

The export of components for the configuration is configured with the row “components”. The tempalte provides a configuration to send entries of a value list as components

 
The related options for the product are loaded via the row “options” and will then be processed in the options-Nodemap. Feel free to adjust the nodemap-settings so each PIM object will get processed through the right nodemap.
 

options-Nodemap

The loaded options will get processed through the options-Nodemap. The important rows for correctly appending the options to their parent component is the row “parentComponent”. This row ensures that the option is added to the right component. (E.g. if the component identifier in the product nodemap is the external key of your value list value, the the same external key must be set in this row)
The option itself will be identified with the “optionIdentifier”.

The other rows e.g. “texts” work the same way as in the product-nodemap