| Release | Comarch ERP Enterprise 6.3 |
| Release date | 28.04.2023 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.3.
This fix comprises the following support deliveries: RFR-016433 – RFR-016435
Information about the features of Comarch ERP Enterprise 6.3 (release news): · INF- 002654 Release-News: Betriebswirtschaftliche Lösungen · INF-002656 Release News: Business Solutions · INF- 002655 Release-News: Technische Lösungen · INF-002661 Release-News: Technical Solutions
System requirements: · INF-002659 Systemvoraussetzungen Comarch ERP Enterprise 6.3 · INF-002660 System Requirements Comarch ERP Enterprise 6.3
To install the support deliveries, please use the following documentation: · “Introduction: Software Logistics” (German language version) · „Using Tools and Troubleshooting Help” To install further languages, use INF-00200 “Sprachaktualisierungen installieren”.
The cumulative installation of support deliveries is described in INF-000228.
In case of problems during the installation, please refer to INF-000155 “Problembeschreibungen und Vorgehensweisen zur Behebung von Problemen bei der Installation von Supportauslieferungen”. |
Table of contents
1 Information about support deliveries 3
2 Installation of software updates 4
3 Information about CEE630PB-Fix06_ 4
3.1 Installing support deliveries 4
3.2 Cumulative installation of support deliveries 4
3.3 Parallel or sequential installation 5
3.4 Problems during the installation 5
4 Rework after installation_ 5
5 Contained changes and extensions 5
5.1.1.2 Contracts/RFQs/Quotations/Orders 8
5.1.1.5 Partner relationship categories 9
5.1.2.1 Calculation – General 10
5.1.5.5 Inventory value query 14
5.1.6.1 Material requirements planning 15
5.1.7.2 Resource capacities 17
5.1.9.3 Sales fast entry vouchers 20
5.1.9.4 Sales price listings 20
5.1.10 Storage Location Control 22
5.1.10.2 Inventory requisitions 22
5.1.10.3 Storage location reservations 23
5.2.4.1 Process definitions 27
5.2.4.2 Workflow templates (transport) 28
1 Information about support deliveries
The “Query support deliveries” application in the support system allows you to download directly from Comarch ERP Enterprise the support deliveries with their corresponding delivery documentation as well as further information.
The following types of support deliveries are relevant for you:
- RFR
This type of support delivery comprises a software upate or a file delivery as well as the corresponding delivery documentation.
- INF
This type of support delivery is used to provide FAQ-like information in a document.
- LNG
This type of support delivery is used to deliver language updates that can be installed in addition to German (de).
- 900
This type of support delivery comprises adaptors for the communication with third-party systems. - APP
This type of support delivery comprises installable Apps as well as the corresponding delivery documentation.
The available support deliveries are displayed in the “Query support deliveries” application according to the selected release, delivery, or delivery date. You can search for support deliveries and download their content. You can also find out whether new support deliveries are available. The application keeps a log on who has displayed which information or downloaded which software update, and when.
Note:
You need appropriate authorizations to download files. Please refer to the application documentation of “Support deliveries query”. If the relevant authorization is missing, please contact your Comarch support partner.
2 Installation of software updates
Follow the instructions given in the documentation “Introduction: Software Logistics” to install the software updates that are contained in the support deliveries. If there are deviating instructions to be followed, they are provided in chapter “Information about CEE630PB-Fix06”.
Preparing the installation
Please read the info texts accompanying the support delivery. Before installing the software updates, you must carry out a data backup of the database contents and the file system.
Make sure that all databases of the system are connected with the message server or with the ERP System Application Server (SAS) that you use for the upgrade. Shut down the SAS of the system before installing the software updates.
3 Information about CEE630PB-Fix06
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix05 will be upgraded to CEE630PB-Fix06.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CIS620PA and CIS620PB-Fix11, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE630PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”.
3.2 Cumulative installation of support deliveries
Code status CIS620PA is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.2 and Comarch ERP Enterprise 6.3 at the same time. Support deliveries for Comarch ERP Enterprise 6.3 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
3.3 Parallel or sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.4 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
No batch data updates have to be carried out.
5.1 Application development
RFR-016435 Correction
Framework: Inventory management
Application: Inventory requisitions
View: Manual inventory movement
Action: Update after two identical serial number assignments have been created for the same line item.
Category: Exception
Problem: It was possible to create two identical serial number assignments for the same line item.
Correction result: The creation of identical serial number assignments for the same line item is prevented by a check.
RFR-016435 Correction
Text corrections (German only)
RFR-016435 Extension
Framework: Base
Application: “n.a.”
View: “n.a.”
Action: “n.a.”
Report output using virtual function com.cisag.app.general.log. TextVirtualFunction
Category: Unexpected behaviour
Problem: It is possible that a virtual table or function is not initialized correctly for ODBC.
Correction result: From now CisEnvironment and CisObjectManager will be initialized correctly for ODBC.
Technical information: CisEnvironment and CisObjectManager are now created in init()-method right before usage.
RFR-016435 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: … execute planning…
Category: Unexpected behavior
Problem: An item has a versioned planning view (application Items –> Planning view). Old version has a “Planning time fence” other than current version. For example “Planning time fence” of current version is 0 days.
Material requirements planning does not regard value of “Planning time fence” of current version and uses value of old/oldest version instead.
Result: If a demand within this wrongly used planning time fence causes a planning recommendation this is set to first working day behind this planning time fence. This is too late if planning time fence of current version is lower or even is 0 days.
Correction result: “Planning time fence” of current version of Items –> Planning view is used. Planning recommendations within this planning time fence are scheduled accordingly as expected.
RFR-016435 Ergonomics
Update of the EN language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016435 Correction
Framework: Production
Application: Operations
View: Structure View
Action: Load/Refresh
Category: Unexpected Behaviour
Problem: In the structure view of the Operations-application, resources use validAt-date of the operation instead of that from the Valid on-field.
Correction result: Resources are now displayed according to date from Valid on-field.
RFR-016435 Correction
Framework: Inventory management
Application: Reservations
View: Inventory or receipts and inventory
Action: Refresh
Category: Unexpected behavior
Problem: If the button “Reserving demand origins” was pressed, then completed demand origins for stock data were also displayed.
Correction result: Completed demand origins for stock data, are no longer displayed.
RFR-016435 Correction
Framework: Production
Application: Cockpit: Production orders
View: Selection fields
Action: Load
Category: Unexpected behavior
Problem: Selection field “Level” of Cockpit: Production orders has a selection other than “All”. If cockpit is refreshed, closed afterwards and restarted, the selection value of field “Level” is not defaulted. Selection value also is not defaulted after action “Save and pin query template” has been performed and cockpit is started anew with this saved query template.
Correction result: Selection field “Level” of Cockpit: Production orders is defaulted as expected in above described contexts.
5.1.1 Base
5.1.1.1 Company calendars
RFR-016435 Extension
Framework: Base
Application: Company Calendar Types
View: n.a.
Action: n.a.
Category: New funcionality
Description: From now the import and export of a company calendar type will be fully supported.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016435 Correction
Class: com.cisag.app.general.order.hook.log. OrderReferenceRegistrationHook.OrderReferenceRegistry
Methods:
– public void registerOrderReference(short sourceOrderType, short targetOrderType)
– public void registerOrderReference(short sourceOrderType, short targetOrderType, ReorganizationRule reorganizationRule)
Problem:
OrderType registrations (source order type ==> target order type) can be done only one time. Also the inverse combination (target/source) must not exist. This was checked already but there was a gap for check of the inverse combination.
Correction result: Now the gap for the reverse combination check was closed so that the exception occurs also in this case.
RFR-016435 Correction
Class: com.cisag.app.general.order.gui.factories. DocumentTextEditorFactory.EditorImpl
Method: public void initVisualElement()
Description:
To avoid some problems with some layouts the following code line has been removed from the editor method “initVisualElement”: documentTextEditor.getEditor().setPreferredHeight(88);
Please note that with this change the “Standard” table hight is now only one row.
5.1.1.3 Fiscal years
RFR-016435 Extension
Framework: Base
Application: Fiscal year statuses
View: n.a.
Action: n.a.
Category: New funcionality
Description: From now the import and export of a fiscal year status will be fully supported.
5.1.1.4 Items
RFR-016435 Correction
The help document “Items” has been updated regarding the searches for items with a partner reference: these searches show the data of all organizations, regardless of the currently selected or currently active organization.
5.1.1.5 Partner relationship categories
RFR-016435 Documentation
Help document “Partner Relations Categories” (German language version) has been corrected regarding the description of the checkbox “Automatically generate incoming releations” and enhanced with information about a data update for initializing the descriptions of the predefined partner relation categories.
5.1.1.6 Partners
RFR-016435 Correction
Framework: Base
Application: Partner- tool phonetic encoder
View: n.a.
Action: n.a.
Category:n.a.
Problem: There is duplicate code that should be remove
Correction result: The duplicated code is already removed
5.1.2 Calculation
5.1.2.1 Calculation – General
RFR-016435 Correction
Framework: Calculation
Application: Trade cost calculations
View: Trade cost calculation sales item
Action: Calculate
Category: Exception
Problem: If an item has no proper features and you call trade cost calculation an exception occurs.
Correction result: If an item has no proper features and you call trade cost calculation there is no exception
but an error message, which indicates the missing feature.
5.1.3 Document Management
RFR-016435 Correction
Framework: Document management
Application: Document types
View: n.a.
Action: n.a.
Category: Exception, Unexpected behavior
Problem: Exception when opening document type which have assigned other field, which was deleted in the meantime.
Next sequence number is created basing on the highest displayed sequence number of other fields, so there is problem in numbering, when there are more pages and we do not open last page of other fields.
Correction result: No more exception.
There is no more problems in numbering of other fields.
5.1.4 Financials
5.1.5 Inventory management
5.1.5.1 Availability rules
RFR-016435 Extension
Framework: Inventory Management
Application: Availability rules
View: n.a.
Action: Import
Category: New action
Description: Support Import of availability rules including positions
5.1.5.2 Identifiers
RFR-016435 Correction
Framework: Inventory Managment
Application: Identifiers
View: n.a.
Using the field value assistant “Identifiers search”
Category: Unexpected behavior
Problem: If the displayed identifiers had assigned several supplier item identifiers the quantity results would be sumed as often as xxx exist.
Correction result: The result is displayed for every single supplier item identifier as expected.
RFR-016435 Correction
Framework: Inventory Management
Application: Inventory identifiers
View: n.a.
QC status change for serial number without inventory management
Category: Unexpected behavior
Problem: If the QC status of a serial number without inventory management was changed the lock and update mechanism would be used.
Correction result: If the QC status of a serial number without inventory management is changed the identifier base data are changed only as expected.
5.1.5.3 Inventory count
RFR-016435 Correction
Framework: Inventory Management
Application: Inventory count
View: n.a.
Action: Validate
Category: Exception
Problem: If an inventory count was duplicated and its type were changed to a not existing type an exception would be caused.
Correction result: The validation will be executed as expected.
RFR-016435 Correction
Class: com.cisag.app.inventory.physical.log. PhysicalInventoryCountListGenerator
Method: (abstract) com.cisag.app.inventory.physical.log. PhysicalInventoryCountListGenerator.treatZero(CisParameterList, List)
Description: A new abstract method was created to avoid unnecessary executions of the treatZero(…) methods within the implementations of the PhysicalInventoryCountListGenerator. The functionality itself was not changed.
RFR-016435 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Validate a big amount of reported loading units
Category: Exception
Problem: If there are a big amount of reported loading units (e.g. > 2000) their validation could cause an exception. Whether an exception is caused depends on the maximun number of supported result set parameters.
Correction result: Independnent of the number of reported loading units they can be validated as expected.
RFR-016435 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Action: Close inventory count lists…
Category: Unexpected behavior
Problem: If a serial number with open process data was removed the job log would contain more messages than necessary.
Correction result: The job log will only contain one message per removed serial number process data.
5.1.5.4 Inventory postings
RFR-016435 Correction
Framework: Inventory management
Application: Inventory postings
View: Inventory posting
Action: Save
Category: Exception
Problem: In the case of a transfer or revaluation postin, an exception has occurred if no company was used as the owner.
Correction result: The exception no longer occurs in the described case.
RFR-016435 Correction
Framework: Inventory management
Application: Inventory postings
View: Posting error log
Action: Post an error log from transport order with the inventory order category “Relocation for withdrawal”.
Category: Unexpected behavior
Problem: An unnecessary attempt was made to remove dependent storage location reservations, which resulted that the inventory transaction could not be posted.
Correction result: The unnecessary removal of storage location reservations has been eliminated.
5.1.5.5 Inventory value query
RFR-016435 Correction
Framework: Inventory Management
Application: Inventory value query
View: Item values periodic
Action: Refresh
Category: Exception
Problem: If the customizing setting “Optional valuation method” (section “Valuation”) is empty (nothing selected) the application “Inventory value query” throws an exception for the “Refresh” action of the view “Item values periodic” if the valuation method has the value “Any”.
Correction result: Now the exception does not occur any more in this case.
5.1.5.6 Picking orders
RFR-016435 Correction
Framework: Inventory
Application: Delivery orders, Picking Orders
View: n.a.
Action: Update
Category: Invalid data / Unexpected behavior
Problem: Reporting quantities in a picking order for a detail line with item identifier type “Serial number without inventory management” lost fixed reservation.
Correction result: From now reporting quantities in a picking order for a detail line with item identifier type “Serial number without inventory management” will work as expected.
5.1.5.7 Reservations
RFR-016435 Correction
Framework: Inventory Management
Application: Inventory orders
View: n.a.
Outgoing report for a loading unit with different serial numbers
Category: Exception
Problem: If fixed reservations were supported and the loading unit was not prescribed by the inventory request an exception would be caused at its reporting.
Correction result: Serial number mixed loading units can be reported as expected.
RFR-016435 Correction
Framework: Inventory Management
Application: Cleanup of reservation data (Data correction application)
View: n.a.
Action: Start data correction
Category: Exception
Problem: If item reservation data should be rebuild that had different units and the first item unit was not the main warehouse unit the correction application would be aborted with an exception. The data were not rebuild completely.
Correction result: Independent of the item units the correction application can be execute as expected. If the execution was aborted this application can be used to rebuild the data.
Please note: If any data correction application is aborted the data to be corrected must be checked before it is allowed to use them.
5.1.6 Planning
5.1.6.1 Material requirements planning
RFR-016435 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: … execute planning
Category: Unexpected behavior
Problem: In some specific contexts conflict “early order” is not properly assigned to receipts
A. Receipts in pre period do not get conflict “early order” in relation to first demand within planning horizon. Depending on context a receipt in pre period may get wrongly conflict unnecessary order.
B. If multiple receipts due date lie in the same period as actual demand none of this receipts gets a conflict “Early order” (as every receipt is related to this demand).
Correction result: A. Receipts in pre period get conflict “early order” if context requires this.
B.
More than one receipt in a certain period (P1) coincide with a demand in this period. This receipts now may get a conflict „Early order“ with respect to later demands compared to P1.
No conflicts are addressed as long as receipt quantities summed up are not covering demand. First receipt for which demand is covered completely also does not get a conflict.
Later receipts (LR) of P1 do get conflicts if further demands follow with a later demand date than P1.
Later receipts get the conflict with respect to next following demand as long as one of the LR covers demand of that period.
Addressing conflict „Early order“ continues as long as there are further LRs in period P1 and still later demands in the same way as described.
RFR-016435 Correction
Framework: Planning
Application: Material Requirements planning
View: n.a.
Action: Update planning data and execute planning
Category: Unexpected behavior
Problem: Status STORE_ITEM_PLANNING_RESULT is displayed as “com.cisag.app.production.ui. APSController:STORE_ITEM_PLANNING_RESULT”.
Correction result: Status STORE_ITEM_PLANNING_RESULT is displayed as text: “Das Planungsergebnis der Artikel wird gespeichert”
5.1.7 Production
RFR-016435 Correction
Framework: Production
Application: Operations
View: n.a.
Action: duplicate external operation
Category: Unexpected behavior
Problem: It is not possible to duplicate an external operation that contains a supplier to which a warning is assigned. The confirmation of the warning does not work.
Correction result: The confirmation of the warning works and the external operation can be duplicated.
5.1.7.1 Production orders
RFR-016435 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: dispatch with multiple level
Category: Exception
Problem: after changing current begin of an operation and saving production order an exception occurs, if the order contains subordinate orders
Correction result: after changing current begin of an operation and saving production order no exception occurs, if the order contains subordinate orders
5.1.7.2 Resource capacities
RFR-016435 Correction
Framework: Production
Application: Resource capacities
View: n.a.
Action: refresh
Category: Exception
Problem: NullPointerException after entering an unsuitable date
Correction result: No nullPointerException after entering an unsuitable date
5.1.8 Purchasing
5.1.8.1 Supplier invoices
RFR-016435 Correction
The documentation “Eingangsrechnungen importieren” has been updated according new data structure of BO “Eingangsrechnung” in release 6.2.
RFR-016435 Correction
Framework: Purchasing
Application: Data import
Action: Import supplier invoices
Category: Unexpected behavior / Ergonomics
Problem:
1.) For the order assignments of supplier invoice line items the associations “SalesOrder” and “SalesOrderDetail” are not supported by the import.
2.) If a correction invoice was created by the import an exception occurs within the save step.
Correction result:
1.) Now both associations have been removed from the import filter definition (main line items and sub line items) but are still present (as before) within the export filter definition.
2.) As in the user interface, manual creation of correction invoices is now no longer possible during import. When attempting to create such an invoice, an error message appears in the same way as in the user interface.
RFR-016435 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Cancel additional cost invoice
Category: Invalid data / Unexpected behavior
Problem: If an additional cost invoice references a receipt of goods line item and such an invoice is canceled the attributes “supplierInvoiceQuantity[0..3]” of the business objects “com.cisag.app. purchasing.obj.ReceiptOfGoodsOrderInfo” and “com.cisag.app.purchasing.obj.ReceiptInvoiceOrderAssignment” are changed up from the release 6.2 although in this case the quantity is not used. As result such a receipt of goods line item can not be used any more to a normal supplier invoice.
Correction result: Now the “Cancel additional cost invoice” action does not change the “supplierInvoiceQuantity[0.. 3]” attributes of the two business objects.
RFR-016435 Correction
The help document “Beschaffungsaufträge” has been updated regarding Accout origin.
RFR-016435 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Create
Category: Invalid data / Unexpected behavior
Problem: If a supplier invoice was loaded that supports “Delivery slip numbers” (types “Supplier invoice” or “Correction supplier invoice”) and has for the relevant field any not empty value and an invoice with a type is created that does not support “Delivery slip numbers” (e.g. “Supplementary cost invoice”) some error messages occur that the “Delivery slip numbers” need to be unique (“PUR-08711”). The problem is here that the value of the relevant field will not be cleared by the “data to ui” step in this case and will be added internally (not visible) multiple times by every “data from ui” step.
Correction result: Now the error does not occur any more.
5.1.9 Sales
5.1.9.1 Customer invoices
RFR-016435 Correction
Frameworks: Financials, Sales
Applications: Debtor credits, Customer invoices
Action: Create invoice
Category: Unexpected behavior
Problem: In some cases it can occur that debtor credits are used by a customer invoice but the assigned values do not match to the “Invoice amount due” so that the “Remaining amount” is not zero. This happens especially for the “Country-specifics” with the value “Switzerland” and activated “Apply rounding to nearest 5 Rappen” functionality.
Correction result: If some debtor credit reservations are found and assigned there are two cases:
1.) This would result in a negative “Remaining amount”. Then the reservation assignments (several, if necessary) are reduced again, resulting in a “Remaining amount” of 0.
2.) For some amount, a value has changed due to the final value handling (e.g. “Apply rounding to nearest 5 Rappen”) and the “Remaining amount” is positive. Then the used reservations are looked at again and it is seen whether there is still an “Open reserved credit”. This is then used – so the assigned amount is increased (if necessary also several here), so that also here the “Remaining amount” is reduced to a maximum of 0.
RFR-016435 Correction
Framework: Sales
Application: com.cisag.app.sales. invoice.log.Invoicing
Action: Default
Category: Unexpected behavior
Problem: In contrast to other similar applications the application “com.cisag.app.sales.invoice.log.Invoicing” does not declare the supported parameter “Date”.
Correction result: Now the parameter “Date” is declared as expected.
5.1.9.2 Customer returns
RFR-016435 Correction
Framework: Inventory
Application: Delivery orders
View: n.a.
Action: Cancel external delivery order
Category: Exception
Problem: An exception occurred cancelling an external delivery order that contained a set item with components.
Correction result: From now cancelling an external delivery order that contains a set item with components will work as expected.
5.1.9.3 Sales fast entry vouchers
RFR-016435 Correction
Framework: Sales
Application: Sales fast entry vouchers
Actions: “Release for automatic transfer” and “Transfer manually”
Category: Unexpected behavior / Ergonomics
Problem: If a sales rapid document is configured so that prices are determined by delay a price listing was mandatory before this change even if the header and all line items are using only manuell discounts and prices.
Correction result: Now the price listing is mandatory only if the discount/price origin is “Price list” or “Price list, manual” for the header or at least one line item.
5.1.9.4 Sales price listings
RFR-016435 Correction
Framework: Sales
Application: Sales price listings
View: n.a.
Action: Validation
Category: Unexpected behavior
Problem: The error checking for the field “currency” takes place only if there are persistent rows in the table.
Correction result: There is an error message if the field “currency” is not inputted even if there are no persistent rows in the table.
5.1.9.5 Sales prices
RFR-016435 Correction
Class: com.cisag.app.costing.log. SalesPriceListUpdate
Description:
The deprecated usage of the method “com.cisag.app.costing.sales. log.SalesCalculationUtility.isSalesOrganization(byte[])” has been replaced by some own coding. This was necessary because the method was deleted by another development order.
RFR-016435 Correction
Framework: Sales
Action: Pricing inquiry
Category: Invalid data / Unexpected behavior
Problem: By mistake up from the fix “CIS600PB-Fix03 KW41/2017” (new flags “Do not apply any order value discounts” and “Do not apply multi-item discounts” within the “Sales price component types”) the sales inquiry sets the attributes “No order value discounts” and “No multi-item discounts” to true for the case that the sales item attribute “Apply no line item discounts or base discounts” (from customer item, from customer classification item or from sales item) is true.
Within proposals/orders with the price origin type “Manual” the behaviour is already as expected and also for the purchasing inquiry.
Correction result: Now the flags “No order value discounts” and “No multi-item discounts” will not be changed if the item attribute “Apply no line item discounts or base discounts” has the value true.
5.1.10 Storage Location Control
5.1.10.1 Inventory orders
RFR-016435 Extension
The following help documents have been updated regarding new action “Lageranforderung für den Rücktransport erzeugen”: * Cockpit: Lageraufträge
* Cockpit: Lageraufträge/Positionen
* Lageraufträge
* Vorgehensweisen: Lageraufträge
RFR-016435 Correction
Framework: Storage Location Control
Application: Storage locations
View: n.a.
Fill up of locations of the kind “Fixed location without storage unit”
Category: Unexpected behavior
Problem: If there is an open process with an incoming quantity for a fixed location the fixed location could not be filled up by another process although it has enough capacity.
Correction result: If a fixed location is allowed to be filled up it will be filled up as expected. Incoming quantities will be considered together with the current stock.
5.1.10.2 Inventory requisitions
RFR-016435 Correction
Framework: Storage Location Control
Application: Inventory requisitions
View: Manual Stock Movements
Incoming with prescribed storage unit
Category: Unexpected behavior
Problem: In some constellations the specified storage unit and the storage unit of the open process data could differ.
Correction result: The specified storage unit is always used to create the open process data as expected.
5.1.10.3 Storage location reservations
RFR-016435 Correction
Framework: Inventory management
Application: Correct voucher data and reservations
View: n.a.
Action: Output test results or correct incorrect data for posting error logs
Category: Unexpected behavior
Problem: The correction of posting error logs from transport order with the inventory order category “Relocation for withdrawal” was incorrect.
Correction result: Data for posting error logs are now correctly created.
5.2 System development
RFR-016433 Correction
Framework: Software development
Application: Job maintenance
View: n.a.
Action: checkin
Category: Unexpected behavior
Problem: During checkin the referenced java classes are checked. If a java class must not be referenced an error message is send.
Checkin itself worked correctly, it just can happen that the context, i.e. the java class causing the problem, is incorrectly set..
Correction result: If such an error occurs, then the correct java class is refered to.
RFR-016433 Correction
Framework: Software development
Application: Repository maintenance
View: Icon
Action: update
Category: Ergonomics
Problem: for all icons a file is put into the file system. For icons of format “font” or format”composite” this is not necessary.
Correction result: No file is put in the file system for icons of format “font” or format “composite”
RFR-016433 Correction
Framework: System management
Application: All
View: n.a.
Action: n.a.
Code which needs a connection from connectionpool.
Category: Unexpected behavior
Problem: The performance for getting a connection from connectionpool was not optimal.
Correction result: Unnecessary syncronization was removed.
RFR-016434 Correction
Message text WFL-00526 has been improved.
5.2.1 Application server
5.2.1.1 MessageDispatcher
RFR-016433 Correction
Process: Messaging
Category: Unexpected behavior
Problem: If the message server sends 2 messages to the same target system shortly in succession, the second might yield the error “Disconnect message received created connection to system [XXX]: already connected” on the target system. The second message isn’t send (and therefore not answered, resulting in appropriate errors on the sending system). The message server tries repeatedly to send the message, each time repeating the error messages, until either one of the message servers is restarted.
Correction result: Second message is sent.
RFR-016433 Correction
Package: Messaging
Category: Ergonomics
Problem: Logging of a ping shows wrong system name in client info.
Correction result: Correct server name is logged. Clean-up of various debug messages.
RFR-016433 Correction
Process: Messaging
Category: Ergonomics
Problem: Several logfile entries for the messaging are misleading: if the connection is a connection from a client server to the system’s messageserver, the client’s log displays the connection info “connection to master [xxx]”, but with the name of the client server. The server’s log displays the correct name.
Correction result: The client’s log display the name of the master server. Several other log messages are enhanced.
5.2.2 System – General
RFR-016433 Correction
Framework: System Management
Application: Synchronize with LDAP
View: n.a.
Action: Execute
Category: Unexpected behaviour
Problem: If the LDAP server is unavailable while executing “Synchronize with LDAP”, a NullPointerException message appears in the log additionally to an error message. If the application is executed as series, the series is aborted.
Correction result: The exception message does not apper. A batch series is executed again after the LDAP server was unavailabla.
5.2.3 Web server
RFR-016433 Correction
Framework: System management
Application: Web server
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The integrated web server of CEE is using “HTTP Strict-Transport-Security” (HSTS) to improve security. In brief, this feature forces the browser to strictly use HTTPS in order to prevent downgrade attacks to HTTP. But this feature is not compatible with configurations, where HTTP and HTTPS is used for different ports on the same host (or hosts within subdomains). An example of such scenario is the usage CEE’s loadbalancer (which is using HTTP).
Correction result: Two new properties have been introduced: com.cisag.sys. kernel.webserver.https.stsMaxAge= (Default: 2000)
com.cisag. sys.kernel.webserver.https.stsIncludeSubDomains= (Default: true)
Using a negative value for stsMaxAge (e.g. “com.cisag.sys.kernel.webserver.https.stsMaxAge=-1”) will disable the HSTS feature.
Note: Browsers may have cached the old setting. Usually this can be deleted using some “expert” pages of the browser (e.g. “chrome://net-internals/#hsts”). Or may be invalided automatically after 2000 seconds (the default for stsMaxAge).
5.2.4 Workflow
RFR-016433 Extension
Framework: Workflow Management
Application: Process definition
View: n.a.
Action: n.a.
Category: Extension
Description: A new tab ‘Start application’ in application Process Definition.
Technical information: This tab will present data about the start application related to the process definition template.
RFR-016433 Extension
Framework: Workflow
Application: Activity Definition,
View: n.a.
Action: n.a.
Category: Extension
Description: New validations added to various workflow-related entities. New validation on starting application of subtype process definition.
RFR-016433 Correction
Framework: Workflowm Management
Application: Activities
View: n.a.
Action: load
Category: Exception
Problem: When open activity with reposytory database type – exception.
Correction result: Activity with reposytory database type is open normal.
RFR-016433 Correction
Framework: Workflow Management
Application: search for tasks
View: n.a
Action: Open
Category: Exception
Problem: When open activity created on repository database, throw exception.
Correction result: Repository database task is opening correctly.
RFR-016434 Extension
Framework: Workflow Management
Application: Process definition
View: n.a.
Action: n.a.
Category: Extension
Description: A new tab ‘Start application’ in application Process Definition.
Technical information: This tab will present data about the start application related to the process definition template.
RFR-016434 Extension
Framework: Workflow
Application: Activity Definition,
View: n.a.
Action: n.a.
Category: Extension
Description: New validations added to various workflow-related entities. New validation on starting application of subtype process definition.
5.2.4.1 Process definitions
RFR-016433 Correction
Framework: Workflow Management
Tool: dltwflprc
Action: -code: < number of process >
Category: Unexpected behavior
Problem: Can not delete a process when has a deserialization exception.
Correction result: Can delete a process when has a deserialization exception by option -code: < number of process >.
5.2.4.2 Workflow templates (transport)
RFR-016433 Correction
Framework: Workflow management
Application: n.a.
View: n.a.
Action: n.a.
Category: Unexpected behavior / Ergonomics
Problem: Wrong error message when saving a workflow definition as a template
Correction result: Message WFL-00555 is removed, but REP-00027 is still presented, it is standard logic for all repository object – first check for the same name, second check for the same name in uppercase
RFR-016434 Correction
Framework: Workflow management
Application: n.a.
View: n.a.
Action: n.a.
Category: Unexpected behavior / Ergonomics
Problem: The actions “Save as template” and “Generate from template” are sometimes available even though the actions are not permitted for the workflow definition or workflow template.
Correction result: Updated the availability of actions “Save as template” and “Generate from template” in applications AD, PD, WR.
Added a check blocking the Duplicate action in the Develeopment objects application
RFR-016434 Correction
nothing changes