|
Issue Number
|
Fixes
|
|
CFGS-195
|
An error that Model Publish issued in the AppServer log has been fixed.
|
|
CFGS-196
|
A Progress error that Configuration Questionnaire issued in the AppServer log in the debug mode has been fixed.
|
|
CFGS-213
|
Previously, if you ran Product Structure Cost Roll Up for a configurable item, the lower cost of the previously created variant item were not updated in item master record. This issue has now been fixed.
|
|
CFGS-219
|
Previously, the system incorrectly used the default value that a rule assigned to the feature as the actual value. This issue has now been fixed.
|
|
CFGS-223
|
A startup issue with Configurator Questionnaire has been fixed.
|
|
CFGS-225, CFGS-251, and CFGS-256
|
Previously, when the SO type of a configurable item was Phantom, Configuration Questionnaire that was started from an SO/SQ line did not populate all fields of the order lines. The unpopulated fields included perform date, tax usage, sales sub-account, discount sub-account, and the standard cost. This issue has now been fixed.
|
|
CFGS-226
|
Previously, when you ran Configuration Questionnaire for a phantom with a BOM-type configurable item at the second level, lower-level costs were not rolled up for the created variant item. This issue has now been fixed.
|
|
CFGS-227 and CFGS-259
|
The performance of rule maintenance functions, Configuration Analyzer, and Configuration Questionnaire has been improved.
|
|
CFGS-228 and CFG-271
|
Previously, when a feature was defined for a second-level item only and at the same time part of the top-level item rules, its price was not displayed in Configuration Questionnaire. This issue has now been fixed.
|
|
CFGS-232
|
Previously, when the numeric format was European and you created a variant item from an SO line, the list price and the net price of the child items were not correctly calculated. This issue has now been fixed.
|
|
CFGS-234
|
Previously, after you created a variant item from SQ line, the Comments field value in Line Details did not match the setting in Sales Quote Control. And the Pricing Date field value became blank. Now these issues have been fixed.
|
|
CFGS-239
|
Previously, after a questionnaire respondent chose Create Date and selected a date on the Existing Configuration tab, reselecting the search criteria was not allowed by using the Clear button. This issue has now been fixed.
|
|
CFGS-240
|
Previously, when you created variant items using first Configuration Questionnaire and then Sales Order Maintenance for a phantom having a BOM component, the system created incorrect SO lines. This issue has now been fixed.
|
|
CFGS-243
|
When you run Batch Compiler, you no longer see any messages for the background process.
|
|
CFGS-254 and CFGS-257
|
Previously, if either Global Alphabetic Sequence or Global Numeric Sequence was defined for a configurable item as the variant item number rule, Configuration Questionnaire did not generate the correct sequence. This issue has now been fixed.
|
|
CFGS-261 and CFGS-263
|
Previously, Model Import/Export did not export item-site planning data of lower-level components. This issue has now been fixed.
|
|
CFGS-262
|
Previously, if you used Manual Configuration Maintenance to create a variant item, the system did not create a price list record for this variant item. This issue has now been fixed.
|
|
CFGS-266
|
Previously, when Standard Options was set to Yes in Feature Maintenance, modifications in Variable Maintenance did not trigger a prompt for reanalyzing the item in Configuration Questionnaire. This issue has now been fixed.
|
|
CFGS-267
|
Previously, if you added a feature and also a rule for this feature and then you reloaded a configuration, the Answer All button did not answer the new feature question. This issue has now been fixed.
|
|
CFGS-269
|
Previously, if the Configuration Questionnaire was started from an SO/SQ line, the validation for starting the questionnaire was less stringent than when started from the Configuration Questionnaire menu. This issue has now been fixed.
|
|
CFGS-274
|
Previously, when the pccop.i file included system variables and you ran Cross Validation Analyzer, the system incorrectly displayed a warning message and flagged the rule as NOT OK. This issue has now been fixed.
|
|
CFGS-275
|
When you run Configuration Analyzer, you no longer see the generated files with the extensions: .i, .p, and .xref.xml in the Appserver questionnaire directory.
|
|
CFGS-276
|
Previously, when a variable or feature was deleted, the system did not delete its string translation records. This issue has now been fixed.
|
|
CFGS-280
|
Previously, if the questionnaire respondent clicked Saved Configuration before answering all the questions and then canceled saving, clicking Answer All did not answer the unanswered questions. This issue has now been fixed.
|
|
CFGS-283
|
Previously, in Configuration Questionnaire, when the questionnaire respondent hovered over a question mark, the text of the rule information was garbled. This issue has now been fixed.
|
|
CFGS-284
|
Previously, Configuration Questionnaire did not show question marks for short questions with general rules. This issue has now been fixed.
|
|
CFGS-285
|
Previously, when you reordered a variant item within a phantom kit for a different customer, the system did not create the customer-specific price list. This issue has now been fixed.
|
|
CFGS-287
|
Previously, if the questionnaire respondent pressed the Tab key before the prior response returned, the Questionnaire hung. This issue has now been fixed.
|
|
CFGS-289
|
Previously, the ATP Enforcement value and the Family ATP value of the created variant item did not follow the rules that were defined in Variant Item Data Rule Maintenance. This issue has now been fixed.
|
|
CFGS-292
|
Previously, in Configuration Questionnaire, when the net price value was more than five digits, it did not show on the Summary Panel. Now the Summary Panel is automatically resized.
|
|
CFGS-293
|
Previously, when creating a variant item for a configurable item with Variant Item-Site Record set to Current site only or All sites, the system displayed an error in the AppServer log. This issue has now been fixed.
|
|
CFGS-296
|
Previously, when creating a variant item for a phantom item with a configuration similar to an existing configuration, the system recorded a Progress error in the AppServer log. This issue has now been fixed.
|
|
CFGS-297
|
Previously, if a feature of a configurable item was deleted and you ran Configurator Rebuild for that item, a Progress error was displayed. This issue has now been fixed.
|
|
CFGS-303
|
Previously, when creating price lists, Configurator used the date of today as the start date, instead of using the sales quote pricing date. This error has been fixed now.
|