Single Items view
There’s only a single flexible view in the Items tab. The default view looks similar to Tree View. To achieve the Table View like layout, consider using hideSiderPanel or defaultPlacement parameters of the Items tab. More in https://pricefx.atlassian.net/wiki/spaces/KB/pages/3980492805/Detail+Page+Layout+and+Dynamic+Tabs#Widget-Parameters.
You need to manually set up the preferences for the Items table. Ember preferences are not used in React for Items table. In React QuoteEditor_TableTreeView and similarly named preferences are used, in Ember it’s either QuoteEditor_Overview or QuoteEditor_TableView.
Data and new endpoints
There’s a new set of endpoints that are used in React: /clicmanager.*. The main difference is that header and line items data are never sent together. We needed this to make it possible to support thousands of line items. So, for example. /clicmanager.fetchheader and /quotemanager.fetch return similar responses, but the new one has no line items and contains ioMeta to know which inputs and outputs are used by the line items. You can retrieve line items by /clicmanager.fetch.
New endpoints are described in the API documentation:https://api.pricefx.com/openapi/reference/pricefx/tag/Clicmanager/
Loops and inline configurators
With autosave on, it’s possible the inline configurators will get to the loop state. There could be more reasons, but it’s usually solvable by adding HIDDEN inputs for attributes that do not represent an input editable by the user. The list of such inputs is displayed in the developer console:
def hiddenInputs = [ "office", "customer", "distributionChannel", "sku", "targetDateLineItem" ]
def ce = api.createConfiguratorEntry()
for (name in hiddenInputs) {
api.inputBuilderFactory()
.createHiddenEntry(name)
.addToConfiguratorEntry(ce)
}
return ce
The next possible reasons for such loops is the input value that is changing every time when the configurator logic is executed, like showing a current timestamp. You either need to make it HIDDEN or remove it.