Pricing Part Rule Maintenance was newly introduced into this release. Using Pricing Part Rule Maintenance, you can define how QAD Configurator assigns pricing parts. After the pricing part rule is set up, you can associate the pricing part rule with the feature options. A new field Rule has been added to variable and feature maintenance screens.

You can now export general rule tables and item-specific rule tables for updates and then import those updated rule tables into QAD Configurator. This functionality provides great convenience and efficiency in rule table management.

Translation Manager was newly introduced into this release. Compared to using the String Translation button, Translation Manager does not require access to Configuration models. Since translation tasks are typically not the responsibilities of modelers, Translation Manager enables independent translations by professional translators. It provides great flexibility in translation management and greatly increases translation efficiency and professionalism.

Using Translation Manager, you can export either all the strings or only the untranslated strings to an Excel file. Then the translators can maintain the translation texts in the Excel file. After they finish the translation, you then use Translation Manager to import the Excel file for questionnaire display.

Configurator Standard Messages was newly introduced into this release. This function is similar to Message Maintenance in QAD Enterprise Applications. Using Configurator Message Maintenance, you can maintain standard Configurator messages independently. The message strings that are entered in this function can be identified and exported for translation. Compared to defining messages in configuration rules, Configurator Message Maintenance provides more flexibility and efficiency in multiple-language support.

Previously, you could use the showMessageBox function in sales configuration rules to define warning messages. But the messages for display were hardcoded. To better facilitate multi-language support in messages, a new function showMessageBoxWithTrans was provided. This function enables the display of messages based on the title code, message code, and language.

When generating a secondary SO, the SBU (bottom level) now creates a PO change acknowledgment of the cost change type. When the MBU (a middle level) imports the PO change acknowledgment, the MBU reprices the corresponding SO line and then sends a PO change acknowledgment. So when the PBU (top level) imports the PO change acknowledgment of the cost change type, the system refreshes the item cost in the PBU.

In this way, if the MBU has a markup defined in the price list, after repricing, the price in the MBU is updated based on the item cost defined in the SBU. So the PBU can adjust the item cost with the updated price in the MBU.

Two new fields, Print Sequence and Print on Customer Documents, were added to the Variable Details, Variable Option Maintenance, Feature Details, Feature Option Maintenance screens. Values of these fields are saved in configurations for printing use.

Previously in Model Publish, external entity rules were included in product configurations. However, the external entity rules are sometimes useful to the sales department. To meet this requirement, a new column was added to allow you to separately publish external entity rules with sales configurations.

Three new system variables were added. You can use these system variables in item rules to control when to trigger the rules, whether on reloading, saving, or creating the configuration.

A new option, Always Refresh Element Variables, was added to Configurable Item Maintenance. You can use this option to define whether to refresh element-type features that are associated with a configurable item on reloading.