Product & Customer Groups

Owned by Johannes Lindgren (Deactivated)
Last updated: Sept 16, 2024 by Ioana Kocurova
3 min read

The product and customer inputs let the user pick a set of existing products and customers from the master data. The two inputs work in the same way, just use different tables for data selection.

The value of this input is CustomerGroup or ProductGroup object. It is often transported as a Map when value is passed between logics over HTTP, so you may need to convert the input map to the object first.

Product

The product filter allows the user to provide a set of products as an input. The end user can either select products from a list, or provide a filter that will be used to query the product master table.

product fixed
Figure 1. A product filter rendered in the web browser. The user selected a fixed set of products from a list.
product dynamic
Figure 2. A product filter rendered in the web browser, after the end user clicked the search icon. The end user specified a filter in two different ways: by clicking one of the "Growth" cells, and by typing "Beef" in the header.
def formFieldSet = api.createConfiguratorEntry() formFieldSet.inputs = [ api.inputBuilderFactory() .createProductGroupEntry('productGroup') .buildContextParameter() ] return formFieldSet
api.inputBuilderFactory() .createProductGroupEntry('productGroup') .getInput()
processor.addOrUpdateInput( //❶ 'ROOT', api.inputBuilderFactory() .createProductGroupEntry('productGroup') .buildMap() )

❶ the processor can be one of the quoteProcessor, cProcessor, etc., which references subclasses of the CalculableLineItemCollectionBuilder

Reading input value in a line-item logic

Creating a filter out of the ProductGroup object to be used in Price Analyzer. It performs the attribute to datasource field name conversion

Creating a filter out of the ProductGroup object to be used in other modules except Price Analyzer

See also Product Picker Filter Logic

Customer

The customer filter allows the user to provide a set of customers as an input. The end user can either select customers from a list, or provide a filter that will be used to query the customer master table.

See also Customer Picker Filter Logic

Found an issue in documentation? Write to us.