In this section you can define templates on which Quote mass update jobs will be based.

Templates

Here you can manage mass update templates. Create a new template or select an existing one to edit its properties.

The template marked as Default will be used when a new mass update job is created by the user.

Header/Item Inputs

In these tables, add the fields that you want users to manually modify when they run a mass update job. Only add fields that are defined as user inputs in the Quote header logic or the default pricing logic.

• Field – The Element Name of the user input element in the logic.

• Label – The text that will be displayed next to the user input field in the mass update dialog.

• Input Type – Select the actual input type as it is defined in the logic element.

• Description – A hint for the end user.

Item Mass Update Logic

A header or item mass update logic can:

• Modify the Quote inputs automatically. You can use this type of logic if you want to, for example, modify the payment terms (a Quote header input).

• Define additional parameters that the user will be able to set in the mass update dialog.

The logic must contain elements, defining inputs, which match the inputs in the Quote calculation logic (they must have the same Element Name).

Example

Item Override Logic

The purpose of this logic is to allow overridable outputs to be processed by a logic in order to keep or further change the output value.

Example

Modified Inputs

Defines which input elements from the pricing calculation logic will be displayed in the summary table on the Quote Mass Update tab.

Outputs of Modified Inputs

Defines which resulting elements from the pricing calculation logic will be displayed in the summary table on the Quote Mass Update tab. Typically, you will list here the elements from the logic that you are updating so that you can see how the values have changed.

Limitations

• You can pass values between individual line item runs by storing them in the cache. Set api.global with retainGlobal = true and create a header logic (even an empty one) to be able to pass values via the header. Without the header logic, api.global will not persist.

• Summary View displays only inputs which are in the header or line item logic. It does not support displaying fields from the Quote Header Info – except for Description (shown as Label in the table) and Name (shown as Source for the original Quote and Target for the target Quote).