| Release | Comarch ERP Enterprise 6.3 |
| Release date | 19.01.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-016473 – RFR-016475
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-Fix12.”
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-Fix12
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix11 will be upgraded to CEE630PB-Fix12.
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.
UPDSUP114077
Deletes tax data for sales quotations and sales orders that no longer exist
When the “Sales quotation” and “Sales order” documents were deleted, the optional tax data was not deleted. This update application deletes all tax data without the corresponding voucher.
5 Contained changes and extensions
5.1 Application development
RFR-016475 Correction
Framework: Inventory
Application: Delivery orders, Goods receipts
View: n.a.
Action: Complete delivery order and create delivery slip
Category: Invalid data / Unexpected behavior
Problem: In special cases the parallel quantities of delivered detail lines were not mapped correctly into the automatically created goods receipt details. I. e. that happens if a detail line has more than one assigned identifier and packaging quantities with onhand support are active.
Correction result: From now the parallel quantities of delivered detail lines will be mapped correctly into the automatically created goods receipt details.
RFR-016475 Documentation
The help document “Einführung: Disposition” has been updated regarding delivery calandar.
RFR-016475 Ergonomics
Update of the Polish language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016475 Correction
Framework: Software development
Application: Support request
View: n.a.
Action: Upload file attachement
Category: Exception
Problem: If a file attachment exists and a second file attachment is to overwrite the first one during upload, an exception occurs.
Correction result: The exception do not occur.
RFR-016475 Documentation
The help document “Einführung: Geschäftsprozesse mit verbindlichen Verpackungsangaben” has been updated regarding item settings, receipts of goods and queries for inventoried packagings.
RFR-016475 Correction
The help document “Cockpit: Bestände: Artikel” (German language version) has been provided in the correct version.
RFR-016475 Correction
Framework: Sales, Purchasing
Application: Price inquiry
View: n.a.
Action: n.a.
Category: Performance
Problem: Index for price inquiry has had a bad sequence of attributes
Correction result: Sequence of index attributes has been changed according to expected data
5.1.1 Base
5.1.1.1 Contracts/RFQs/Quotations/Orders
RFR-016475 Correction
Class: com.cisag.app.general.order.ui. AbstractOrderHeaderUi
Method: constructor
Description: Before this correction the constructor contains the variable assignment “dataViewUI = dataViewUIContainer.getDataViewUI();” two times.
5.1.1.2 Fiscal years
RFR-016475 Correction
Framework: Accounting, Inventory
Applications: “Fiscal years”, “Inventory count”
Action: Own “Inventory count” layout
Category: Exception
Problem: If one of the fields “beginDate” and “endDate” of the “Fiscal year” data view is used outside of the maintaining application (e.g. within the “Inventory count” application) for an own layout an exception occurs during the try to access the entity that belongs to the maintaining application – this entity will be used to determine if the field is editable or read only.
Correction result: If the entity is not present the field is now always not editable. So, the exception does not occur any more.
Technical information: In addition to the correction, the relevant EditorFactory classes implement now also the interface TableEditorFactory – so both fields can be used now also within customizable tables that are based on the “fiscal year” data view.
5.1.1.3 Item characteristics
RFR-016475 Documentation
The help document “Varianten eines Referenz-Artikels suchen und hinzufügen” has been created.
The following help documents (German versions) have been updated regarding new action “Varianten eines Referenz-Artikels suchen und hinzufügen”:
– Beschaffungskontrakte: Aktionen
– Vorgehensweisen: Beschaffungskontrakte
– Beschaffungsanfragen: Aktionen
– Vorgehensweisen: Beschaffungsanfragen
– Beschaffungsangebote: Aktionen
– Vorgehensweisen: Beschaffungsangebote (Fehler: Text für Hyperlink “Beschaffungsaufträge: Aktionen” ist falsch)
– Beschaffungsaufträge: Aktionen
– Vorgehensweisen: Beschaffungsaufträge
– Vertriebskontrakte: Aktionen
– Vorgehensweisen: Vertriebskontrakte
– Vertriebsschnellerfassungsbelege (neu in 6.3)
– Vorgehensweisen: Vertriebsschnellerfassungsbelege
– Vertriebsanfragen: Aktionen
– Vorgehensweisen: Vertriebsanfragen
– Vertriebsangebote: Aktionen
– Vorgehensweisen: Vertriebsangebote
– Vertriebsaufträge: Aktionen
– Vorgehensweisen: Vertriebsaufträge
– Verteilanfragen
– Vorgehensweisen: Verteilanfragen
– Verteilaufträge: Aktionen
– Vorgehensweisen: Verteilaufträge
– Verteilanfragearten importieren (change of help document folder, no change of help document)
RFR-016475 Documentation
The help document “Vorgehensweisen: Beschaffungsangebote” has been corrected regarding hyperlink “Beschaffungsaufträge: Aktionen”
The help document “Vertriebsaufträge: Aktionen” has been corrected regarding wrong internal link.
5.1.1.4 Items
RFR-016475 Correction
Framework: Base
Application: Items
View: Planning data
Action: n.a.
Category: Unexpected behavior
Problem: The category ‘External purchasing data’ of the view ‘Planning data’ was deactivated in the design mode because it contained a label as a placeholder without an id.
Correction result: From now the view ‘Planning data’ will work as expected. The label is removed from the set of visual elements of that view.
RFR-016475 Extension
Class: com.cisag.app.general.item.log. ItemsImpl
Methods:
– retrieveSupplierPurchaseItems(byte[][], byte[][], byte[][]),
– retrieveCustomerSalesItems(byte[][], byte[][], byte[][]),
– retrieveCustomerClassificationItems(byte[][], byte[][], byte[][]),
– retrieveCustomerPlanningDatas(byte[][], byte[][], byte[][])
Description: From now the performance of these methods will be improved.
5.1.1.5 Partners
RFR-016475 Correction
Business object: com.cisag.app.general.obj. OrganizationalUnitPartner
Description: A new non unique index with the attributes guid + organizationalUnit + validFrom + validUntil + visibility was created.
5.1.2 Inventory management
5.1.2.1 Delivery orders
RFR-016475 Correction
Framework: Inventory
Application: Reorganize picking orders, reorganize delivery orders
View: n.a
Action: Reorganize
Category: Invalid data
Problem: The reorganization applications did not delete instances of the BO com.cisag.app. inventory.obj.ReportedQuantities.
Correction result: From now the reorganization applications will delete the associated instances of the BO com.cisag.app.inventory.obj.ReportedQuantities when a picking order or deliver order is deleted.
Technical information: Data update: use OQL
“delete from com.cisag.app.inventory.obj.ReportedQuantities rq
where not exists (select po:guid from com. cisag.app.sales.obj.PickingOrder po where po:guid = rq:header)
and not exists (select so:guid from com.cisag.app.sales.obj.ShippingOrder so where so:guid = rq:header)”
to get rid of not used ReportedQuantities instances.
5.1.2.2 Identifiers
RFR-016475 Correction
Framework: Inventory Management
Application: Receipt of goods
View: Purchasing
Assignment of a supplier item identifier
Category: Unexpected behavior
Problem: If a supplier item identifier was assigned in a receipt of goods the supplier item identifier would not be assigned to the item identifier.
Correction result: If a supplier item identifier is assigned in a receipt of goods the supplier item identifier will be assigned to the item identifier as expected.
5.1.2.3 Inventory count
RFR-016475 Correction
Framework: Inventory Management
Application: Inventory count list
View: n.a.
Switch between loading unit correction application and inventory count lists application
Category: Ergonomics
Problem: If a new line item was added in the loading unit correction application the new corresponding count list line item would not be displayed after the switch to the inventory count list application.
Correction result: After the update of the count list line items it will be reloaded at the application switch as expected.
5.1.2.4 Inventory management – General
RFR-016475 Documentation
Following help documents (German language versions) have been updated regarding the explantion of the “Binding unit” field: – Items, “Sales” View
– Items, “Purchasing” View
– Items, “Suppliers” View
– Items, “Customer Classification” and “Customers” Views
– Supplier Contracts
– Purchasing RFQs
– Supplier Quotations
– Purchase Orders
– Customer Contracts
– Sales RFQs
– Sales Quotations
– Sales Orders
– Distribution Orders
5.1.2.5 Inventory postings
RFR-016475 Correction
Framework: Inventory
Application: Inventory postings
Action: Post manually
Category: Invalid data / Unexpected behavior
Problem: Up from 6.3 a manual transfer inventory transaction can optionally use a specified price for the incoming transaction in the case that the owners are different financial organizations. By mistake this functionality does not work as expected.
Correction result: Changed behavior for manual transfer inventory transaction: – As before the outgoing transfer transaction valuates the price.
– If a price is specified (any domestic amount value is not zero) and the owners are different financial organizations the incoming transfer transaction will use now the specified price.
Otherwise – as before – the valuated outgoing transfer transaction value will be used also for the incoming transfer transaction.
RFR-016475 Correction
Framework: Inventory management
Application: Inventory postings
View: Inventory posting or import of inventory postings
Action: Post an inventory posting with a serial number with inventory management specification or post an inventory posting with a unit load with a serial number with inventory management specification.
Category: Unexpected behavior
Problem: The serial number specification in the inventory posting resulted in stocks being built up for this serial number.
Correction result: The serial number specification in the inventory posting is now ignored.
5.1.2.6 Receipts of goods
RFR-016475 Correction
Framework: Inventory
Application: Goods receipts
View: n.a.
Action: Post goods receipt …
Category: Unexpected behavior
Problem: Posting a goods receipt the error message ‘PUR-01059’ was displayed if a packed detail line has more than one order assignment line assigned to it.
Correction result: From now the error message ‘PUR-01059’ will be displayed only when it is expected.
5.1.2.7 Reservations
RFR-016475 Correction
Framework: Sales
Application: Sales orders
View: n.a.
Action: Create production orders…
Category: Unexpected behavior
Problem: There was a rounding error within the additional item reservation quantities units when two orders were bound with different main units.
Correction result: If two orders with different units were bound the reservation quantities will be rounded as expected.
5.1.3 Multi-site capability
5.1.3.1 Distribution orders
RFR-016475 Correction
Framework: Sales
Application: Distribution orders
Action: Generate inventory allocation
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the release 6.1, the “Immediately” execution of the “Generate inventory allocation” action does not display the table view with the field “Allocated qty f. delivery order/picking order”.
Correction result: Now the behavior is again as in the release 6.1.
Technical information: In addition to that the “Sales orders” coding has been changed in analogy to the “Distribution orders” so that also here the focus will be set to the relevant field if any message requires attention.
5.1.4 Planning
RFR-016475 Correction
Framework: Production
Application: Material Requirements Planning
View: n.a.
Action: Restart Planning Server / Shut down Planning Server
Category: Unexpected behavior
Problem: When shutting down an MRP server while it is currently working (e.g. transferring item data for planning), the server is not shut down correctly and cannot be started again.
The server continues to occupy main memory and CPU and does not delete its temporary data from DB until SAS restart.
Correction result: The MRP server is shut down correctly and can be started again.
5.1.4.1 Material requirements planning
RFR-016475 Correction
Framework: Planning
Application: Material requirements query
View: n.a.
Action: n.a.
Category: Exception
Problem: If there is incomplete data for the selection of item/site, an exception may occur.
Correction result: If there is incomplete data for the selection of item/site, error message PRD-2632 appears.
5.1.4.2 Planning – General
5.1.5 Production
RFR-016475 Correction
Framework: Production
Application: Cockpit: Betriebsmittelanforderungen
View: n.a.
Action: Betriebsmittel zuweisen
Category: Unexpected behavior
Problem: When equipment instances are assigned to an equipment requirement linked to a production order detail of type equipment, the source storage area of the production order detail should be used primarily as source warehouse.
Instead the production order target warehouse was used to find available equipment instances.
Correction result: In case it is defined, the warehouse specified by the production order detail is now used to find available equipment instances.
Technical information: ProductionOrderDetail:storageArea.
RFR-016475 Correction
Framework: Production
Application: Bills of material
View: Line item filter
Action: Select item
Category: Unexpected behaviour
Problem: The entry of several unequal links leads to wrong results.
Correction result: The entry of several unequal links leads to correct results.
RFR-016475 Correction
Framework: Production
Application: Time models
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: In SUP-112858 a simplification was introduced to normalize all times to be located at the same day, except for midnight time ranges shifts, for which the end time was located at the following day.
Correction result: Time ranges that are located in the table after a midnight spanning time range will now remain at their position and remain located at the following day. The buttons to move table rows up and down are available again.
5.1.5.1 Bills of material
RFR-016475 Correction
Framework: Production
Application: Import data
View: n.a.
Action: Import data
Category: Unexpected behavior
Problem: When trying to import Bill of material, when the field ‘organizationalUnit’ did not have the correct format (guid) but another(e.g. the code of an organization), an exception has been sent as message, which could be found in logs of incorrect import.
Correction result: The message is now sent instead of exception when field ‘organizationalUnit’ is in wrong format.
5.1.5.2 Operations
RFR-016475 Correction
Framework: Production
Application: Operations
Action: Create/Update Multi-site production operation
Category: Unexpected behavior
Problem: When editing “Pseudo item for outbound transporting” field the “Use in order” check was ignored. Item without “Use in order” could be added without warning.
Correction result: Validation now checks “Use in order” and if it is not checked in pseudo item an error message is created.
5.1.5.3 Production orders
RFR-016475 Correction
Framework: Production
Application: Order maintenance, Cockpit: Production orders
View: n.a.
Action: Generate picking orders and output picking slips…
Category: Unexpected behavior
Problem: A picking order which has been generated by action “Generate picking orders and output picking slips” will not be completed but canceled instead.
Result: Picking status of corresponding production order details remains status “Picking in process”. Also new “Open picking quantity” of this production order details after cancellation is wrong
Correction result: In above described context, cancellation of a picking order without completion works as expected. New picking status of production order details is “No picking in progress”. New open picking quantity has been increased by canceled quantity.
Please note: Problem occurred recently in application.
RFR-016475 Correction
Framework: Production
Application: Order maintenance
View: n. .a.
Action: Recalculate due date and quantity
Category: Unexpected behavior
Problem: Context: Process structure of a product contains an external operation. This operation has a provided material which is a semi-finished product. In the course of dispatching multiple levels, the semi-finished product will be dissolved and a sub order will be generated.
The current end date of the generated sub order must match the current begin date of the corresponding external operation. This is the case after dispatching.
If now the (main) production order is rescheduled with another due date the sub order not anymore ends at current begin of external operation. Sub order ends at current begin of the operation following the external operation.
Correction result: In above described context sub orders current date end matches current begin date of corresponding external operation after rescheduling.
RFR-016475 Correction
Frameworks: Production, Sales
Applications: Productions orders, Sales orders
Action: Change sales order line item
Category: Exception / Unexpected behavior
Problem: If a sales order line item references a production order and the current user is not authorized to load a production order an exception occurs. In addition to that the production order cannot be changed in this case by the sales order.
Correction result: The general order base class “com.cisag.app.general.order.log.AbstractEntity” was corrected so that now a change is possible if an entity instance is not in the “normal mode” that is used by the normal maintenance (here the case because the “production order entity” is used in a special “dependent mode” by the “sales order”).
5.1.6 Purchasing
5.1.6.1 Purchase order confirmations
RFR-016475 Correction
Framework: Purchasing
Application: Supplier confirmations
Action: Add line item
Category: Unexpected behavior
Problem: The “Add line item” action send an error message “number already used” also in some cases where the number is allowed to be used (already a member of a previous confirmation).
Correction result: Now in this case the error message does not occur any more.
5.1.6.2 Supplier invoices
RFR-016475 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Book invoice
Category: Invalid data / Unexpected behavior
Problem: If an internal invoice is based on internal billing data that belongs to a sales order with the type “Return replacement order” unexpected bookings will be performed – the behavior should be the same as for the type “Customer order”.
Correction result: The special bookings will be performed now only for sales orders with the types “Consignment order” and “Branch order” and not for the types “Return credit note”, Return replacement order” and “Customer order”.
RFR-016475 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Refresh “Supplier invoices” by “com.cisag.app.tools.DomesticAmountConverter”.
Category: Exception / Invalid data / Unexpected behavior
Problem: In contrast to the method “com.cisag.app.purchasing.invoice.log.InvoiceBookingUtility.sumDetailNetAmountDomestic(InvoiceEntity entity)” the method “InvoiceBookingUtility.sumDetailNetAmountDomestic(SupplierInvoice)” does not work as expected: – if the supplier invoice has no line item an exception occurs
– if the supplier invoice has more than one line item only the first line item will be considered
Correction result: Now the method works as expected.
5.1.7 Relationship Management
5.1.7.1 Customizable cockpits
RFR-016475 Correction
Framework: Purchasing
Application: Cockpit: Supplier puchase items
View: n.a
Action: Load supplier purchase item in application ‘Items’
Category: Ergonomics
Problem: In former releases that action works with a double click on a line item. The functionality was deactivated unintentionally.
Correction result: From now the action “Load supplier purchase item in application ‘Items’ ” will work with a double click on a line item again.
5.1.8 Sales
5.1.8.1 Customer invoices
RFR-016475 Correction
Framework: Sales
Application: Customer invoices
Action: Generate invoice
Category: Exception
Problem: Because of a correction within “CEE630PB-Fix09 KW35/2023” the invoice generation throws sometimes an exception if a customer invoice is based on a sales order but the invoice line item is not based on a sales order line item.
Correction result: Now the exception does not occur any more.
5.1.8.2 Customer returns
RFR-016475 Correction
Framework: Sales
Applications: Customer returns, Sales orders
Action: Create “Return create order” and “Return replacement order”
Category: Unexpected behavior
Problem: If the sales order line item attribute “No cash discount” is not activated within the original order line item a cash discount might be present and used. But for a “Return create order” or “Return replacement order” the value of this attribute was set always to true as default value – so without a manual change the credit note value to be paid back to the customer is sometimes higher than the value that was paid by the customer for the original invoice.
Correction result: To avoid this the generator for “Return create orders” and “Return replacement orders” uses now the original order line value of the “No cash discount” attribute. Only if no original order line item is present the value true will be used as before.
5.1.8.3 Sales – General
RFR-016475 Correction
Framework: Sales
Applications: Customer proposals, Sales orders
Action: Delete
Category: Invalid data / Unexpected behavior
Problem: If a customer proposal or a sales order uses the optional tax data – this data will not be deleted by the proposal/order delete action.
Correction result: Now also the tax data will be deleted as expected.
Data update: Please execute the data update application UPDSUP114077 to correct the existing data.
RFR-016475 Correction
Framework: Inventory
1. Application: Delivery slip types
View: n.a.
Action: n.a.
Category: Ergonomics
Problem: The field “Export delivery slip data for customs clearance” is activated for delivery slip types of subtype “External delivery” although this process is not supported for these delivery slips at all.
Correction result: From now the field “Export delivery slip data for customs clearance” is deactivated for delivery slip types of subtype “External delivery”.
2. Application: Cockpit: Delivery orders
Action: “Export delivery slip data for customs clearance”
Problem: An exception occurred if a delivery slip of subtype “External delivery” is selected to export.
Correction result: From now delivery slips of subtype “External delivery” will be skipped as expected.
5.1.9 Storage Location Control
5.1.9.1 Inventory orders
RFR-016475 Correction
Framework: Storage locations
Application: Inventory orders
View: n.a.
Action: Validate
Category: Ergonomics
Problem: If the transport quantity was an inventory packaging and it was tried to report an item unit only a general quantity message would be displayed.
Correction result: If an item unit is tried to be reported although it should be an inventory packaging a better matching message will be displayed.
5.1.9.2 Inventory requisitions
RFR-016475 Extension
Class: com.cisag.app.inventory.location.requisition.log. CreateDefaultRequisitionGenerator
Method: Params.createNotEmptyRequisition(boolean createNotEmptyRequisition)
Description: Indicates whether an empty requisition (no line items) must not be created (Default is FALSE, empty is allowed).
5.1.9.3 Storage locations
RFR-016475 Correction
Framework: Storage Location Control
Application: Storage locations
View: n.a.
Import of a picking location definition
Category: Exception
Problem: If a new picking location definition was imported an exception was thrown.
Correction result: A new picking location definition can be imported as expected.
5.2 System development
RFR-016474 Ergonomics
Update of the Polish language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016474 Ergonomics
Files of the online help file system have been updated.
RFR-016474 Documentation
The following help documents have been created (German versions):
– “Cockpit: Aktivitätsdefinitionen”
– “Cockpit: Aktivitätsdefinitions-Vorlagen”
– “Cockpit: Programmierte Ereignisse”
– “Cockpit: Prozessdefinitionen”
– “Cockpit: Prozessdefintions-Vorlagen”
RFR-016473 Correction
Framework: Software development
Application: Job Maintenance
View: n.a.
Action: Activating task, successor system
Category: Ergonomics
Problem: If you have defined a successor system for your development system, then on activating a task the contained objects will be locked in a task associated with a follow up development request.
If now there had been some translation for an the newer release and on the lower release the text had been changed, then the text will simply be overwritten in the newer release.
The editorial team don’t want that.
Correction result: Now a text conflict is created if the texts do not match. Analogous to the editorial tasks.
RFR-016473 Correction
Framework: Software Development
Application: Development tasks
View: n.a.
Action: Save
Category: Error message
Problem: Error message if the user does not have permission for B.E. com.cisag.sys.configuration.obj.Licence.
As a result, the .project file for common-project was not correctly created.
Correction result: Now it is possible to create a new development task without such an error message.
RFR-016473 Correction
Framework: Software Development
Application: Development objects resp. Simplified data import
View: External object
Action: resolving foreign key based on a secondary key
Category: Unexpected behavior
Problem: Within application “Simplified data import” is possible to resolve a foreign key supposed it is defined within the used external object.
If the resolving key is a secondary key, i.e. a unique key but neither the primary key nor the business key, the resolve mechanism did not work.
Correction result: Resolving a key via use of a secondary key now works properly.
RFR-016473 Correction
Framework: n.a.
Application: n.a.
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The isBatchActionHookApplication(String) method in the class BatchActionHookApplication.Utility does not work correct properly.
Correction result: It now works properly.
RFR-016473 Extension
Framework: System Management
Tool: rgzrep
View: n.a.
Action: deleting test object and deleting internal use objects.
Category: Exception
Problem: The options for deleting test objects and for deleting internal objects did not work.
Correction result: The options now work properly.
RFR-016473 Correction
Framework: System Management
Tool: insrfr
View: n.a.
Action: Login to system while an installation is planned
Category: Ergonomics
Problem: If an installation is planned for the system, then a message box should inform the user.
Correction result: Now this message box is shown.
RFR-016473 Correction
Framework: System management
Tool: upgaps
View: n.a.
Action: undo
Category: Exception
Problem: If an ‘undo’ is necessary for an installation and a development object of type Terminus is concerned, then an exception occurs.
Correction result: ‘Undo’ now works properly even if a terminus object is concerned.
5.2.1 Application server
5.2.1.1 JobControl
RFR-016473 Correction
Process: Closing an application
Category: Exception
Problem: If a new application A is opened exceeding the maximum of open dialog sessions, another open application B in display mode is automatically closed. Upon closing A, B is opened again. If B fails to start due to a runtime exception, there is a chance of an endless loop resulting in a stack overflow.
Correction result: Debug message and exception instead of stack overflow.
Technical information: Please submit request including logfile if this occurs.
5.2.2 Configuration
RFR-016473 Correction
Framework: System Management
Application: System cockpit
View: License
Action: Generate system with components
Category: Unexpected behavior
Problem: Using action “Generate system with components” may fail with an error message regarding a database access path which contained the database name, as well as a question mark section. Such an access path may be legal.
Correction result: The problem is resolved.
Framework: System Management
Application: System cockpit
View: License
Action: Generate system with components
Category: Unexpected behavior
Problem: A system created by using action “Generate system with components” may not have the same user channel assignments as in the source system.
Correction result: The problem is resolved. The user channel assignments are the same as in the source system.
5.2.3 Kernel
5.2.3.1 Locking / Caching
RFR-016473 Correction
Class: com.cisag.pgm.datatype.ObjectUtility
Method: waitSafe(T obj, long timeout, Predicate success)
Description: Implementation of Object.wait (long timeout) that is guarded against spurious wakeups.
Process: Locking
Category: Unexpected behavior
Problem: “Spurious wakeups” might cause unexpected results when using Object. wait(timeout).
Correction result: Concerned locking methods have been reworked to be safe.
5.2.4 Searches
5.2.4.1 Searches
RFR-016473 Correction
Framework: All
Application: all adaptable cockpits
View: n.a.
Action: searching
Category: Exception
Problem: If cockpit searches use a SearchResultFilter and this search was used in a background processing without having previously selected “search” in the cockpit, an exception occurred.
If a new detailed search was entered and added in a cockpit, an exception could occur during the search.
Correction result: The exceptions do not occur.
5.2.5 System – General
RFR-016473 Correction
Framework: n.a.
Application: n.a.
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: The getDataViewClassName() method in the class BatchActionHookApplication does not work correct properly.
Correction result: It now works properly.