| Release | Comarch ERP Enterprise 6.3 |
| Release date | 19.08.2024 |
| 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-016506 – RFR-016508
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-Fix17.”
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-Fix17
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix16 will be upgraded to CEE630PB-Fix17.
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.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.
4.2.1 UPDBUG028844
Updates the combination of the begin value in InventoryOnhandPeriodSummay BO.
Checks the currency combination of the begin value with a zero amount of the inventory onhand period summaries and updates it if it is different to the used currency combination with the used currency combination.
5 Contained changes and extensions
5.1 Application development
RFR-016508 Correction
Framework: Production
Application: Cockpit: Production orders/material line items ,Cockpit: Production orders/work line items
View: Cockpit: Production orders/material line items ,Cockpit: Production orders/work line items
Field: Line item output
Category: Unexpected behavior
Problem: Default view of field “Line item output” shows all 5 possible choices instead of “All” text.
Changing value of this field and then perform action “New” did not resets value of this field to default one.
Correction result: If all choices are set for “Line item output” field it displays “All” text in every case.
Performing action “New” is always changing value of this field to default value of chosen view.
RFR-016508 Correction
Framework: Inventory
Application: Picking Orders
View: n.a.
Action: Update
Category: Unexpected behavior
Problem: Changing the warehouse for an identifier assignment line was not possible, if the warehouse value of the detail line of that assignment has not a valid QS-status. The message INV-01233 was displayed.
Correction result: As expected, from now changing the warehouse for an identifier assignment line will not depend on the QS-status of the detail line.
5.1.1 Base
5.1.1.1 Base – General
RFR-016508 Ergonomics
Applications
Category: Unexpected behavior / Ergonomics
Problem: In some cases, “1-n” data will be maintained with the help of the class com.cisag.app. general.gui.factories.OneManyDependentEditor.
If new data and deletion is supported the “set/remove deletion marker” action is not directly active after adding a new row.
The “set/remove deletion marker” action will be activated later by an extra “round trip” or action (e.g. “validate”).
Correction result: Now the “set/remove deletion marker” action will be activated directly after adding a new row.
Technical hints: The new functionality is implemented within the method “protected void addRows(List preparedDependents)”.
If the “toggle deletion marker” action is not supported in some specific cases (implemented in an own “public void setValue(Object value, DataDescriptionModification metadata)” method) you have to override also the “addRows” method and disable the action here with respect to the relevant rules.
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016508 Correction
Application: Order applications with an action based on the class “com.cisag.app.general.order.ui.DetailSelectionList”
Category: Invalid data / Unexpected behavior
Problem: If an order application provides an action that is based on the class “com. cisag.app.general.order.ui.DetailSelectionList” (e.g. sales order action “Cancel line items”) and the selection list shows more than 100 line items the selected line items will not be used in every case for the action.
Correction result: Now the selection will be considered as expected.
5.1.1.3 Items
RFR-016508 Correction
Framework: Sales, Purchasing
Application: All applications which call the class “com.cisag.app.general.item.log.ItemsImpl”
View:n.a.”
Action:n.a.
Category: Unexpected behavior
Problem: There was problem with the use of customer classification-specific article data.
Correction result: Applications that call this Method work correctly
Technical information: in the class “com.cisag.app.general.item.log.ItemsImpl” (Version 40.0:6.3.0) an error was found in the method “retrieveCustomerClassificationItems(byte[], byte[][], byte[])”
Within the last loop, the “cache.load” method is passed “customer” as the second parameter, the correct parameter should be “items[i]”.
5.1.2 Document Management
RFR-016508 Correction
Framework: Document management, Base
Application: Items, Partners
View: n.a.
Action: Change logo
Category: Unexpected behavior
Problem: In the window for changing logo available in Partners and Items application, there was the option “Semiramis documents” and it was possible to choose any file, which would be assigned to the logo.
In the same window it was possible to type any file, including invisible files for Graphics filter and it would be assigned to the logo.
Correction result: “Semiramis documents” filter is now not available for changing the logo.
New validation has been added to check if the document selected with typing or after updating new file is according to “Graphics” filter.
Technical information: Supported “Graphics” files are: bmp, gif, jpeg, png, svg+xml, tiff, x_emf, x_icon, x_png, x_wmf, x_xbitmap.
RFR-016508 Correction
Framework: Document management
Application: All applications with Create document action, Documents
View: n.a.
Action: Create document, Insert reference, Create notes dialog
Category: Unexpected behavior
Problem: Customizing setting “Document reference type for documents” and preferred document reference type from “Document types” application were not used when creation documents with references.
Always Customizing setting “Document reference type for notes” was used.
Correction result: Currently, logic takes preferred document reference type from “Document types” application. If there is no preferred reference, type logic takes it from Customizing according to document kind (Document / Note).
If the setting “Document reference type for documents” is empty, logic would use “Document reference type for notes” for compatibility reasons.
5.1.2.1 Documents
RFR-016508 Correction
Framework: Document management
Application: All applications having Create document action, Documents
View: n.a.
Action: Create document, Create note dialog
Category: Exception
Problem: Exception occurred when calling “Create document” action from context, which does not have Document management customizing function activated.
Correction result: Exception does not occur when action “Create document” is being called from context without activated Document management function.
5.1.3 Inventory management
5.1.3.1 Delivery orders
RFR-016508 Correction
Framework: Inventory
Application: Delivery slips
View: n.a.
Action: n.a.
Category: Invalid data
Problem: The outputted documents “delivery slip” and “dispatch advice” did not show the correct values for gross weight, net weight, gross volume and net volume from the database.
Correction result: From now the documents will show the correct values.
5.1.3.2 Inventory count
RFR-016508 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Action: Report of a different storage unit
Category: Unexpected behavior
Problem: If a different storage unit and an item inventory difference were reported, no difference would not be detected at closing.
Correction result: If a difference is detected this difference will be corrected at closing as expected.
RFR-016508 Correction
Framework: Inventory management
Application: Inventory counts
View: n.a.
Action: Delete
Category: Unexpected behavior
Problem: The automatic deletion of inventory count lists before the inventory count deletion looks not save.
Correction result: To avoid errors during the deletion of inventory counts, an additional validation will be executed now.
5.1.3.3 Receipts of goods
RFR-016508 Correction
Framework: Production
Application: Material issue posting
View: n.a.
Action: Post
Category: Exception
Problem:
Context: 1. Production order without picking. Production warehouse is empty!
2. Material is reported automatically on receipt of goods of production order
3. Customizing -> Inventory Management -> Reservations -> Field “Date tolerance limit” must be set to a positive number, e.g. 10 days
4. Demand of material is reserved against a planned receipt (not against inventory!). Delivery date of planned receipt must be: actual date + Date tolerance limit + x days. Demand date of material must be within range delivery date – Date tolerance limit
If in this context a receipt of goods of production order at actual date is performed an exception occurs while material is automatically reported. The exception occurs because demand coverage date is later than date tolerance limit compared to demand date (which is actual date).
Correction result: In above-described context, receipt of goods of production order and subsequent automatic reporting will not be successful. Instead of an exception, an error message is output: PRD-2030 Production order line item XX could not be reported.
5.1.3.4 Reservations
RFR-016508 Correction
Framework: Storage Location Control
Application: Inventory requisitions
View: Manual stock movement
Action: Generate inventory orders…
Category: Unexpected behavior
Problem: If an inventory order should transport goods from a simple warehouse to the receiving zone (specified target) of a structured warehouse the inventory order could not be generated.
Correction result: Goods can be transported from a simple warehouse to the receiving zone (specified target) of a structured warehouse as expected.
RFR-016508 Correction
Class: com.cisag.app.inventory.reservation.log. FixedReservationLogic
Method: reserve(ReservationRequestCollection), report(ReservationRequestCollection), transfer(ReservationRequestCollection)
Description: New possibility to collect reservation requests and executes them as a bulk operation. Internal sorting will reduce the possibilities of dead lock situations within reservation processes.
RFR-016508 Correction
Framework: Inventory Management
Application (Batch): Update demand data
View: n.a.
Create and reserve serial number demand data
Category: Unexpected behavior
Problem: If a serial number was specified within an order (e.g. sales order) it would only be tried to reserve when the reservation strength had to be stock bounded (e.g. delivery orders).
Correction result: If a serial number is specified within an order (e.g. sales order) it is tried to be reserved as expected.
5.1.4 Multi-site capability
5.1.4.1 Distribution orders
RFR-016508 Correction
Framework: Inventory
Application: Delivery Orders
View: Distribution
Action: Cancel
Category: Unexpected behavior
Problem: The inventory transactions of a canceled delivery order were transferred into the transaction error log, because the onhand on the transfer warehoue is less than needed. That happend if the delivered quantity (or a part of it) was former manually completed at the target warehouse.
Correction result: From now the inventory transaction of a delivery order cancelation can be posted as expected, even if the delivered quantity (or a part of it) was completed manually at the target warehouse.
RFR-016508 Correction
Framework: Production
Application: Reorganize distribution orders
View: n.a.
Action: Reorganize
Category: Unexpected behavior
Problem: A cross-site production order process uses distribution orders to transport a product to a target site for refinement, to transport the refined product back to main site and to provide inter company billing.
If these distribution orders are reorganized, this process fails as distribution orders are related to production orders. On the other side production orders belonging to a cross-site production process cannot be reorganized as long as the related distribution orders are not reorganized.
Correction result: Distribution orders related to a cross-site production process can be reorganized. If this distribution orders are reorganized the production orders of this cross-site production process cannot be rescheduled with a change of quantity any more.
5.1.5 Planning
RFR-016508 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning actions
Category: Unexpected behavior
Problem: In case the planning is forced to schedule production resources over many years it will consume a lot of time.
Such planning results are mostly useless because planning is not intended to span many years.
Correction result: Now there is a time limit which will stop the scheduling of a resource in case a limit of 10 years before or after the planning base date is passed.
An error message will show up in the message log and the planning log.
Technical information:
System property: com.cisag.app.aps.SchedulingTimeHorizon
Possible values: Number of years as positive integer
Default: 10
RFR-016508 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: all planning actions
Category: Unexpected behavior
Problem: In case items were planned with reservations and with forecasts and a reservation was earlier in a forecast period than a forecast, this forecast was not reduced by the reserved quantity.
Correction result: Reserved quantities of a demand in a forecast period do reduce forecasts at the same day or later in the same forecast period.
5.1.6 Production
RFR-016508 Correction
Framework: Production
Application: Bills of resources
View: Bill of resources
Action: n.a.
Category: Exception
Problem: Open a Bill of resources having an associated routing that contains a cross-site operation position. Without closing the just opened BOR, open associated routing and delete one of the cross-site operations. After coming back to opened Bill of resources an exception occurred.
Same exception occurred after deleting bill of materials line item (It is bill of materials used as line item in another bill of materials).
Correction result: An exception does not occur anymore. Instead, an error message is displayed about the deleted line item. Deleting an operation or external operation from routing or material from bill of materials results in the same behavior.
RFR-016508 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: All planning actions
Field: Forecasts in time fence
Category: New field
Description: New field has been added to allow user to keep forecasts in time fence for items that has this time fence specified.
This makes that forecasts from time fence will be cumulated and if needed recommendation will be created for them at the first day after time fence ends.
RFR-016508 Correction
Framework: Production
Application: Order maintenance, Cockpit: Production orders
View: n.a.
Action: Reschedule
Category: Unexpected behavior
Problem: If errors occurred while rescheduling production orders message PRD 1995 shows wrong number of successfully rescheduled production orders
Correction result: If errors occurred while rescheduling production orders message PRD 1995 shows correct number of successfully rescheduled production orders
RFR-016508 Extension
Framework: Production
Application: Reorganize production order scheduling import data
View: n.a.
Action: n.a.
Category: New application
Description: Reorganize application which deletes all ProductionOrderBookingImport data with all dependent references which has status successfully processed.
RFR-016508 Correction
Framework: Production
Application: Production order
View: n.a.
Action: Recalculate due date and quantity
Category: Unexpected behavior
Problem: When production order has cross-site operation as one of its line item, the subOrder is created after dispatching. Additionally, for both of those orders a distribution order is created. After finishing those distribution orders and deleting both of them, performing action “Recalculate due date and quantity” on main production order causes a second, new distribution order for return transport (for sub order) to be created.
Correction result: The second distribution order is no longer created, when an existing one is already deleted.
5.1.6.1 Production – General
RFR-016508 Correction
Framework: Production
Application: Cockpit: Production items
View: n.a.
Action: Open empty
Category: Unexpected behavior
Problem: If Cockpit: Production items is opened empty in selection field “Item” a value “OBH-S101” is defaulted. This value is also defaulted when changing to view “Extended”.
Correction result: If Cockpit: Production items is opened empty, selection field “Item” is empty. It stays empty when changing to view “Extended”.
5.1.6.2 Production cockpit
RFR-016508 Extension
Framework: Production
Application: Cockpit: Production orders
View: Cockpit: Production orders
Action: n.a.
Field/Column: Bill of resources, Bill of material, Routing
Category: New fields
Description: Production order header attributes Bill of material, Routing and Bill of resources can now be used as search parameters in Cockpit: Production orders.
5.1.6.3 Production orders
RFR-016508 Correction
Framework: Production
Application: Order maintenance
View: n.a.
Action: Recalculate due date and quantity
Category: Unexpected bahaviour
Problem: A production order at a target site in a cross-site process is rescheduled. If assigned distribution order for transporting back the refined product is missing an error is output. This error has wrong number (PRD 2756 instead of PRD 2757)
Correction result: In above-described context the correct error message PRD 2757 is output.
RFR-016508 Correction
Framework: Production
Application: Cockpit: Production orders
View: Selection fields –> “Level”
Action: New, Load
Category: Invalid data
Problem: Selection field “Level” has a value which is not “(All)”. Button “New” is clicked. Result: Selection field “Level” keeps original value instead of changing to “(All)”
A search filter “X1” is pinned to context menu with a specified value for field “Level” (not “(All)”). Another search filter “XAll” is pined to context menu with value “(All)” for field “Level”.
Filter “X1” is active and displayed. Now Filter “XAll” is activated. Result: Value of field “Level” does not switch to value “(All)” as is expected. Value is the same as before activation filter “XAll”.
Correction result: The value of field “Level” always changes to predefined values as expected after action “New” or switching from one filter to another.
RFR-016508 Correction
Framework: Production
Application: Order maintenance
View: Operation Detail
Action: Save
Category: Unexpected behavior
Problem: An operation is manually added to a production order. The default value of due date is changed.
Result: Assigned resource line items do not have changed due date but still default value of due date.
Correction result: In above descried action all resources assigned to newly added operation have same due date as new operation has.
5.1.7 Purchasing
5.1.7.1 Bonus agreements
RFR-016508 Correction
Framework: System Management
Application: Import data
View: n.a.
Import of purchase item bonus classification
Category: Unexpected behavior
Problem: The import of sales item bonus classification, purchase item bonus classification and supplier quotation classification 4 could not detect the organizational unit correctly.
Correction result: The import of sales item bonus classification, purchase item bonus classification and supplier quotation classification 4 will detect the organizational unit as expected.
5.1.7.2 Purchase orders
RFR-016508 Correction
Applications: Order applications with “Find and add line items” dialog.
Action: “Find and add line items”
Category: Exception
Problem: If the search was executed and at least one entry is selected and at least one selection field value was changed to an invalid value before accepting the result an exception occurs during the “Accept” (all or single) functionality.
Correction result: Now one or more error message will be send and the dialog stays open without executing the “Accept” functionality so that the exception does not occur any more.
5.1.8 Sales
5.1.8.1 Sales orders
RFR-016508 Correction
Framework: Sales
Application: Sales orders
Action: Generate purchase orders
Category: Unexpected behavior
Problem: In some cases, the unexpected error message “PUR-01859” (storage area needed) occur during the try to add some further line items by a sales order – e.g. so:
1. Create a sales order header with the purchasing reference value “Delivery to issues warehouse”.
2. Create a sales order line item also with the purchasing reference value “Delivery to issues warehouse”.
3. Create the purchase order ==> the header and line item “delivery recipient” belong to the warehouse.
4. Change the sales order line item purchasing reference value to “External third-party order”. Save will update also the purchase order line item.
5. Copy the sales order line item so that the new line item has also to purchasing reference value to “External third-party order”; ensure that the purchase order (without line number) is present for second sales order line item.
6. Create now again the purchase order. ==> Error message “PUR-01859”.
Correction result: Now the error message does not occur any more.
5.1.9 Storage Location Control
5.1.9.1 Inventory management server
RFR-016508 Correction
Framework: Inventory Management
Application: Inventory postings
View: Manual inventory postings
Action: Save
Category: Unexpected behavior
Problem: If the used posting key is without ‘quantity transaction’ the specified item identifier will not be validated.
Correction result: If an item identifier is specified it will be checked whether it is existing as expected.
RFR-016508 Correction
Framework: Inventory management
Application: Inventory management server
View: n.a.
Action: Restart Inventory Management server
Category: Exception
Problem: If a financial organization exists for which no financials function in customizing is available, the inventory management server is terminated with an exception.
Correction result: If a financial organization exists for which no financials function in customizing is available, the inventory management server can still start and sends an error message to the message log.
RFR-016508 Correction
Framework: System Management
Application: Customizing (Function: base)
View: n.a.
Action: Save after changing the currency combination
Category: Invalid data
Problem: A cache responsible for the currency combinations was not updated after data was changed in customizing.
Correction result: The cache responsible for the currency combinations is now updated when data in customizing is changed.
Data update: com.cisag.app.update.log.UPDBUG028844 Data update description: Updates the combination of the begin value in InventoryOnhandPeriodSummay BO.
5.1.9.2 Inventory requisitions
RFR-016508 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: n.a.
Action: n.a.
Category: Exception
Problem: Technical problems during the class replacement mechanism.
Correction result: The class com.cisag.app.inventory. location.requisition.log.RequisitionDetailValidation can be replaced now.
Technical information: The static initializing of Path information caused problems during the RequisitionDetailValidation class replacement mechanism. The static variables declaration is removed now.
RFR-016508 Correction
Framework: Storage Location Cocntrol
Application: Cockpit: Inventories
View: n.a.
Action: Generate inventory requisitions…
Category: Unexpected behavior
Problem: If the target of a transfer is a structured warehouse and the target storage zone or bin is specified these data would be ignored.
Correction result: If the target of a transfer is specified these data will be considered as expected.
RFR-016508 Correction
Framework: Storage Location Control
Application: Inventory requisitions
View: Manual stock movement
Release of serial number transfer between two warehouses (structured warehouse at the source)
Category: Invalid data
Problem: If several serial numbers assignments with storage bin specification were created only the first serial number would get open outgoing process data. (Seldom use case)
Correction result: Open outgoing process data will be created for every exactly specified transfer transports.
Data update: If necessary erroneous data can be corrected by using the existing application “Correct voucher data and reservations” which should be restricted for the concrete source side.
5.1.9.3 Storage locations
RFR-016508 Correction
Framework: Inventory Management
Application: Receitp of goods
View: n.a.
Search-Action: “Find and add storage locations…” within the dialog “Assign storage locations”
Category: Unexpected behavior
Problem: The performance of the search action is worth for a big amount of partners.
Correction result: The performance of the search action is increased for a big amount of partners.
5.2 Infrastructure
5.2.1 Consulting
RFR-016508 Correction
Framework: Base
Application: Import data
Filter: com. cisag.app.general.obj.Partner
Action: Import
Category: Unexpected behavior
Problem: The error message PGM-10 was displayed importing a human partner.
Correction result: From now importing a human partner will work as expected.
RFR-016508 Correction
Framework: Various
Application: Various
View: n.a.
Action: n.a.
Category: API extension
Description: The API class “com.cisag.app.general. extension.log.Extensions” for “Other fields” programming support was extended to facilitate long texts.
RFR-016508 Correction
Framework: base?
Application: Partner
View: Action: Other Fields -> new field
Category: Unexpected behavior
Problem: When creating a new field of type ‘Price’, input a numerical value without a UOM for default, then add in the restrictions some currencies. Upon hitting ‘Accept’, both a red corner is placed upon the UOM part of the field, as well as a valid currency is placed there, based on the restrictions. So just accepting again will let you proceed.
Correction result: the uom part of the field now gets filled before the validation, so no red corner gets placed
5.3 System development
RFR-016506 Correction
Framework: System Management
Tool: insrfr
View: n.a.
Action:Message for logged in Users
Category: Ergonomics
Problem: If an installation is planned for the system, then a message box should informs the already logged in users.
Correction result: Now this message box is shown.
RFR-016506 Extension
Update of the library of crystal report.
RFR-016507 Extension
Update of the library of crystal report.
5.3.1 Application server
5.3.1.1 Autorizations
RFR-016506 Correction
Process: update of authorization roles
Category: Invalid data
Problem: After any capability of an authorization role is changed on one application server, this exception can occur on other active application servers of the system: “Exception in shared cache object change listener, java.lang.IllegalArgumentException: Parameter guid must not be null”. The capability update is not accounted for in subsequent logins.
Correction result: Updated capability is available on other application servers.
5.3.2 Configuration
5.3.2.1 System cockpit
RFR-016506 Correction
Framework: System Management
Application: System cockpit
View: System
Action: “Open empty” in the navigator for the System cockpit
Category: Exception
Problem: If the system cockpit is open, and the tab “Sessions” is displayed for a system, and the user selects “Open empty”, the system cockpit may close with an exception message “java.lang. IllegalStateException: System guid missing in state.”.
Correction result: The System cockpit remains open without an exception.
Framework: System Management
Application: System cockpit
View: User Group
Action: “Update the table’s content based on the search criteria”
Category: Exception
Problem: If the user field for a member is empty because it is being edited, then selecting the action “Update the table’s content based on the search criteria” results in an exception message “java.lang.NullPointerException”.
Correction result: The problem is resolved.
5.3.3 Repository
RFR-016506 Correction
Framework: Software development
Action: Installing language refreshes
Category: Unexpected behavior
Problem: If you install an old language refresh, it can happen that effectively older text versions become active.
Correction result: The version of the imported text is now compared to the version of the existing text if present. The newer one will become active.
5.3.4 System – General
RFR-016506 Correction
Framework: n.a.
Application: All of report output application
View: n.a.”
Action: Save, Validate
Category: Exception
Problem: Exception will be thrown on validate or save action, if the user want to create a new report output and the report title field contains more than 50 characters.
Correction result: Error message will be sent if the report title field contains more than 50 characters.
5.3.5 Workflow
5.3.5.1 Process definitions
RFR-016506 Correction
Framework: Workflow
Application: Process Definitions
View: n.a.
Action: Refresh
Category: Exception
Problem: The Method TaskList. recordAction(int action, CisParameterList parms, String description, boolean persistent) handled only null String objects.
Which led to the error in the further processing in UserHistorySupport. recordAction(…) method.
Correction result: No exception.
Technical information: StringUtilitiy. isEmpty(String) function fixes this issue.