| Release | Comarch ERP Enterprise 6.3 |
| Release date | 03.01.2025 |
| 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-016524 – RFR-016526
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 “Support deliveries query” 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 update 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 Support delivery query 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 delivery 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-Fix20.”
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 to the message server or to 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-Fix20
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix19 will be upgraded to CEE630PB-Fix20.
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 is 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 Rework after installation
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
No data updates have to be carried out.
5 Contained changes and extensions
5.1 Application development
RFR-016526 Ergonomics
Update of the French language user interface.
The installation does not affect the texts. You obtain the translations in the support deliveries from the support center.
RFR-016526 Ergonomics
Update of the Polish language user interface.
The installation does not affect the texts. You obtain the translations in the support deliveries from the support center.
5.1.1 Base
5.1.1.1 Contracts/RFQs/Quotations/Orders
RFR-016526 Correction
Action: Document reorganization
Category: Unexpected behavior
Problem:
1. In some rare cases, a self-order reference exists (the source and target orders are the same). If such a reference is present, it will prevent the reorganization.
2. “Debtor credits” application: The standard action “Reserve automatically” and “Reduce unallocated credit reservations” are enabled also if the current instance is marked for reorganization.
Correction result:
1. Now, all order references in which source and target order are the same will be ignored.
2. Now both actions are disabled for instances that are marked for reorganization.
5.1.1.2 Exchange rates
RFR-016526 Extension
Framework: Base
Application: Exchange rates
View: n. a.
Action: n.a.
Category: Required changes
Description: The following changes have been made:
1. Some columns must also be right-aligned.
2. In the tooltip, the quote that is not entered but calculated by reciprocal value formation should be displayed with 15 decimal places and use the round sign ˜ (or ‘\u2248’) instead of the equal sign.
3. The prices in the table that are displayed in a different notation from the one entered or saved, i.e. those that cannot be edited, should be displayed with 15 decimal places and in italics.
5.1.1.3 Fiscal years
RFR-016526 Correction
Framework: Base
Application: Fiscal years
Action: Next period status (ERP)
Category: Invalid data / Unexpected behavior
Problem: The period status can be changed to “Temporarily closed” without a warning and to the “Closed” status without an error message even if an open supplier invoice is present with a “date” value within this period. This is especially a problem for internal supplier invoices that belong to a customer invoice since here, the “date” attribute value cannot be changed manually.
Correction result: Now, the warning and error messages will be send within the “Fiscal years” application as expected. Please note that different messages will be used for supplier invoices with the status values “Invalid” and “Released”.
Technical information: The class “com.cisag.app.purchasing.log.FiscalPeriodSetPurchasingStatusHookImpl” has been corrected.
The coding of the class “com.cisag.app.sales.log.FiscalPeriodSetSalesStatusHookImpl” has been changed in analogy (without any functional change).
5.1.1.4 Item characteristics
RFR-016526 Correction
Framework: Base
Application: Item characteristic classifications
Category: Invalid data / Unexpected behavior
Problem: The description (attribute “label”) of the “Item characteristic” is not always displayed within the content language of the current user.
Correction result: Now, the description will be displayed within the content language of the current user as well.
RFR-016526 Correction
Framework: Base
Application: Item characteristics
Action: Delete
Category: Exception / Unexpected behavior
Problem: If new item characteristics were not considered by the generation (no table column is present) and has a deletion marker, an exception occurs during the attempt to delete directly such item characteristics.
Correction result: Now the exception does not occur any more.
Hint: Please note that the “Generate table schema” action/application considers all item characteristics, those with a deletion marker as well.
5.1.1.5 Partners
RFR-016526 Correction
Framework: Base
Application: Partners
View: Financials
Action: Create new bank account
Category: Unexpected behavior
Problem: If IBAN is given, an account holder without a bank account must be possible
Correction result: The validation of a bank account is removed, an account holder without a bank account now is possible
5.1.2 Calculation
RFR-016526 Correction
Framework: Calculation
Application: Product Cost Calculations
View: Pre-calculation
Action: Change simulated costs / Save
Category: Unexpected behavior
Problem: If a warning that needed to be confirmed was displayed, saving was not possible after confirmation of the warning, due to an error in the locking logic.
Correction result: Saving after confirmation of warning is possible.
RFR-016526 Correction
Framework: Calculation
Application: Product Cost Calculations
View: Pre-calculation
Action: Change simulated price in editor
Category: Unexpected behavior
Problem: Changing the simulated price of a resource causes a change for all resources in the calculation to the same price.
Correction result: Changing the simulated price of a resource causes a change for all of the same resources. For all others prices, it stays the same.
5.1.2.1 Calculation – General
RFR-016526 Correction
Framework: Calculation
Application: Cockpit: Production orders; Product cost calculation
View: n.a.
Action: Cockpit: Production orders -> Generate calculations…; Product cost calculation -> Calculate…
Category: Unexpected behavior
Problem:
A. In the application “Product cost calculations”, a calculation of type “Calculation of the production order” is created with a “Valuation price” = “Price from price listing”. Material of the calculated product has well defined purchase prices from specified price listing.
Result: No purchase prices are retrieved. Instead, the substitution valuation price is retrieved. This is incorrect. The reason is the setting “Use target quantity” (see shelf) = “Use target quantities and target times”. This setting is correct but leads to a false mode of retrieving quantities for finding prices from price listing.
B. In the application “Cockpit: Production orders” for one or more production orders “Generate calculations…” is performed, also with a type “Destiny category” = “Calculation of the production order”. The dialog shown for this action has a not editable field “Use target quantity” = “Use actual quantities and actual times” set.
Due to the help document, this setting is wrong (the correct one is “Use target quantities and target times” as in context A).
C. In the application “Cockpit: Production orders”, the action “Generate calculations…” is performed with a type “Destiny category” = “Final calculation of the production order”. In this case, the field “Use target quantity” is editable with a default value of “Use actual quantities and actual times”.
This behavior is missing in an application “Product cost calculations” when a new calculation of a view “Final calculation of the production order” is created.
D. The logic of calculating quantities due to the setting “Use target quantity” does not make a difference between values “Use actual quantities and actual times” and “Actual quantities and actual times for completed line item” and acts as if the latter is set. Besides of wrong reported quantities of material and operations, this may lead to wrong prices. This is the case for a final calculation with completely reported material for which purchase prices should be calculated but instead, the replacement price is taken.
Correction result:
A. For the setting “Use target quantity” = “Use target quantities and target times” the quantities for calculating purchase prices are set up correctly and hence purchase prices are calculated correct.
B. The dialog for “Generate calculations…” sets “Use target quantity” = “Use target quantities and target times” when “Destiny category” = “Calculation of the production order” or “Pre-calculation with order reference”. Together with a correction A, the correct purchase prices are calculated.
C. Application “Product cost calculations” sets a default of a field “Use target quantity” correctly to “Use actual quantities and actual times” if a new final calculation is created. Only for a final calculation values of a field “Use target quantity” can be changed.
Please note: If a final calculation has been calculated successfully and the user changes value of a field “Use target quantity” this is (now) a relevant change of calculation settings. Therefore, this change switches a status of calculation to “Incomplete”. The calculation has to be done once again. This new behavior is a consequence of solving problem D.
D. The settings of “Use target quantity” (can only be set and changed in a final calculation); The setting “Use actual quantities and actual times”: The reported quantities are calculated for materials and operations only.
For “Calculation quantity” (product), the reported quantity is set.
The setting “Actual quantities and actual times for completed line item”: For material and operations which are reported completely, the reported quantities are calculated. Otherwise, the target quantities are calculated.
For “Calculation quantity” (product), the reported quantity is set if reporting is completely. Otherwise, the target quantity is set.
The setting “Use target quantities and target times”: For material and operations only the reported quantities are calculated.
For “Calculation quantity” (product), the target quantity is set if no report for product has been done yet. Otherwise, the reported quantity is set.
5.1.3 Inventory management
5.1.3.1 Delivery orders
RFR-016526 Correction
Framework: Inventory
Application: Delivery orders, Picking Orders
View: n.a.
Action: n.a.
Category:Unexpected behavior
Problem: The Hook-Interface “com.cisag.app.general.order.hook.log.HeaderApplyDefaultsHook” wasn’t called, although it’s contained in the hook-contract
Correction result: From now the Hook-Interface “com.cisag.app. general.order.hook.log.HeaderApplyDefaultsHook” will be called as expected.
5.1.3.2 Identifiers
RFR-016526 Correction
Framework: Inventory managment
Application: Identifiers
View: n.a.
Action: Load
Category: Ergonomics
Problem: Although the working area contained more elements than the view can display, no scrollbar was supported.
Correction result: If the working area contained more elements than the view can display, a scrollbar will be offered as expected.
5.1.3.3 Picking orders
RFR-016526 Correction
Framework: Inventory
Application: Picking orders
View: Delivery orders
Action: Add new detail line
Category: Exception
Problem: In some special cases, adding a new detail line leaded to an exception.
Correction result: From now, adding a new detail line will work as expected.
5.1.3.4 Reservations
RFR-016526 Correction
Framework: Inventory Management
Application: Reservations
View: Issues
Action: Reset reservation category
Category: Ergonomics
Problem: The action was not selectable after using the second view “Receipt and Inventory”
Correction result: The action is always selectable within the view “Issues” as expected.
5.1.4 Multi-site capability
5.1.4.1 Inter-company billing
RFR-016526 Correction
Framework: Base
Application: Inter-company billing
Action: Generate inter-company billing
Category: Invalid data / Unexpected behavior
Problem: If some base discounts are present but not used by all line items, the currency of these discounts is not set. So, in case of “Gross calculation”, some base discounts are visible but without a currency.
Correction result: Now, the values of all used base discounts will be initialized with the invoice currency so that this error does not occur any more.
Hint:
There is no data update application available to correct the wrong data; if needed, you have to cancel and recreate such invoices.
RFR-016526 Correction
Framework: Base
Application: Inter-company billing
Category: Unexpected behavior / Ergonomics
Problem: The field “Price origin type” is always not editable if the current value is “Price list” – a change to this value prevents a change back to the original or any other value.
The original reason was an authorization topic – the intention was that not every user can define manual prices for the “Inter-company billing”.
Correction result: If the data of the entry can be changed, now this field can be changed independently from the current value as well – so the behavior is the same as in the proposals/orders applications.
Hint: If not all user are allowed to change the “Price origin type” value, you can use the field authorization definitions for these restricted users.
5.1.5 Planning
5.1.5.1 Generate purchasing recommendations
RFR-016526 Correction
Framework: Purchasing
Application: Purchasing recommendations
View: n.a.
Action: New purchase recommendation
Category: Unexpected behavior
Problem: Adding a purchase recommendation manually by using a blocked item or blocked supplier was allowed without any message, although on this recommendation actions “Generate purchase orders” and “Generate purchase RFQs” cannot be performed as long as item and/or supplier are blocked.
Correction result: Trying to add purchase recommendation manually with a blocked item or/ and supplier will display an error now, which means that this kind of recommendation cannot be added anymore. Errors are the same as during action “Generate purchase RFQs”.
5.1.6 Production
RFR-016526 Correction
Framework: Production
Application: External operation transaction postings
View: n.a.
Action: Ship to external manufacturer
Category: Unexpected behavior
Problem: A production order has an external operation with some assigned material provided. In the application “External manufacturing operation postings”, for this external operation, a quantity is specified and subsequently “Ship to external manufacturer…”.
At least one of the assigned material providers is not available for shipment.
Result: A delivery order is generated with an externally manufactured item and a material provided except the one which is not available. There is no notification of user about the missing material provided.
However, it is not possible to ship the material provided later on when it is available. The only workaround has been to “Complete delivery order and perform output slip” for the generated delivery order and perform “External manufacturing operation postings” anew when all material provided is available.
Unfortunately, this workaround does not work anymore due to a problem which skips the problematic material provided again in the course of generating a delivery order, even though it is available.
Correction result: A new validation is introduced now which checks if all material provided is available for the process “Ship to external manufacturer” and outputs proper messages if not. Thus, the user can quit this process in that case.
If, despite this validations, a delivery order with material provided missing is generated, the workaround described above is working as expected.
RFR-016526 Correction
Framework: Inventory
Application: Inventory requisitions
View: Production equipment
Action: Create new
Category: Unexpected behavior
Problem: It was possible to manually create and save an inventory requisition in a view “Production equipment”, which could not be used in any way.
Correction result: When trying to create an inventory requisition in a view “Production equipment”, saving is not possible and error message INV-08602 appears.
RFR-016526 Extension
Framework: Production
Application: Production orders
View: n.a.
Action: dispatch
Category: Unexpected behavior
Problem: In case a production order was dispatched a 2nd time with a different earliest begin, latest end date, or switched scheduling direction,
the scheduling logic still used the scheduling base date of the very first dispatch to start the scheduling forward or backward from this old date.
Correction result: In case a production order is dispatched a 2nd time, the scheduling base date is recomputed from the earliest begin or latest end date depending on the scheduling direction and the scheduling logic will start from this recomputed date.
5.1.6.1 Production – General
RFR-016526 Correction
Framework: Calculation
Application: CalculationTypes
View: Ident view
Action: n.a.
Category: Exception
Problem: It was possible to set field “Product cost calculation type” = “Incomplete” in an application “Calculation types”. If such a calculation type is used in an application “Product cost calculation maintenance” on action “Create” an exception occurs.
The reason is that value of “Product cost calculation type” triggers the view of an application “Product cost calculation maintenance”. A value “Incomplete” in this context is not allowed.
“Product cost calculation type” = “Incomplete” is only used for calculations “on the fly” which are not intended to be saved persistently. An example is calculating a price for a configurable item in a sales order.
Correction result: In the application “Calculation types” it is not any more possible to set a field “Product cost calculation type” = “Incomplete”.
If the application “Calculation types” opens a calculation type with this value already set on a field “Product cost calculation type” is emptied so that user has to select a proper value when saving.
If the user creates a new calculation via the application “Product cost calculation maintenance”, using a calculation type with above mentioned wrong value a calculation of a target type “Pre-calculation” as a default value is created.
If the user generates new calculations via “Cockpit: Product cost calculations” using a calculation type with the above-mentioned wrong value calculations with a target type “Pre-calculation” as default value are created.
5.1.6.2 Production orders
RFR-016526 Correction
Framework: Production
Application: Cockpit: Production orders/Material line items, Cockpit: Production orders, Production orders
View: n.a.
Action: Calculate availability
Category: Unexpected behavior
Problem:
A. Some production orders have material line items with a material which is not onhand accounted. On creation, this material get availability status “No availability check”. If in “Cockpit: Production orders/Material line items” this material is selected for a performing action “Calculate availability..”
The result of this action is that material not onhand accounted gets an availability status “Not available”. This is not correct.
B. A production order is scheduled back or forward multiple levels and some sub-orders are generated. Due to the production order type, no availability check is on generation. This is done by the user, subsequently performing an action “Calculate availability…” (-> “Determine only availability status”) either by the application “Production orders” or “Cockpit: Production orders”.
The result: only for a main order calculation of availability is done, not for sub-orders.
Please note: if availability check has to be done on generation of production order/sub-orders (due to the setting of a production order type), this calculation is done for a main order as well as for sub-orders
Correction result:
A. Performing an action “Calculate availability..” via “Cockpit: Production orders/Material line items”, an availability status remains in status “No availability check” for a material which is not onhand accounted.
B. Performing an action “Calculate availability…” (-> “Determine only availability status”) either by an application “Production orders” or “Cockpit: Production orders” calculates and sets availability status for a main order as well as for sub-orders.
RFR-016526 Correction
Framework: Production
Application: Production orders, Routings, Operations
View: n.a.
Action: Dispatch, Dispatch and release, New dependency
Category: Exception
Problem: Creating a new dependency between the details with column “Overlap time” set to a non-time unit of measure and trying to dispatch that constraint caused an exception.
A value assistant for that column suggested each unit of measure, not only time-specific units.
An error about a wrong unit of measure triggers only in some cases, although setting in wrongly for each case caused exception then.
Correction result: Now, the setting unit is different than a second, minute or hour displays an error message in every case.
Now, the value assistant shows only an allowed unit of measure.
The dispatching constraints with a wrong unit of measure (created before that fix) will set “Overlap time” to zero with the same unit as “Target processing time”.
5.1.7 Purchasing
5.1.7.1 Supplier invoices
RFR-016526 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Manually assign purchase order line item to selected line item / Manually assign receipt of goods line item to selected line item
Category: Invalid data / Unexpected behavior / Ergonomics
Problem: If the purchase order has a specified costing data (“cost centre” “cost objective”), either as one value or as splitted values, the supplier invoice did not use the specified data in all cases. The data will be used only if the “cost centre / cost objective” combination has not been already present.
Correction result: Now, in the case that a “Cost centre / cost objective”, the combination has been already present, the quantities and values will be increased with respect to the added data.
RFR-016526 Correction
Framework: Purchasing
Application: Supplier invoice
Action: Apply defaults and logics about the “account” attributes
Category: Invalid data / Unexpected behavior
Problem: Since some time, the usage of the purchasing customizing property “Account origin for additional cost invoices” was restricted to additional cost invoices (purchasing or distribution) only.
However, this was not enough for cases where “General ledger entries” is activated for the relevant financials organization.
Correction result: The “Account origin for additional cost invoices” is used now also for “regular” invoices and will be copied also into their correction invoices, but it has an effect only on additional invoice line items.
To avoid some further problems, the customizing value “Use “from order”” will be used now only for invoices with activated “General ledger entries”.
Also some further problems have been corrected especially for line items for that an expense account is relevant.
Hint: Please note that the needed documentation changes will be performed by an extra correction order.
5.1.8 Sales
5.1.8.1 Customer invoices
RFR-016526 Correction
Framework: Sales
Application: Customer invoices
Action: Create/generate customer invoice
Category: Unexpected behavior
Problem: If the ISO code of an output language (from the invoice customer) has more than two signs (e.g. “en-us”), a specified item description in this language will not be determined, because within the system engine the language code has no separator (for example here “enus”).
Correction result: Now, the separator will be removed before reading the item data by the system engine.
Please note that in case of an empty item description in the output language the database default language will be used as before.
Hint: In addition to that, some customer invoice coding has been corrected that did not consider the output language for the “price uom” code.
5.1.8.2 Customer returns
RFR-016526 Correction
Framework: Sales
Application: Customer returns
Actions: Generate or change credit note orders and Generate or change replacement delivery orders
Category: Invalid data / Unexpected behavior
Problem: If a sales order is generated by a customer return and a line item that is relevant for the save limit (typically the sixteenth line item) is a kit, the sales order cannot be created because of the error message “SAL-00768” (Kit needs at least one kit component).
The reason is that the customer return tries to save the sales order before adding the relevant kit components.
Correction result: Now, it will be ensured by the customer return order generation that all kit components are added before the sales order will be attempted to save. So the problem does not occur any more.
5.1.8.3 Sales orders
RFR-016526 Correction
Framework: Inventory
Application: Sales orders, distribution orders, production orders
View: n.a.
Action: Generate picking orders and output picking slips, Generate delivery orders with order reference
Category: Unexpected behavior
Problem: Since changing the inventory recommendation determination to the proposer algorithm (CEE 6.0), the inventory recommendation determination did not consider identifier demands of concurrent orders when creating delivery orders/picking orders.
Correction result: From now, the identifier demands of concurrent orders will be considered again.
Technical information: The new behaviour can be reset to the status prior to this correction using the ‘com.cisag.app.inventory.picking. log.IgnoreIdentifierDemandWhenProposing’ property:
set com.cisag.app.inventory.picking.log. IgnoreIdentifierDemandWhenProposing=true
5.1.8.4 Sales quotations
RFR-016526 Correction
Framework: Sales
Application: Customer proposals
Action: Print
Category: Invalid data / Unexpected behavior
Problem: If a customer proposal uses the “Net kind of pricing” and has some freight costs the standard report contains an unexpected value for the printed “Total value”; also the “End value” is missing in some cases.
Correction result: The standard report has been corrected.
5.1.9 Storage Location Control
5.1.9.1 Inventory requisitions
RFR-016526 Correction
Class: com.cisag.app.inventory.order.log. DemandElementHookWarehouseOrderImpl
Method: n.a.
Description: The method getDemandElementInfo(byte[] header, byte[] detail, byte[] subKey, short availabilityType) now fully supports the specification of a sub key with the value not equal to ZEROGUID.
5.1.9.2 Storage locations
RFR-016526 Correction
Framework: Inventory management
Application: Storage locations
View: n.a.
Action: Create a new storage location
Category: Unexpected behavior
Problem: If the type was not yet specified, the fields for replenishment were not displayed in the item definition.
Correction result: If the type is not specified, all fields are displayed in the item definition, including those for replenishment.
RFR-016526 Correction
Framework: Inventory Management
Application: Warehouses
View: n.a.
Import of simple zones
Category: Unexpected behavior
Problem: When you attempted to import a simple zone, an error message disabled the import.
Correction result: Simple zones can be imported as expected.
5.2 System development
RFR-016524 Correction
Framework: All
Application: All cockpits
View: n.a.
Action: n.a.
Using other fields with type values et as search field
Category: Invalid data
Problem: When using other fields of a selection field type as search characteristics, not all results are found in all cases. If no values were saved in the additional fields, these data records were not found.
Correction result: If all values are selected, all results are found.
RFR-016524 Correction
Framework: System management
Tool: crtsas, chgsas
Category: Ergonomics
Problem: The parameter svmStartParameters has no effect
Correction result: The parameter is removed
RFR-016524 Correction
Framework: Software development
Application: Text editing cockpit
View: Import texts/translations
Action: Import Excel file(s)
Category: Exception
Problem: If the file to be imported is corrupt, then the parser can’t read it.
Correction result: If just some rows can’t be parsed, then the exception is caught. A message is written in the log that the row in question will be skipped.
RFR-016525 Correction
Framework: Software development
Application: Text editing cockpit
View: Import texts/translations
Action: Import Excel file(s)
Category: Exception
Problem: If the file to be imported is corrupt, then the parser can’t read it.
Correction result: If just some rows can’t be parsed, then the exception is caught. A message is written in the log that the row in question will be skipped.
5.2.1 Application server
RFR-016524 Correction
Framework: System management
Application: Cockpit: Data exchange log entries
View: n.a.
Action: Open with pin
Category: Unexpected behavior
Problem: The filter field “Responsible user” is filled with the current user, ignoring the user in the pinned parameters
Correction result: The field is filled with the user from the pinned parameters
5.2.1.1 JobControl
RFR-016524 Correction
Framework: System Management
Installing software updates
Category: Unexpected behavior
Problem: Entity menu default entries for fields (field-specific defaults) may be lost after software updates have been installed, or after the tool shell command “rgzusrentmnu -withoutTarget” was executed. The issue occurs if some inconsistencies in the entity menu were detected, and a message SYS-1105 was written into the application server log during the installation or tool execution.
Correction result: The problem is resolved.
5.2.2 GUI
5.2.2.1 Grid control
RFR-016524 Correction
The error has been fixed. Now the table will also update correctly after “arrow keys”.
RFR-016524 Correction
Now the horizontal alignment is taken from the editor if no DataDescription and no Path was found.
5.2.3 System – General
RFR-016524 Correction
Framework: Software Development
Reading a relationship in a data view
Category: Exception
Problem: When reading a “1..n” relationship of a data view, where the relationship has the PERSISTENT property, an exception “java.lang.IllegalArgumentException: wrong number of arguments” appears. The exception is thrown when program code iterates over the com.cisag. pgm.util.OneMany object which is returned by the relationship’s retrieve…() method.
Correction result: The relationship’s target objects are returned.
Framework: Software Development
Reading a relationship in a data view
Category: Exception
Problem: When reading a “1..n” relationship of a data view, where the relationship is from a data view extension and the data view is of “view” visibility, a ClassCastException exception
similar to ” java.lang.ClassCastException: class com.sun. proxy.$Proxy123 cannot be cast to class com.cisag.pgm.base.DataAccess … at com.cisag.pgm.util. OneManyBase.get …” is thrown.
Correction result: The relationship’s target objects are returned.
5.2.4 Workflow
5.2.4.1 Activities
RFR-016524 Extension
Framework: Workflow
Tool:
View: n.a.
Action: n.a.
Category: Exception
Problem: In some cases, an activity cannot be deserialized after a system update. The scheme of the contained, serialized business object instance was changed.
This leads to a parser exception and the activity cannot be dealt with.
Correction result: Excute tool com.cisag. sys.workflow.log.GetRidOfDefectedActivities on the toolshell.
It scans activities on all OLTP databases and the repository databases that are not already cancelled or done.
If such an activity cannot be parsed, i.e. throws a ParserException, it will be set to canceled.
5.2.4.2 Workflow templates (transport)
RFR-016524 Correction
Framework: Workflow
Application: Process Definitions
View: n.a.
Action: n.a.
Category:Ergonomics
Problem: When the process definition is loaded, no message informs about it.
Correction result: Works as expected, excepts only the first load is not informed.