| Release | Comarch ERP Enterprise 6.3 |
| Release date | 03.11.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-016460 – RFR-016462
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-Fix10.”
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-Fix10
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix09 will be upgraded to CEE630PB-Fix10.
3.1 Installing support deliveries
The following sections describe the special features for installing the support deliveries of this delivery.
If the source system has a state that is between CIS620PA and CIS620PB-Fix11, you can use the manual update procedures described below to upgrade a Comarch ERP Enterprise based system to CEE630PB.
Further information is provided in INF-000155.
To install the support deliveries, please use the documentations “Introduction: Software Logistics” and “Using Tools and Troubleshooting Help.”
3.2 Cumulative installation of support deliveries
Code status CIS620PA is required for the release upgrade. It is not possible to install Comarch ERP Enterprise 6.2 and Comarch ERP Enterprise 6.3 at the same time. Support deliveries for Comarch ERP Enterprise 6.3 can be installed cumulatively. Further information about the cumulative installation are provided in INF-000228.
3.3 Parallel or sequential installation
If you use the tool insrfr to install the support deliveries, you must choose the sequential (installType:3) installation type. Alternatively, you can first install the system code support deliveries manually and install the application code support deliveries afterwards.
3.4 Problems during the installation
If a problem arises during the installtion of support deliveries, you can refer to INF-000155 “Behebung von Installations-Problemen von Supportauslieferungen” which contains information about possible causes and about instructions on how to solve the problem.
4.1 Data updates
No data updates have to be carried out.
4.2 Batch data updates
No batch data updates have to be carried out.
5 Contained changes and extensions
5.1 Application development
RFR-016462 Correction
Framework: Production
Application: Bills of material
View: Line item filter
Action: Select item
Category: Exception
Problem: If only special characters are entered in the item field, e.g. “+”, the PatternSyntaxException “Dangling meta character ‘+’ near index 0” occurs.
Correction result: If only special characters are entered in the item field, e.g. “+”, no exception occurs.
RFR-016462 Ergonomics
Update of the PL language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016462 Documentation
Text corrections (German only).
RFR-016462 Ergonomics
Update of the FR language user interface.
The installation does not affect the texts. You obtain the translations in support deliveries from the support center.
RFR-016462 Correction
Framework: Base
Application: Customizable cockpit that call batch application
View: n.a.
Action: Batch action
Category: Unexpected behavior
Problem: Customizable cockpit does not pass the correct objects to batch application for time-dependent objects.
Correction result: The problem is fixed.
RFR-016462 Documentation
The help document folder “Lagercockpit” has been deleted.
RFR-016462 Correction
Class: com.cisag.app.general.partner.ui. PartnerBaseSubapplication
Method: n.a.
Description: Global private final static variable LEVY_COLLECTION_LEVEL_CLASSIFICATION_PATH is removed from code.
RFR-016462 Correction
Class: com.cisag.app.general.ui.TextAssignmentEditor.EditDialog
Method: Constructor, show(CisListPartMutable row)
Description: From now an error in handling the focus when reopening the text editor will be corrected.
RFR-016462 Documentation
The following help documents (German language versions) have been updated regarding the criteria for price determination:
– Einführung: Vertriebspreise (Introduction: Sales Prices)
– Vertriebspreisermittlung (Sales Price Determination)
– Einführung: Beschaffungspreise (Introduction: Purchase Prices)
– Beschaffungspreisermittlung (Purchase Price Determination)
5.1.1 Base
5.1.1.1 Base – General
RFR-016462 Correction
Classes: com.cisag.app.general.ui. SingleObjectMaintenance/SingleObjectTableMaintenance
Category: Exception
Problem:
If the annotation UseSingleObjectViewAttributes is used by a concrete class an exception occurs in some cases for the last key attribute within the step “buildByBusinessKey” if the business key contains multiple attributes.
Correction result:
1. Now the used field will catch an exception of the method super class call (“SimpleEntityField#buildByBusinessKey”) – if this occurs the field returns “null” as result within the step “buildByBusinessKey” so the SimpleEntityField will read in this case an empty object and the exception does not occur any more.
2. Now the concrete application can implement the new interface “com.cisag.app.general.ui.UseSingleObjectViewAttributes.MultipleBusinessKeyBuilder” and the implementation can be registered as “AttributeContext” value for the last key attribute. If specified this implementation will be used instead of the default behavior – so a concrete class can provide an implementation that considers the data of all key attributes.
Hints: Because the AttributeContext is available also within the MultipleBusinessKeyBuilder implementation you can access the values of the other key attributes by the DataView instance of the AttributeContext. To ensure here that the current values are present, it makes sense to enable the “immediate updates” functionality for the other business key attributes.
RFR-016462 Correction
Framework: System Management
Application: Reorganize change journal
View: n.a.
Action: Execution
Category: Exception
Problem: Reorganizing the change journal may abort with an exception message “java.lang.ClassCastException: class com.cisag.app. general.obj.DomesticAmountMutable cannot be cast to class com.cisag.app.general.obj.DomesticAmount”. This issue can occur only if an export of reorganized objects is activated both in batch application “Reorganize change journal”, and in application “Activate change journal”.
Correction result: The problem is resolved.
5.1.1.2 Classifications
RFR-016462 Correction
Framework: Base
Application: Classifications
Action: Import with additional “HierarchyExtensionHook” data
Category: Invalid data / Unexpected behavior
Problem: Within the import correction mode the classification application does not consider data that was added by a “HierarchyExtensionHook” implementation.
Correction result: Now such data will also be considered as expected.
5.1.1.3 Customizing
RFR-016462 Correction
Framework: Base
Application: Partners
View: Employee
Action: Load
Category: Exception
Problem: An exception occurred loading an employee if the organization responsible is not already assigned to a firm.
Correction result: From now loading an employee if the organization responsible is not already assigned to a firm will work as expected.
5.1.1.4 Item characteristics
RFR-016462 Documentation
The following help documents have been updated created:
– Cockpit: Artikelmerkmale
– Cockpit: Artikelmerkmal-Klassifikationen
– Cockpit: Artikel-Artikelmerkmal-Zuordnungen
RFR-016462 Documentation
The following help documents have been created or updated according to new handling of item properties:
– Artikelmerkmalgruppen
– Vorgehensweisen: Artikelmerkmalgruppen
– Artikelmerkmale
– Vorgehensweisen: Artikelmerkmale
– Artikelmerkmal-Klassifikationen
– Vorgehensweisen: Artikelmerkmal-Klassifikationen
– Artikel-Artikelmerkmal-Zuordnungen
– Vorgehensweisen: Artikel-Artikelmerkmal-Zuordnungen
RFR-016462 Correction
Framework: Base
Application: Item characteristics
Action: Create user interface
Category: Unexpected behavior / Ergonomics
Problems:
1. In contrast to the table columns, the editor does not consider the “Display language” of the current user for the field labels.
2. The problem exists also for the search area of the additional item search “Item characteristics”.
Correction result: Now also the editor field labels are as expected. The same for the additional item search “Item characteristics”.
RFR-016462 Documentation
The following help documents have been updated regarding modified handling of item properties:
– Export- und Import-Schnittstellen
– Artikelmerkmale importieren
– Artikelmerkmal-Klassifikationen importieren
– Artikel-Artikelmerkmal-Zuordnungen importieren
– Benutzerdefinierte Felder importieren
5.1.1.5 Items
RFR-016462 Correction
Framework: Base
Application: Items
View: Base
Action: Validate / Update
Category: Exception
Problem: An exception occurred validating a new packaging unit of measure line.
Correction result: From now validating new packaging unit of measure lines will work as expected.
RFR-016462 Correction
Framework: Base
Application: Items
View: n.a.
Action: n.a.
Category: Unexpected behavior / Ergonomics
Problem: The views of an item, that have already been created, are displayed on the right of the article picture in the ident view. If you move the mouse over this area, the mouse pointer will also change in the “empty” area and a non-existing view can be clicked. If you click on it by mistake, the view, e.g. Sales, will be created and CEE expects the maintenance of the mandatory fields.
Correction result: From now there will not be a clickable action in the “empty” area. It will not be possible to create a view by mistake via clicking the “empty” area between the displayed icons any more.
RFR-016462 Correction
Framework: Base
Application: Items
View: Finance
Action: Create new version
Category: Unexpected behavior
Problem: The application went into “update”-mode after creating a new version of financials data and removing the output tax classification in the new version.
Correction result: From now the application will work as expected after saving the changed data.
RFR-016462 Correction
Framework: Base
Application: Import Data
Filter: com.cisag.app.general.obj.Item
Action: Import
Category: Exception
Problem: The import of variant items caused a java.lang.RuntimeException: “primary key cannot be changed” if the XML-File contains the association “ItemPropertyCollection” setting a NULL value.
Correction result: From now the import of variant items will work as expected.
Technical information: The association “ItemPropertyCollection” had to be removed from the filter because a NULL value in the XML-File for this association set the primary key of the imported item to NULL. The association was removed instead of marking it as “dependent” because item properties could not be updated in the application “Items”. The application “Item-characteristics assignments” (or a filter based on com.cisag.app.general.obj. ItemPropertyCollection) must be used for it.
RFR-016462 Correction
Framework: Base
Application: Import data
Filter: com.cisag.app.general.obj.Item
Action: Import
Category: Exception
Problem: An exception occurred importing item data, if the flag ‘Subject to base price regulation’ is activated for the item and attributes of the association ‘ItemBasicPriceData’ are activated in the import filter and the imported XML-File doesn’t contain data of that association.
Correction result: From now importing item data will work as expected no matter if the imported XML-File contains data of the association ‘ItemBasicPriceData’ or not.
5.1.1.6 Partners
RFR-016462 Correction
Framework: Base
Application: Partners
View: n.a.
Action: Validate, update, …
Category: Exception
Problem: The application throws an exception after running the reorganization application for partners and a partner marked as deleted is loaded before running the reorganization application.
Correction result: From now the partners application will work as expected.
5.1.2 Document Management
RFR-016462 Correction
Framework: Document management
Application: Documents
View: n.a.
Action: Create document via drag & drop
Category: Unexpected behavior
Problem: It was impossible to create a document via drag & drop component if the dropped file contained special characters like space.
Correction result: It is now possible to create a document via drag & drop component when the dropped file contains special characters.
RFR-016462 Correction
Framework: Document Management
Application: Documents
View: n.a.
Action: n.a.
Category: Unexpected behavior
Problem: If the business object Document has a supplement not initialized for each instance, error APP-00004 appears during the process of saving the document, when the object is updated many times.
Correction result: Error APP-00004 no longer appears if the problem conditions are met.
5.1.3 Inventory management
RFR-016462 Correction
The help documents “Introduction: Inventory Management” and “Inventory Management Server” (German language versions) have been updated: the background application com.cisag.sys.kernel.at.log.AtServiceBatch must run so that the inventory management server can update the inventory information for new item versions.
5.1.3.1 Identifiers
RFR-016462 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Save of a found not existing but expired batch.
Category: Unexpected behavior
Problem: If an unexpected and not existing batch was found and it was already expired an error message will be send because of the automatically calculated hold date.
Correction result: An unexpected and not existing expired batch can be reported as expected.
5.1.3.2 Inventory count
RFR-016462 Correction
The help document “Inventuren” has been updated regarding error described in REQ-074349 (“Einstellung Bestandsmenge”).
The help documents “Berichte” and “Inventurzählliste ausgeben” have been set to “Nicht sichtbar”.
RFR-016462 Correction
Framework: Inventory Management
Application: Inventory count lists
View: n.a.
Action: Save the report of a new line item
Category: Unexpected behavior
Problem: If the inventory count list was already opened and a new line item was created, the validation of the entered quantities would be erroneous.
Correction result: If the inventory count list is already opened the entered quantities of new line items will be validated as report quantities as expected.
5.1.3.3 Inventory management – General
RFR-016462 Extension
Framework: Inventory Management
Application: Inventory order types
View: n.a.
Action: Generate inventory order
Field/Column: serial number assignment, report open quantity
Category: New field
Description: Two additional settings for the application Inventory order types are added: Serial number assignment and report open quantity. These new settings will be also available for the following applications: Inventory
requisitions, receipts of goods, picking orders.
5.1.3.4 Inventory postings
RFR-016462 Correction
Class: com.cisag.app.inventory.reservation.log. FixedReservationAvailabilityMaintenanceLogic
Method: ReservationSupport. removeReservation(ZeroData)
Description: The attribute “identifier” of the BO AvailabilityDetail must be set to an identifier GUID or “null”. But in some constellation, it was set to ZEROGUID instead of null. This is now corrected. But to ensure the robustness for existing data the attribute interpretation considers both variants.
RFR-016462 Correction
Framework: Inventory Management
Application: Cockpit: Inventory postings
View: n.a.
Overtake of the inventory posting object as application parameter
Category: Unexpected behavior
Problem: The business entity “InventoryTransaction” was specified as application parameter but it was not used to preset the posting number.
Correction result: The application parameter “InventoryTransaction” and “Number” will now be used to preset the new standard search criterion “posting number”.
5.1.3.5 Inventory query
RFR-016462 Correction
Framework: Inventory Management
Application: Cockpit: Inventories/identifiers
View: n.a.
Action: Identifier type selection
Category: Unexpected behavior
Problem: Identifier type should be limited to lot, batch, serial number level.
Correction result: The problem is fixed.
5.1.3.6 Reservations
RFR-016462 Documentation
The help document “Kommissionen” (Picking Orders) has been updated regarding the descriptions of the action buttons in the “Rückmeldung” (Reporting) dialog box and of the action button “Gesamtmenge auf kommissionierte Menge reduzieren” of the line item list.
5.1.4 Production
RFR-016462 Correction
Framework: Production
Application: Cockpit: Betriebsmittel initialisieren
View: n.a.
Action: Betriebsmittel initialisieren
Category: Exception
Problem: In case an equipment item was incoming with serial number, but the inventory server has not finished the related background work yet,
the “Cockpit: Betriebsmittel initialisieren” did produce a NullPointerException in the action “Betriebsmittel initialisieren”.
Correction result: The equipment can be initialized now in the situation described above.
RFR-016462 Extension
Framework: Production
Application: Where-used list
View: (all)
Action: Refresh/Replace line detail items
Category: Exception
Problem: When loading or recursively showing an equipment position (or some production plan containing an equipment), the application crashes with an exception.
When replacing an equipment position in some Bill of Material with another equipment item, the application does not execute the replacement and does not show any error message.
Correction result: Equipment positions can be loaded and shown correctly.
Replacing equipment positions works correctly.
RFR-016462 Correction
Framework: Production
Application: Time models
View: n.a.
Action: Input begin time / end time
Category: Unexpected behavior
Problem: If a negative or invalid time is entered at the start, e.g. “-08:00” or “08:98”, the whole thread is stuck in an endless loop during validation.
If a negative or invalid time is entered at the end, e.g. “-08:00” or “08:98”, invalid values occur.
Correction result: If a negative or invalid time is entered at the start, e.g. “-08:00” or “08:98”, no endless loop during validation occurs.
Incorrect times are set to 00:00.
If a negative or invalid time is entered at the end, e.g. “-08:00” or “08:98”, no invalid values occur. Incorrect times are set to 00:00.
RFR-016462 Correction
Framework: Production
Application: Production orders
View: n.a.”
Action: Recalculate due date and quantity / Midpoint rescheduling
Category: Unexpected behavior
Problem: If the checkbox “Consider admin time” is not activated, the transitional goods receipt does not flow into the current end of the production order.
Correction result: On activating a new system property, The transitional goods receipt from the production order header is always used for scheduling regardless of the content of the checkbox.
Technical information: To get the desired result, the property “com.cisag.app.production.order.log.AlwaysUseTransitionTime” must be set to “true”.
5.1.4.1 Bills of material
RFR-016462 Extension
Framework: Production
Application: Bills of material
View: Bill of Material
Action: Save/Validate/Check all line items
Category: Invalid data
Problem: An equipment detail position could be saved with a non-existing or invalid item.
Correction result: When saving/validating a detail position, invalid items generate an error and the BoM cannot be saved.
5.1.4.2 Production orders
RFR-016462 Documentation
The help document “Vorgehensweisen: Produktionsaufträge” has been updated regarding the function “Mit Administrationszeit/Übergangszeit-Lagerzugang” in the context of recalculation of quantities and completion date.
RFR-016462 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Create/edit equipment position
Category: Unexpected behavior
Problem: For equipment positions in production orders, multiple input fields in the position editor are irrelevant/unused/misleading.
Correction result: Only show appropriate input fields.
5.1.4.3 Resources
RFR-016462 Correction
Framework: Production
Application: Resources / Import Resources
View: n.a.
Action: Change resource type
Category: Ergonomics
Problem: If the resource type of a resource is changed, the change is not automatically propagated to all existing versions.
Correction result: If the resource type of a resource is changed, the change is automatically propagated to all existing versions.
5.1.4.4 Where-used list
RFR-016462 Correction
Framework: Production
Application: Where-used list
View: all
Action: Refresh/Load
Category: Exception
Problem: The application crashes with an Exception when there are Bills of Resources shown, that contain too many Bills of Materials or Routings.
This can happen at around 350 or 700 or more BoMs/Routings at the same depth level, depending on database configuration and customizing.
Correction result: The application correctly shows the ProductionItems (from the BoMs/Routings) from Bills of Resources.
This also fixes a similar potential problem in the “Replace detail line item” dialog.
This also fixes a similar potential problem in the APS Production Planning.
5.1.5 Purchasing
5.1.5.1 Purchase orders
RFR-016462 Ergonomics
Framework: Purchasing
Application: Purchase orders
Action: Find and add external manufacturing line items
Category: Unexpected behavior / Ergonomics
Problem:
1. The title bars are added by using levels so the first title is bold and the second is italic. But the style should depend on user settings (e.g. theme) and should not be overridden by the application.
2. The dialog title uses parameters although this is not needed here – this is a disadvantage e.g. for translations and documentation.
Correction result:
1. Now the title bars are added without levels.
2. Now the dialog title is a string table entry without parameters.
5.1.5.2 Supplier invoices
RFR-016462 Correction
Framework: Purchasing
Applications: Purchase orders, Supplier invoices
Action: Purchase order action “Generate supplier invoices for third-party orders”
Category: Exception
Problem: The action creates in some cases an exception within the method “private QuantityMutable[] calculateOpenQuantities(SelfBillingOrderSource sbs)” of the class “com. cisag.app.purchasing.invoice.log.SelfBillingOrderEntityManager.”.
Correction result: Now the exception does not occur any more.
5.1.6 Sales
5.1.6.1 Customer invoices
RFR-016462 Correction
Framework: Sales
Applications: Customer returns, Sales orders, Customer invoices
Action: Create customer invoice, Customer return (apply defaults)
Category: Exception / Invalid data / Unexpected behavior
Problems:
1. The customer invoice generation does not consider for a kit component if the kit main detail was skipped because of the tax code type “EU end consumer delivery” (confirmed warning “SAL, 8889”) – so an exception occurs because a kit component was tried to be added to an invoice without the corresponding kit main detail.
2. If the “Reference” value of a customer return line item changes all kit components will be removed and added again. But this is not possible in some cases because for example the kit components are referenced by some booked receipt of goods.
Correction result:
1. Now the customer invoice generation skips also kit components if their kit main detail will be skipped because of the tax code type “EU end consumer delivery”. So now the exception does not occur any more in this case.
2. If the “Reference” value of a customer return line item changes the kit components will not be removed any more if a booked receipt assignment is present (booked receipt of goods, booked pickup shipping order or reported direct supplier receipt) – these details will be marked only as deleted now. Also such details will be reused if the new assigned reference (e.g. “Delivery slip line item”) provides again some kit components for the original order detail.
So by changing the customer return to a reference to the original invoice line item (“delivery slip line item plus invoice line item” or “cash invoice line item”) the customer return can be changed now also for kits.
After that you can refresh the credit note orders (will cancel the old one and create a new one); so the original invoice line item is present in the credit order line item and you can create the credit invoice also in case of “EU end consumer delivery”.
5.1.6.2 Kits
RFR-016462 Correction
Framework: Base
Application: Kits
Actions: Add new component
Category: Unexpected behavior / Ergonomics
Problem: In case of new component line items error messages are not available at the relevant field.
Correction result: Now the error messages are present at the relevant field as expected.
5.1.6.3 Sales fast entry vouchers
RFR-016462 Correction
Framework: Sales
Applications: Sales fast entry vouchers, Sales RFQs, Sales quotations, Sales orders
Actions: “Transfer manually” of the application “Sales fast entry voucher” plus new line item in target application
Category: Exception
Problem: If the “Transfer manually” of the application “Sales fast entry voucher” was performed and completed, an exception occurs during the save operation if any new detail was added by the this application instance.
Correction result: Now the exception does not occur any more.
5.1.6.4 Sales prices
RFR-016462 Correction
Framework: Purchasing, Sales
Application: Reorganize purchase/sales prices
View: n.a.
Action: n.a.
Category: Performance improvements
Description: Whether a price definition is in use is checked with bulk operations. The number of definitions for execution of such bulk operation (aka blocksize) influences the memory consumption as well as the number of full-table scans on the database and therefore the performance of the execution of the whole reorganization. It is now possible to configure the blocksize to adapt to the special needs in a certain system. An increased blocksize reduces the number of full-table scans but increases the memory consumption. Default blocksize is 32 (as in the past). If the blocksize exceeds 128, the check for used price definitions is moved from the database to the SAS. Whether this increases or decreases the performance depends on the data in the system. From technical point of view it should be possible to increase the blocksize to 10000 or even higher.
The blocksize can be changed with system property ‘com.cisag.app.purchasing.pricing.reorg.PriceReorganization_Blocksize’ resp. ‘com.cisag.app.sales.pricing.reorg.PriceReorganization_Blocksize’.
5.1.7 Service
5.1.7.1 Receipt of goods and Customer returns
RFR-016462 Correction
Framework: Inventory
Application: Goods receipts
View: Return of goods
Action: Post receipt of goods…
Category: Unexpected behavior
Problem: The warning message “PUR-1938” (valuation price will be zero) was displayed although the valuation of the inventory transaction later will not be zero.
Correction result: From now the warning message “PUR-1938” (valuation price will be zero) will be displayed only if the valuation of the inventory transaction later will be zero too.
5.1.8 Storage Location Control
5.1.8.1 Inventory requisitions
RFR-016462 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: n.a.
Action: add position.
Category: Unexpected behavior.
Problem: When entering the item in the Inventory requisitions application, it will be not checked whether the specified item can be stored in the specified fixed/picking location or not.
Correction result: The Problem is fixed.
5.2 System development
RFR-016461 Extension
Framework: System management
Application: system cockpit
View: application server
Action: n.a.
Field:Process Id
Category: New field
Description: The process id of the application server is displayed.
Technical information: Additionally a file named “Semiramis.pid” is written on startup into the server directory of the server.
If the application server is terminated regularly, this file is deleted on shutdown.
RFR-016461 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-016460 Correction
Class: com.cisag.pgm.datatype.CisTimeStamp
Method: createTimeStamp(long date)
Description: If a CisTimeStamp is to be created with one of the predefined minimum or maximum values, a singleton is returned instead of a new instance. The undocumented property com.cisag.pgm.datatype.CisTimeStampMutable has been removed.
RFR-016460 Correction
Framework: Software Development
Application: Editorial cockpit
View: Import text/translation
Action: import data
Category: Unexpected behavior
Problem: When a translated text is imported and the text object is locked in another task, then the data is written into a helper table (LdtDelayed).
Once the locking task is activated the data is transferred from the helper table into the real table.
But if there is no active text in the real table than this transfer did not happen.
That means completely new translations, i.e. there has never been a translation for this language, and the text object was locked at the moment of import, then the imported translation was effectively lost.
Correction result: The import of translation now works also in the case the text object is locked and there is no already existing translation for the language given.
RFR-016460 Correction
Framework: System management
Application: ODBC Data sources
View: n.a.
Action: File to create or change the user data source: createDSN.bat
Category: Unexpected behavior
Problem: The action should create a batch file for creating the data source. But the browser could not interpret the created url.
Correction result: The batch file will be created.
5.2.1 Application server
5.2.1.1 JobControl
RFR-016460 Correction
Framework: All
Context menus of Entity fields in applications
Category: Unexpected behavior
Problem: A context menu of an entity field may show only one of multiple cockpit applications that use the same cockpit search.
Correction result: The default context menu includes all visible cockpit applications that use the same cockpit search, if the cockpit search has an attribute of the entity field’s business object. Context menus must perhaps be reset to defaults to show missing cockpit applications.
Technical information: The issue may not occur if the cockpit application’s development objects declares a “Load” parameter for the business object.
5.2.2 Customizable cockpits
RFR-016461 Extension
Framework: All
Application: Customizable applications
View: n.a.
Action: n.a.
Field/Column: n.a.
Category: New feature
Description: Filter fields of cockpit widgets can be now assigned to (entity) fields of the hosting application. This allows automatic refresh of the cockpit result list, when the application changes its field values.
Technical information: The assignments between search fields and application fields can be made in the design mode of the application. The property (edit) dialog of the Cockpit-Widget has a new tab, where one or more such assignments are possible.
RFR-016460 Correction
Framework: All
Application: Customizable cockpits
View: Filter panel
Action: n.a.
Category: Unexpected behavior
Problem: Filter values saved in the application layouts of a customizable cockpit were not completely restored at switching between these layout, because actual values are carried over.
Correction result: If actual values should be carried over between application layouts can now be customized in the user settings application (“Display/Operation settings/Accept search criteria”).
This settings was already used, the behavior of actual filter value when switching between different cockpits. Now, it also applies to switching between application layouts as well.
5.2.3 Data exchange
RFR-016460 Correction
Framework: System Management
WADL description for REST web services
Category: Unexpected behavior
Problem: The WADL REST web service description available by a REST URI with query string ?_wadl containes multiple identical ”
Correction result: The mentioned section appears once.
RFR-016460 Correction
Framework: System Management
Application: Data exchange log entries
View: n.a.
Action: Open correction application…
Category: Exception
Problem: Exception will be thrown for Json error import file.
Correction result: It works properly.
5.2.4 GUI
RFR-016460 Extension
Framework: System Management
Application: User settings and Customizing
View: n.a.
Action: n.a.
Fields: “Font size” and “View (density)”
Category: New field/feature
Description: The new field “View (density)” in the “Display settings” section of tab “Display”, allows to configure the information density in the UI independent of the font size. It affects the size of the UIs elements as well as the spacing between then, but keeps the font size as specified in the field “Font size). Also the font size can be changed, without affecting the space consumed by the UI elements.
Note: The font size is now specified in “px” and no longer in “percent”.
5.2.5 Kernel
RFR-016460 Correction
Framework: system management
Application: crtdbinf
View: n.a.
Action: -nlsAutomatic
Category: performance
Problem: Due to an optimization for big BO / tables some tables are processed faster but other tables are processed much slower. Unfortunately we cannot easily combine both strategies, therefore we switched back to the old strategy.
Correction result: crtdbinf should be faster on average.
5.2.6 System – General
RFR-016460 Correction
Framework: All
Category: Unexpected behavior
Problem: A race condition was identified that, in specific conditions including a very high number of runnable threads in an application server, could lead to threads being blocked forever for no apparent reason, and/or exceptions like “java.lang.NullPointerException at com.cisag.sys.kernel. CisSessionManagerImpl$SessionCopyRunner.initializeSession (…)”. This issue appeared in very specific tests.
Correction result: The issue is resolved.
5.2.7 Workflow
RFR-016461 Correction
The help documents “Aktivitätsdefinitionen” and “Hintergrund-Anwendung “Hintergrund-Anwendungen im Workflow aufrufen”” (German versions) have been updated.