| Release | Comarch ERP Enterprise 6.3 |
| Release date | 03.02.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-016421– RFR-016423
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”. |
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-Fix04”.
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-Fix04
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix03 will be upgraded to CEE630PB-Fix04.
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
With the “Query data updates” application, you must schedule the following data updates, for any point in time.
UPDADV108282
5.1 Application development
RFR-016423 Documentation
The help document “Actions: Reschedule Reminder Date, Shipping Date, Delivery Date, Preferred Date” (German language version) has been updated regarding the actions for rescheduling the reminder date and the shipping date.
RFR-016423 Ergonomics
Update of the Polish user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016423 Documentation
The English help document “Export and Import Interfaces” has been updated.
RFR-016423 Correction
Framework: Production
Application: Resource utilization, Calculate resource utilization, Resource allocation, resource capacities
View: n.a.
Action: New
Category: Unexpected behavior
Problem: The “duplicate” button in the pull-down menu of the “new” button has no function.
Correction result: use the “new” button without pull-down menu.
RFR-016423 Extension
Class: com.cisag.app.general.log. QuantityConverterVirtualFunction
Method: “n.a.”
Description: New virtual function “Quantity converter” which can be used to convert item quantities as needed.
Class: com. cisag.app.general.log.TextVirtualFunction
Method: “n.a.”
Description: New virtual function “Text” which can be used to find Text and ContentType by code or guid (and language) on demand.
RFR-016423 Documentation
The following English help documents have been provided: “Distribution Recommendations”,
“Conditions, Formulas, Substitute Functions”,
“Dispatching”,
“Operations”,
“Production Issues”,
“Cockpit: Production Orders”,
“Bills of Resources”,
“Structure View”,
“Resources”,
“Routings”.
RFR-016423 Correction
Framework: Base (and others)
Application: Applications based on com.cisag.app.general.ui.SingleObjectTableMaintenance
View: n.a.
Action: Delete, Mark for deletion, Unmark for deletion
Category: Exception
Problem: If a newly created, but not saved instance is deleted (or marked/unmarked for deletion), an “IndexOutOfBoundsException” may occur at the next action.
Correction result: Fixed.
5.1.1 Base
5.1.1.1 Contracts/RFQs/Quotations/Orders
RFR-016423 Correction
New entries in com.cisag.app.general.OrderType:
1.
Name of entry: CKAPP_COMPL_CUSTOMER_COMPLAINT
ID: 2034
Description (de): Kunden-Reklamation
Description (en): Customer complaint
2.
Name of entry: CKAPP_COMPL_SUPPLIER_COMPLAINT
ID: 2035
Description (de): Lieferanten-Reklamation
Description (en): Supplier complaint
RFR-016423 Extension
1.
Framework: Purchasing
Application: “Cockpit: Purchase orders/line items”
Category: New actions
Description: The following new actions have been added: – Reschedule delivery date
– Move preferred date
2.
Framework: Purchasing, Sales
Applications: “Cockpit: Sales orders/line items” (sales) and “Cockpit: Distribution orders/line items” (sales and purchasing)
Category: New actions
Description: The following new actions have been added: – Reschedule reminder date
– Reschedule shipping date
– Reschedule delivery date
– Move preferred date
RFR-016423 Correction
1.
Frameworks: Purchasing, Sales
Applications: “Supplier quotations”, “Cockpit: Supplier quotations/line items”, “Sales quotations” and “Cockpit: Sales quotations/line items”
Category: New actions
Description: The following new actions have been added:
– Reschedule delivery date
– Move preferred date
2.
Framework: Purchasing, Sales
Applications: “Purchasing RFQs”, “Cockpit: Purchasing RFQs/line items”, “Supplier quotations” and “Cockpit: Supplier quotations/line items”
Category: New action
Description: The following new action has been added: Move preferred date.
5.1.1.2 Items
RFR-016423 Correction
Classes: com.cisag.app.general.item.log. ItemAccountingEntity,
com.cisag.app.general.item.log.CustomerPlanningEntity,
com.cisag.app. general.item.log.ItemPlanningEntity
Method: update()
Description: A duplicate call of CisObjectManager.putObject(…) for updating the entities object is removed from the method’s code. It was redundant and furthermore not correct without reading the putted data again before putting it.
5.1.2 Calculation
RFR-016423 Correction
Framework: Calculation
Application: Trade cost calculations
View: n.a.
Action: Calculate…
Category: Unexpected behavior
Problem: Quantity unit of measure (uom) of a trade cost calculation is one of defined sales units. On calculation no conversion of valuation price per this uom takes place if valuation price is one of
1. valuation price 1-5 of Item -> financial view or
2. last cost price or
3. average price.
Prices 1.-3. are prices per base unit of measure.
Calculation ends up with wrong results.
Correction result: Values of valuation price 1-5, last cost price and average price are converted to per uom values of trade cost calculations quantity. Calculation works poperly.
5.1.2.1 Calculation – General
RFR-016423 Correction
Framework: Calculation
Application: Compare product cost calculations
View: Tab “Calculation details”
Action: Save
Category: Exception
Problem: If two (or more) product cost calculations are compared which deviate by their process structures an exception occurs on saving product cost calculation comparison.
Correction result: It is possible to compare two (ore more) product cost calculations with different process structures. No exception occurs.
5.1.3 Inventory management
5.1.3.1 Delivery orders
RFR-016423 Correction
Class: com.cisag.app.inventory.delivery.order.log. OrderDetail, com.cisag.app.inventory.picking.order.log.OrderDetail
Method: toString()
Description: The methods are newly added. Refer to the Javadoc.
5.1.3.2 Inventory count
RFR-016423 Documentation
The following help documents have been changed according to new functionality “Inventurdifferenzliste”:
– “Inventurzähllisten”
– “Vorgehensweisen: Inventurzähllisten”
– “Vorgehensweisen: Inventuren”
RFR-016423 Correction
Framework: Inventory management
Application: Cockpit: Inventory counts
View: n.a.
Action: Initiate line items
Category: Ergonomics
Problem: In the parameter view the fields voucher date setting and voucher date were displayed although they were not used.
Correction result: The two fields have been removed from the patameter view.
5.1.3.3 Picking orders
RFR-016423 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Complete picking order…
Category: Exception
Problem: Completing many picking orders at the same time could cause a deadlock and at least an exception and abort of the process.
Correction result: From now the completing process will work as expected because all running completing processes will sort the detail lines by the same item order.
5.1.3.4 Receipts of goods
RFR-016423 Correction
Framework: Inventory Management
Application: Receipts of goods
Category: Unexpected behavior / Ergonomics
Problem: If a receipt of goods instance has the type “Customer return” with the return reference type value “Customer return” the order assignments data is not changeable for all cases but an order assignment that belongs to an empties receipt line item. By mistake the field “Receipt quantity (1st item unit)” was changeable although it should not be. After a try to change the data an error message occurs that the data can not be changed.
Correction result: Now also this field is not editable as expected in such a case.
5.1.4 Planning
RFR-016423 Correction
Framework: Planning
Application: Material Requirements Planning
View: n.a.
Action: all planning actions
Category: Unexpected behavior
Problem: Delivery dates were earlier than configured in delivery calendar in case the item had a receipt trainsitional time configured.
Correction result: The receipt transitional time is added to the delivery calendar dates as working days and the planning examines demand dates according to receipt dates computed from the delivery calendar dates.
RFR-016423 Correction
Framework: Material requirements planning
Application: Material requirements planning
View: n.a.
Action: “…and execute planning”
Category: Unexpected behavior
Problem: An item is planned with forecasts. One or more demands are in pre period with respect to forecast period.
Planning parameter “Prior period’s forecast results” is set to “Forecasts and issues”. This means: in first forecast period forecasts and issues are offset against each other.
This does not work. A result is a to high quantity of first recommendation.
Correction result: In above described context offset of forecasts and demands works as expected. First recommendation is properly adjusted.
RFR-016423 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer data and execute planning
Category: Ergonomics
Problem: No problem
Correction result: Technical redesign of transferring internal / external purchasing data of items. This is a preparation for a subsequent adjustment for faster transfer.
RFR-016423 Correction
Framework: Planning
Application: Material requirementy planning
View: n.a.
Action: all planning actions
Category: Unexpected behavior
Problem: When a demand and a receipt are at the same day and both combined with the projected quantity yield a new projected quantity higher or identical to the minimum inventory level, there was a minimum level underrun detected and a recommendation created in case the demand whithout the receipt would yield a projected quantity below the minimum inventory level. The reason was that the receipt was ignored on that day and loaded later when the next demand was analyzed. The problem existed only in planning engine version 4.
Correction result: Receipts for a given day are added to the projected quantity of that day before the level underrun detection logic is called for this day, so the logic works with the correct projected quantity for the examined day.
5.1.4.1 Material requirements planning
RFR-016423 Correction
Framework: Planning
Application: Material requirements plannig
View: n.a.
Action: Transfer planning data and execute planning
Category: Ergonomics
Problem: Organizations are transfered as planning data for a planning run. But this is done without the information which the assigned calendar keeps. This are:
1. What is the first day of week (Monday or Sunday)
2. How many days has first week of year for which a calendar is set
Up to now a planning calendar is set up with default values:
a. First day of week is always Monday
b. Number of days of first week is always 1 day
Up to now now, problem is known due to using planning calendar with this default values.
Correction result: Nevertheless transfer of calendar is extended. Values 1. And 2. are also transfered and are used for setting up planning calendars.
Attention: After implementation a backup file from generated before implementation cannot be opend anymore.
RFR-016423 Correction
Framework: Material requrements planning
Application: Material requirements planning
View: n.a.
Action: … and execute planning…
Category: Unexpected behavior
Problem: A product uses as a default production method a bill of resources (BOR). All operations of assigned routing are skipped due to formula and conditions. A recommendation for the product is generated. But for none of the material used by BOR (wether assigned to operations or not) a secondary demand is generated. Hence no recommendation is generated (which probably is necessary if demand would exist).
Also operations are skipped if they have no resources assigned (skipped because of conditions). This also may lead to a situation described above.
Correction result: In above described context secondary demands of material of BOR are generated while recommendation of product is created. If the secondary demands cause a under run of coverage also recommendations for this demands are created.
Please note: If default production method is a bill of material (BOM), secondary demands are generated.
If default production method is a combination of BOM and routing, secondary demands are generated even if all operations of routing are skipped.
Attention: After implementation a backup file from generated before implementaion cannot be opend anymore.
5.1.4.2 Planning – General
RFR-016423 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Save backup file
Category: Exception
Problem: An exception occured when saving backup file of planning. This happens if a planned item uses forecasts.
Correction result: Saving backup file of planning works as expected. No exception occurs.
5.1.5 Production
RFR-016423 Correction
Framework: Production
Application: Routings
View: n. a
Action: Change of operation in the editor
Category: Unexpected behavior
Problem: When overwriting the operation with another operation, the default values are not updated.
Correction result: When overwriting the operation with another operation, the default values are updated now.
RFR-016423 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Split…
Category: Exception
Problem: Unit of measure (uom) of production orders quantity can be base unit of item as well as every inventory managed packaging unit.
1. A production orders quantity uom is a inventory managed packaging unit. A receipt of goods is done but with a quantity using base unit of item. The receipt of goods results in a partial reporting of quantity.
If subsequently the production order is split an exception occurs due to improper adding of quantities of variaous unit of measures.
2. A production orders quantity uom is a inventory managed packaging unit. A receipt of goods is done but with a quantity using base unit of item. The receipt of goods results in a complete reporting of quantity.
If subsequently a rescheduling of production order is done with a higher order quantity, status of reporting remains “completed”.
Correction result:
1. In above described context a splitting of production order works as expected. No exception occurs.
2. In above described context status of reporting changes from “completed” to “partial”.
RFR-016423 Extension
Framework: Inventory
Application: Cockpit: Equipment
View: n.a.
Action: n.a.
Category: New application
Description: The new cockpit enables users to get an overview of equipment instances: the amount of their wear and wear capacity, their requirement origin and in which status they currently are and will be next.
RFR-016423 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Change multi-site production operation
Category: Unexpected behavior
Problem: When changing the multi-site production operation in the editor, the default values are not updated.
Correction result: When changing the multi-site production operation in the editor, the default values are now updated.
RFR-016423 Correction
Framework: Planning
Application: Material requirements inquiry
View: n.a.
Action: Refresh (Load)
Category: Exception
Problem: If an item is planned for inventory packaging units and is internally purchased, an exception occurs if data is displayed by application “Material requirements inquiry”.
This happens, if “Unit of measure” field in selection area is switched from one to another unit.
Please note: Standard behaviour is: “Unit of measure” field is not editable.
Correction result: In above described context no exception occurs on switching from one unit to another.
RFR-016423 Extension
Framework: Inventory
Application: Cockpit: Equipment History
View: n.a.
Action: n.a.
Category: New application
Description: The new cockpit enables users to see in a chronological order changes made to equipment items, including the corresponding requirement origin and the attached resource.
5.1.5.1 Production orders
RFR-016423 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Save
Category: Exception
Problem: -Load Production Order
-Clear automatic feedback checkbox
-Save button -> exception
Correction result: -Load Production Order
-Clear automatic feedback checkbox
-Save button -> no exception
RFR-016423 Correction
Framework: Production
Application: Production order
View: n.a.
Action: Dispatch
Category: Unexpected behavior
Problem: A process structure for a product P has at least one semi-finished product SF. Process structue of semi-finished product SF uses a routing with more than one operation. The ressources of last operations “LastOp” have conditions assigned so that in the course of scheduling none of the resources can be used.
A production order with product P is dispatched multilevel. A result of dispatching is that semi-finished product SF is not in the material list of dispatched production order. Also the sub-order for the semi-finished product does not exist.
Correction result: In the above described context the semi-finished product SF is member of the material list of the dispatched order. For semi-finished product SF a sub-order does exist. As the operation “LastOp” within this sub-order has no resources assigned this operation is skipped and is not in the list of operations of sub-order.
Please note:
1. Skipping operation with no ressources assigned (because filtered by conditions) is a common behaviour
2. If material is assigned to such a skipped operation this material is assigned to next operation. In a multi level structure this may also be an operation at the parent level (also a common behaviour).
3. Application “Bill of materials” can display the process structure in “Tree view”. Here operations without assigned ressources are displayed. Depending on the conditions (they can be related to item or top leve item) a production item must be specified in selection fields of tree view. Also “Level from/To” must be specified properly.
RFR-016423 Correction
Framework: Production
Application: Bills of material, Routings
View: n.a.
Action: Duplicate, save
Category: Unexpected behavior
Problem:
1. Duplicate BOM immediately (Confirm warnings checkbox is NOT checked) –
nothing happens: Bom is not duplicated and there is no error/warning about the reasons.
2. Duplicate BOM immediately/in batch (Confirm warnings checkbox is checked) – Bom is duplicated but there is no information about replaced item.
3. Duplicate Routing with e.g. blocked operation immediately – nothing happens: routing is not duplicated and there is no error/warning about the reasons.
4. Duplicate Routing without constraints immediately – routing is duplicated but there is no information about replaced operation.
5. Saving BOM with an incorrect material position containing a replacement item – after confirming the warnings, the actual error messages are not displayed and an incorrect position is created.
Correction result:
1. Duplicate BOM immediately (Confirm warnings checkbox is NOT checked)
– nothing happens: Bom is not duplicated but there is error/warning about the reasons.
2. duplicate BOM immediately/in batch (Confirm warnings checkbox is checked) – Bom is duplicated and there is information about replaced item.
3. Duplicate Routing with e.g. blocked operation immediately – nothing happens: routing is not duplicated but there is error/warning about the reasons.
4. Duplicate Routing without constraints immediately
– routing is duplicated and there is information about replaced operation.
5. Saving BOM with an incorrect material position containing a replacement item – After confirming the warnings, the actual error messages are now displayed and an incorrect position isn’t created.
5.1.5.2 Resource capacities
RFR-016423 Correction
Framework: Production
Application: Resource Utilization
View: Selection view
Action: Refresh
Category: Exception
Problem: If selection field “Time period” contains a invalid period of time or invalid date (e.g. 01.11.2022 – 31.11. 2022; 31.11.2022) an exception occurs.
Correction result: If selection field “Time period” contains a invalid period of time or invalid date a proper error message is displayed.No exception occurs.
5.1.6 Sales
5.1.6.1 Customer invoices
RFR-016423 Correction
Framework: Sales
Application: Sales orders, Distribution orders, Customer invoices
Action: Validate order details, Create and cancel customer invoices
Category: Invalid data / Unexpected behavior
Problem: If a sales order line item or a distribution order line item contains some “Order line item value discounts” and a positive customer invoice exists (invoice) and also a negative customer invoice with the negated quantity (credit note) it can occur that the invoiced quantity is zero but the considered “Order line item value discounts” are not zero. So as result the credit note contains a higher value as the invoice.
Correction result:
1. The customer invoice generation was changed:
– If the order line item was invoiced (invoiced quantity is not zero) and changes by the current invoice to zero the new invoice line item will contain and use the “Order line item value discounts” in that way that not only the invoiced quantity changes to zero; also the considered “Order line item value discounts” will be set to zero as result.
– In all other cases the behavior was not changed. So a customer invoice generation uses the difference value of the current order data and the data that was considered already by previous invoices.
2. Sales and distribution orders: New warning for order line items if the invoice status is different from “Not invoiced” and some “Order line item value discounts” data changes.
3. Cancel customer invoice: New warning within the “cancel validation” for the case that an invoice is based on some order line items with “Order line item value discounts” and the current invoice is not the last invoice of such order line items.
Hint: In the future, there might be some extensions to handle this or all kinds of discounts in an other way so that this warning would be not needed any more.
Data update: To correct the existing data you have to cancel the credit note customer invoice and create it again. Also other problems in this context can be solved to cancel all relevant customer invoices and create them again.
5.1.6.2 Sales – General
RFR-016423 Correction
Framework: Sales
Application: Sales quotations, Sales orders
Action: Change kit line item quantity
Category: Invalid data / Unexpected behavior
Problem: If a main line item is a kit main detail and has some configuration data, the kit components will be removed by mistake in some cases.
Correction result: Now kit components will not be removed any more in this case.
5.1.6.3 Sales quotations
RFR-016423 Correction
Framework: Sales
Application: Customer proposals
Action: Import
Category: Unexpected behavior
Problem: The import filter definition provides the attributes “proposalCounter”, “proposalType” and “proposalVersionStatus” although the import of these attributes is not supported.
Correction result: Now the three attributes have been removed from the import filter definition. The export is supported as before.
RFR-016423 Correction
Framework: Sales
Application: Sales quotations
Action: Change invoicing terms
Category: Invalid data / Unexpected behavior
Problem: If sub line items are price relevant (e.g. kit components), the price data of proposal sub line items will not be refreshed by the “Change invoicing terms” functionality (e.g. in case of price changes). In case of sales orders the functionality is OK.
Correction result: Now the functionality works also for sales quotations as expected.
5.1.7 Workflow Management
5.1.7.1 Job titles
RFR-016423 Correction
Framework: Workflow Management
Application: Job titles
View: n.a.
Action: save, validate
Category: Unexpected behavior
Problem: It was possible to add a partner relationship to non existing person. After that, this partner is not displayed.
Correction result: Validate, if a partner is an existing partner person and show error message if necessary.
5.2 Comarch Financials Enterprise
5.2.1 Financial accounting
5.2.1.1 Posting
RFR-016423 Correction
Framework: Inventory management
Application: Inventory postings.
View: n.a.
Action: Save an inventory posting with transaction type account classification specification.
Category: Unexpected behavior
Problem: The transaction type account classification was not considered for manual inventory postings.
Correction result: The transaction type account classification is now also considered in manual inventory postings
5.3 System development
RFR-016422 Documentation
The following English help documents have been corrected: “Import Data Automatically”, “Import Filters”, “Reorganize Data Exchange Log Entries” and “Import Multiple Files per Workflow”.
RFR-016422 Correction
The text of the “Verbindung testen” button in the customizing function “LDAP-Synchronisation” has been corrected (concerns German only).
RFR-016422 Ergonomics
Update of the Polish user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016422 Documentation
The new help document “Entwicklungsobjekt: Dateiauslieferung” (com.cisag.sys.help.softwaredevelopment.developmentobjects. DevelopmentObjectFileDelivery) has been created.
RFR-016422 Ergonomics
Update of the French user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016421 Correction
Framework: n.a.
Application: n.a.
View: n.a.
Action: Open an application in a new window by selecting “Open in new window” on the context menu does not work properly.
Category: Unexpected behavior
Problem: For example:
– Goal: application “Cockpit: sales orders/line items” should be opened in a new window from application “Sales orders”
Steps:
– Open Application ” Sales orders”
– Press right mouse button on the sales order number to get context menu.
– Select “Sales” entry.
– Select “Cockpit: sales orders/line items”.
– Press right mouse button again.
– Select “Open in new window”
– Result: Application “sales orders” will be opened in new window instead “Cockpit: sales orders/line items”. It is not correct.
Correction result: Application “Cockpit: sales orders/line items” will be opened in new window properly.
5.3.1 Data exchange
RFR-016421 Extension
Framework: System Management
Application: BIS REST import web service (/services/rest/com.cisag.sys.tools.bi.rest.Import)
Category: New action
Description: In the web service, an option was added to return the error file contents if the import failed. The error file contents are transmitted if the parameter ReturnErrorData=true is specified as URL query paraemter in the web service call. The error file contents usually contains the error messages.
Framework: System Management
Application: BIS REST import web service (/services/rest/com.cisag.sys.tools.bi.rest.Import)
Category: Unexpected behavior
Problem: Calling the web service could create temporary files in the applicaiton that are not properly deleted after some time.
Correction result: Temporary files used by the webservice are deleted after use.
5.3.2 GUI
5.3.2.1 Look & feel
RFR-016421 Correction
Framework: All
Application: Cockipts and applications with customizable tables
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: CDS theme only: The background color of the focussed row is too close to the regular row background and do not conform to the color defined by the CDS design.
Correction result: The background color of the focussed row is changed to the color defined by the CDS design.
5.3.3 Kernel
RFR-016421 Correction
Framework: system management
Infrastructure: shared cache
View: n.a.
Action: n.a.
Category: Exception (Error)
Problem: Size of dynamic objects was miscalculated. That could lead to an out of memory error, if very large dynamic objects were used.
Correction result: Size is now computed correctly.
5.3.4 System – General
RFR-016422 Correction
Framework: System management
Application: Change journal query
View: n.a.
Action: Update
Category: Ergonomics
Problem: The change journal might contain references to business object classes that don’t exist anymore, e.g. deleted extensions. This would result in exception “object meta data not found for object with GUID xxx” and termination of the application.
Correction result: The application displays the evaluable data, error messages point to outdated references.
5.3.5 Workflow
5.3.5.1 Activities
RFR-016421 Correction
Framework: Workflow Management
Application: Activity
View: n.a.
Action: n.a.
Category: Exception
Problem: NPE was being thrown when user attempted to complete interactive email node.
Correction result: NPE should not be thrown anymore.