| Release | Comarch ERP Enterprise 6.3 |
| Release date | 15.08.2025 |
| Reference to other documents | You can find further information in the info texts of the support deliveries for Comarch ERP Enterprise 6.3.
This fix comprises the following support deliveries: RFR-016566– RFR-016568
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-Fix24”.
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-Fix24
With the delivered software updates, a Comarch ERP Enterprise system that has version CEE630PB-Fix23 will be upgraded to CEE630PB-Fix24.
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 data updates have to be carried out.
5 Contained changes and extensions
5.1 Application development
RFR-016568 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-016568 Correction
Framework: Base
Application: Voucher document templates
View: n.a.
Action: save, validate
Category: Unexpected behavior
Problem: Disabled fields (irrelevant data) will be validated. So, there is sometimes error message from unabled fields.
Correction result: Disabled fields (irrelevant data) will not be validated.
RFR-016568 Correction
Framework: Production
Application: Operations, Routings, Bills of materials, Bills of resources, Resource lists
View: n.a.
Action: Create document
Category: Exception
Problem: Performing action “Create document” in mentioned applications for object that has not any released version caused exception.
Correction result: Now exception is not thrown and proper document is generated and opened.
5.1.1 Base
5.1.1.1 Classifications
RFR-016568 Correction
Framework: Base
Application: Classifications
Action: “Delete”, “Mark for delete”
Category: Exception / Unexpected behavior / Ergonomics
Problem: If a specific classification type is maintained on the organization level and a new relevant organization was added (status “Entered”) and a node has no data for such organization an IllegalStateException (“Classification was not replicated for organization …”) occurs during the try to delete or set a deletion marker for such a node.
Correction result: Now instead of the exception an error message will be send (existing error message “GEN-07115”).
5.1.1.2 Contracts/RFQs/Quotations/Orders
RFR-016568 Extension
- Classes: “com.cisag.app.sales.proposal.log. ProposalEntity”, “com.cisag.app.sales.order.log.OrderEntity” and “com.cisag.app.multiorg.order.log. OrderEntity”
new methods:
– public final void setAvailabilityValidationDisabled(boolean availabilityValidationDisabled)
– public final boolean isAvailabilityValidationDisabled()
Description:
Theses new methods can be used to disable the availability vaildation even if it is enabled with respect to the relevant document type instance and item master data.
This is useful if the availability vaildation is not needed in some cases (e.g. import or document generation).
Hint: Please note that an “availability inquiry/validation” might be performed in some cases also if “availability vaildation” is disabled by this new property (e.g. because of item property “replaced/deleted if availability is zero”).
2.
The new method “setAvailabilityValidationDisabled” is used now in the following classes (together with “entity. getReservationLogic().disableTemporaryData(true)”): – com.cisag.app.inventory.receipt.log. SalesOrderGenerator
– com.cisag.app.multiorg.order.log.OrderBatchLogic
– com.cisag.app.multiorg. order.log.OrderImportController
– com.cisag.app.sales.customerreturn.log.AbstractOrderGenerator
– com.cisag.app.sales.order.log.OrderBatchLogic
– com.cisag.app.sales.order.log. OrderImportController
– com.cisag.app.sales.proposal.log.ProposalBatchLogic
– com.cisag.app.sales. proposal.log.ProposalImportController
– com.cisag.app.sales.rapid.log.TargetEntityFactory
3.
Class: “com.cisag.app.general.order.log.ReservationChangeData”.
methods: public void change(…, boolean newInstance, …)
The java documentation of the “newInstance” parameter has been corrected.
5.1.2 Calculation
RFR-016568 Correction
Framework: Calculation
Application: Output product cost calculations
View: n.a.
Action: Output report document in batch, Output report document immediately and display output to file
Category: Unexpected behavior
Problem: Selecting and outputting multiple product cost calculations is allowed and results in headers for all but the first product cost calculation missing from the output.
Correction result: Prevent selection of multiple product cost calculations at once. Add validation and error messages for the single selected product cost calculation.
5.1.2.1 Calculation – General
RFR-016568 Correction
Framework: Calculation
Application: Product cost calcultion maintenance
View: Total sum view
Action: Calculate…
Category: Unexpected behavior
Problem: Toggle button “Total” is clicked and total sums are displayed. Next button “Create simulation costs” is clicked.
Result: Beneath column “Simulated value” the total sums of simulated cost must be displayed. After creation of simulated costs simulated sums must have the same values as its counterparts of column “Total costs”. But “Labor costs” of simulated sums is missing.
If “Simulate with changed costs” is clicked “Labor costs” of simulated sums is displayed with correct calculated value.
Correction result: If in above described sequence button “Create simulation costs” is clicked “Labor costs” of simulated sums is displayed with correct value (same value as its counterpart of column “Total costs”).
Please note:
Product cost calculations calculated before this correction has been activated still show the incorrect behaviour. This behaviour changes after a calculation is performed anew.
5.1.3 Inventory management
5.1.3.1 Availability query
RFR-016568 Correction
Framework: Inventory Management
Application: Availability queries
View: All views
Action: Load
Category: Exception
Problem: Although the selection data were not valid it was tried to load data or execute list actions.
Correction result: If the selection data is not valid the list will be disabled as expected.
RFR-016568 Correction
Framework: Inventory Management
Application: Reorganize availability and demand data
View: n.a.
Action: Execute the reorganization not only for invalid data
Category: Unexpected behavior
Problem: If there was an availability data to be deleted and its demand type was not correct the reorganization could create an error message that a shipping order is missing.
Correction result: If the availability data to be deleted belongs to a shipping order that is already deleted it will be rerorganized without any error messages as expected.
5.1.3.2 Inventory postings
RFR-016568 Correction
Framework: Inventory management
Application: Import data
View: n.a.
Action: Import inventory transactions
Category: Exception
Problem: A loading unit posted via goods receipt cannot be corrected if the correction is made by importing material postings and there are several material postings in the import file that are intended to correct this loading unit.
Correction result: A loading unit posted to goods receipt can now be corrected simultaneously using multiple material postings.
5.1.3.3 Picking orders
RFR-016568 Correction
Framework: Inventory
Application: Picking orders
View: n.a.
Action: Complete picking order …
Category: Exception
Problem: An exception occurred when completing a picking order after canceling then reporting of a former reported detail line, that was reported by a transport order with an inventory packaging unit of measure.
Correction result: From now completing a picking order will work as expected.
5.1.3.4 Receipts of goods
RFR-016568 Correction
Framework: Inventory
Application: Goods receipts
View: Return of goods
Action: Create and display loading units …
Category: Exception
Problem: An exception occurred trying to pack an empties detail line.
Correction result: As expected from now the packing dialog will not contain any empties detail lines to pack.
5.1.3.5 Reservations
RFR-016568 Correction
Framework: Inventory Management
Application: n.a.
View: n.a.
Action: Save
Category: Unexpected behavior
Problem: The performance of reservation logic could be improved.
Correction result: The performance of reservation logic is improved now.
RFR-016568 Correction
Class: com.cisag.app.inventory.stock.log. WarehouseStockStorage, com.cisag.app.inventory.reservation.log.FixedReservationWorker
Method: WarehouseItemStockDynamicStorage.loadStockData(CisList), FixedReservationWorker.Context.Transaction. begin()
Description:
(WarehouseStockStorage) The OQL to detect the warehouse stock data was changed to improve the performance.
(FixedReservationWorker) The internal transaction handling within the fixed reservation logic was changed to improve the performance.
Several other little changes were made that belongs to new not peristent availability and demand data to improve the performance.
5.1.4 Multi-site capability
5.1.4.1 Distribution orders
RFR-016568 Correction
Framework: Purchasing
Application: Distribution order generation
View: n.a.
Action: Generate distribution orders
Category: Exception
Problem: In case there are no existing distribution recommendations in the DB (not even ones marked for deletion), a NullPointerException was thrown when Distribution order generation was run as a batch application via “Development objects”.
In case in distribution recommendation a batch job to create distribution orders was used as a time series, the first execution of the job worked normal (created distribution order and marked the used recommendations as deleted) but subsequent executions created further distribution orders from the same recommendations.
Correction result: In case there are no existing distribution recommendations in the DB (not even ones marked for deletion), instead of an NPE, info message “PUR-01109 No distribution generated. The selection provided no data.” is displayed.
In case in distribution recommendation a batch job to create distribution orders was used as a time series, the first execution of the job works normal: it creates a distribution order and marks the used recommendations as deleted, subsequent executions will not create distribution orders from the recommendations that have been marked for deletion.
5.1.4.2 Distribution recommendations
RFR-016568 Correction
Framework: Planning
Application: Distribution recommendations
View: List of recommendations
Action: Save
Category: Ergonomics
Problem: If user is editing delivery date AND availability date a transition time goods receipt is calculated out of the difference of the edited dates when recommendation is saved. If subsequently only one of the dates delivery date / availability date is changed the corresponding date is calculated from the before achieved transition time goods receipt. This behaviour also occurs when transition time goods receipt originally had a value greater zero due to transition time goods receipt of item -> planning view -> internal purchasing data.
If the user wants another relation between delivery date and availability date than the current one (that means another duration between these dates) he must (again) change both dates.
It can happen that the user erroneously changes these dates so that delivery date is after availability date which leads to an error message. Up to now this also leads to a negative value of transition time goods receipt and correction only works by changing both dates. This happens because calculation is done before validation and negative value thus remains.
Correction result: If user changes both delivery date and availability date and delivery date is after availability date the transition time goods receipt keeps its value. It will only be changed after user corrects his input so that saving is successful.
5.1.5 Planning
RFR-016568 Correction
Framework: Planning
Application: Material requirements planning, Generate purchasing recommendations, Generate distribution recommendations
View: n.a.
Action: Transfer planning data and execute planning, Generate purchasing recommendations, Generate distribution recommendations
Category: Unexpected behavior
Problem: If “availability date” was set to non-working day and:
1. “Transition time goods receipt” for the corresponding items was set to 0 days then the calculated delivery date was after availability date and displays transition time was negative.
2. “Transition time goods receipt” was bigger than 0 days then the calculated delivery date was transitional time plus one working days before availability date and displayed transition time in purchasing/distribution recommendations application was always one day bigger then corresponding item “transition time goods receipt”.
Correction result: If “availability date” for recommendation is set to non-working day and:
1. “Transitional time goods receipt” in item planning data is 0 the calculated delivery date is on first working day before availability date which means negative transition time and wrong order of dates is not generated anymore.
2. “Transitional time goods receipt” is bigger than 0 days the distance between availability date and delivery date in recommendations is always equal to the one specified in item planning data.
RFR-016568 Correction
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning
Category: Unexpected behavior
Problem: Context: Planning parameter “Plan inventoried packaging units” is active, Items ->Planning view “Plan inventoried packaging units” is active for some items. These items must have defined some inventoried item packaging units.
Planning is executed.
Result: For one or more of the items an error message is output in log file: “PRD-02532 The inventory-managed packaging units of article AX_10122 cannot be converted to the first article unit. Article is not planned.”
This is due to a wrong transfer of inventoried packaging. For specific sets of inventoried packaging units a necessary transfer of first unit of item is missing which causes the error.
Correction result: In above-described context transfer of inventoried packaging units together with first unit of item works properly. No such error message is output and items are planned properly.
RFR-016568 Extension
Framework: Planning
Application: Material requirements planning
View: n.a.
Action: Transfer planning data and execute planning, Update planning data and execute planning, Re-execute planning
Category: Unexpected behavior
Problem: Material requirements planning took a long time, especially for transferring item data and for transferring production-related data like variables.
Correction result: Material requirements planning is faster. Especially planning many items and sites is faster. Especially running MRP when items do not have a production view is faster.
RFR-016568 Extension
Framework: Purchasing
Application: Distribution Recommendations
View: n.a.
Action: Generate Distribution Orders…
Category: Performance
Description: Runtime performance of this batch action was improved by disabling the reservation of the generated positions while they are still unsaved (even when Customizing enables reservation of temporary positions).
Runtime performance of this batch action was improved by disabling the expensive availability validation. The availability validation will not generate warning messages any more.
5.1.5.1 Material requirements planning
RFR-016568 Correction
Framework: Production
Application: Check production planning structures
View: n.a.
Action: execute batch application
Category: Unexpected behavior
Problem: Despite running and ending correctly, the batch job would output an error message that the job was canceled (KRN-45).
Correction result: Error message KRN-45 is not displayed anymore, if the batch job ran correctly.
5.1.5.2 Material requirements query
RFR-016568 Correction
Framework: Planning
Application: Material requirements query
View: n.a.
Action: Refresh
Category: Exception
Problem: Under very special cirumstances, querying an item with packaged UOMs could lead to a null pointer exception.
Correction result: The possibility for a null pointer exception has been remedied.
5.1.5.3 Planning – General
RFR-016568 Correction
Class: com.cisag.app.general.item.log. AbstractItemRoleDataObject
Method: com.cisag.app.general.item.log.AbstractItemRoleDataObject. isPersistent()
Description: The method must not return getRoleEntity().isPersistent(). This could result in an infinite loop if ‘isPersistent()’ is called in ApplyDefaultsHook. From now it will always return super.isPersistent().
5.1.6 Production
RFR-016568 Correction
Framework: Production
Application: Production orders
View: n.a.
Action: Dispatch
Category: Unexpected behavior
Problem: In multi-level dispatched production orders there can be multiple sub-orders following each other immediately.
In case the 2nd sub-order has a first operation with a buffer time formula,
the system automatically creates a dependency to the previous sub-order.
This ensures that multi level dispatching in multiple orders and multi level dispatching in single orders
both use the buffer time via automatically created constraint.
If the user wants to have the sub-orders scheduled in parallel, no contraints must exist between the sub-orders.
The change also applies to the case of buffer time after at the last operation.
Correction result: A new system property allows to turn off the automatic constraint creation for operations with buffer time as as first operation in sub-orders.
Technical information: set com.cisag.app.production.order.log. NoBufferTimeBetweenSubOrdersOnDispatch=true
RFR-016568 Correction
Framework: Production
Application: Production Orders, Cockpit: Production Orders
View: n.a.
Action: Release, Dispatch and release
Category: Unexpected behavior
Problem: No error message is displayed, when item identifier creation fails, e.g., because the number-range ran out of numbers.
Correction result: An appropriate error message is shown.
Additionally, some potential problems with locking and saving have been fixed.
5.1.6.1 Bills of material
RFR-016568 Correction
Framework: Production
Application: Operations/ Operations templates Bills of materials / Bills of resources / Routings
View: n.a.
Action: Use value assistant in version field
Category: Unexpected behavior
Problem: When searching for a version of a ProductionPlan (i.e. bill of material, operation, etc.), all versions for all existing production plans indepenent of type were displayed, even if the code of a ProductionPlan was already typed into the corresponding field.
Correction result: Only the versions of the corresponding ProductionPlan (and ProductionPlanType) are displayed.
5.1.6.2 Production – General
RFR-016568 Correction
Framework: Production
Application: Reorganize production orders
View: n.a.
Action: n.a.
Category: Exception
Problem: A production order is reorganized even if there exists a parent production order referencing it, that would not be reorganized.
This can lead to all sorts of other problems, like Exceptions when such a referenced order is edited.
Correction result: A production order can only be reorganized if its parent production order, can also be reorganized. This means, the whole tree of production orders has to be reorganizable.
This applies for parent production orders by multi-level-scheduling process as well as parent production orders by cross-site process.
The reorganization of a production order now stops immediately, after the first error is encountered.
Technical information: Reorganizing a po finds its reachable root and checks recursively whether all sub-POs of this root are reorganizable. Only if they are, the po can be reorganized.
5.1.6.3 Resource groups
RFR-016568 Correction
Framework: Production
Application: Resource groups
View: n.a.
Action: n.a.
Open application
Category: Unexpected behaviour
Problem: Even though resource groups with capacity category “unlimited” are not allowed, it was possible to select this a field in application “Resource groups”. When trying to save, this led to error “PRD-02338 – A resource group may not be unlimited”.
Correction result: The field has been removed. Capacity category of resouce groups is now “time-dependent” by default.
5.1.7 Purchasing
5.1.7.1 Supplier invoices
RFR-016568 Correction
Framework: Purchasing
Application: Cockpit: Supplier invoices
Action: Mark for delete (reorganization)
Category: Invalid data / Unexpected behavior
Problem: In contrast to the supplier invoice application the deletion (here: reorganization) marker can be set by mistake since 6.2 for supplier invoices by the cockpit also for open invoices.
Correction result: Now the behavior is again as expected.
Hints: – In contrast to 6.1 the check with the message “PUR, 1267” will be performed now only if the message “PUR, 1264” was not send.
Hint: In the same way now also the the customer invoice check with the messages “SAL, 8152” and “SAL, 8153” will be performed now only if the message “SAL, 2049” was not send.
– Also in contrast to 6.1 the checks that belong to the messages “PUR, 1268”, “PUR, 1269”, “PUR, 1269” and the “InternalInvoicingData”-validations will be performed only at reorganization time (as for customer invoices).
RFR-016568 Correction
Framework: Purchasing
Application: Supplier invoices (additional costs)
Action: Assign orders
Category: Exception / Unexpected behavior
Problem: In contrast to normal invoices additional cost invoices support the usage of orders with a different currency. If such a different order currency can not be converted into the supplier invoice currency an exception occurs before this correction.
Correction result: Now the exception does not occur any more.
RFR-016568 Correction
Framework: Purchasing
Application: Supplier invoices
Action: Apply defaults
Category: Invalid data / Unexpected behavior
Problem: In a supplier invoice contains a kit main detail and the “cash discount base” of this kit main detail is maintained manually the kit component “cash discount base” value might be wrong if the “cash discount base” of this kit main detail was changed multiple times.
Correction result: Now the error does not occur any more.
5.1.8 Sales
5.1.8.1 Sales – General
RFR-016568 Correction
Framework: Sales
Application: Customer proposals, Distribution orders
Action: Apply defaults
Category: Unexpected behavior / Ergonomics
Problem: In contrast to the sales orders “apply line item default” logic the logic for customer proposals and distribution orders does not refresh the “cost of goods” value by a “old total quantity ==> new total quantity factor” if only the total quantity is changed from a non zero value to an other non zero value. Instead, the “cost of goods” value was refreshed always by the “item valuation price logic” (even if the item, identifier and storage area are the same).
So especially in cases were the “cost of goods” was changed or defined manually a total quantity change does not change as expected the “cost of goods” value.
Correction result: Now the logic of the customer proposals and distribution orders has been corrected so that all of these three documents have the same refreshment behavior.
Hints: – Please note that a change of the item, identifier (if present) or (source) storage area triggers always – as before – a new “Cost of goods” determination by the “item valuation price logic”.
– If the “cost of goods” and the “total quantity” are changed together (in the same “round trip”) the “cost of goods” value will – as before – not refreshed, so that the user defined value will not be changed.
5.1.8.2 Sales quotations
RFR-016568 Correction
Framework: Sales
Application: Customer proposals
Action: Copy or create by source, Import, …
Category: Invalid data / Unexpected behavior
Problem: In contrast to other order types the “customer proposal header source data” was not created correctly before this correction.
Especially the “com.cisag.app.general.order.hook.log. HeaderSourceState” was created after building the “com.cisag.app.sales.proposal.model. CustomerProposalAccess” so that for example a “com.cisag.app.general.order.hook.log.HeaderSourceState” implementation was not present as expected within a “com.cisag.pgm.base.hook.DataAccessInitializerHook” implementation.
Correction result: Now the behavior is as expected.
5.1.9 Storage Location Control
5.1.9.1 Empty storage units
RFR-016568 Correction
Framework: Sales
Application: Cockpit: Empties account
View: n.a.
Action: Generate balances
Category: Exception
Problem: An exception occurred if the selected organization is not a financials organization.
Correction result: From now the action will be executed as expected even if the selected organization is not a financials organization.
5.1.9.2 Inventory order types
RFR-016568 Correction
Framework: Storage Location Control
Application: Inventory order types
View: n.a.
Action: Save
Category: Exception
Problem: If a supplement was created for the inventory order type business object (TransportOrderType) an exception could be caused at save.
Correction result: The inventory order type can be saved as expected.
5.1.9.3 Inventory requisitions
RFR-016568 Correction
Framework: Inventory Management
Application: Inventory requisitions
View: n.a.
Action: Manually complete transport process
Category: Invalid data
Problem: If an inventory requisition line item was completed manually its availability and demand data were not completed.
Correction result: If an inventory requisition line item is completed manually its availability and demand data will also be completed as expected.
5.2 System development
RFR-016566 Correction
Optimizing CisConnectionPool
RFR-016566 Correction
Framework: System management
Application: Individual indexes
View: both
Action: load
Category: Unexpected behavior
Problem: When the user types the name of an index and presses enter, the application reports that data has changed, even though nothing has changed.
Correction result: The application loads the specified index on enter.
RFR-016567 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-016566 Correction
Framework: Workflow
check for authorization
Category: Exception
Problem: It might happen for users without admin authorization that there is an exception when a check for authorization is performed while they work in workflow context.
Due to technical reason a transaction must be created and committed. A session with Workflow context must not commit a transaction. This led to an exception.
Correction result: checks for authorization are now possible in the context of workflow.
RFR-016566 Correction
Framework: System management
Application: System cockpit
View: Application Server, Tab Database connections
Action: Double click on an active connection.
Category: Invalid data
Problem: The dialog shows the active SQL statement. In rare cases, it may happen that the current SQL is not displayed here, but an older one.
Correction result: The dialog shows the current SQL statement.
5.2.1 Application server
5.2.1.1 Batch
RFR-016567 Correction
Framework: System Management
Batch application dialogs
Category: Ergonomics
Problem: The notification options “only in case of errors” in the batch job submit dialog, tab “Background settings”, does not result in a notification if the batch job has error messages in the job log, but the job is finished in “Completed” state.
Correction result: The behaviour is correct because of the “Completed” status. The option labels were changed to “in case of an abort” to clarify how the notifications work.
RFR-016566 Correction
Framework: System Management
Batch application dialogs
Category: Ergonomics
Problem: The notification options “only in case of errors” in the batch job submit dialog, tab “Background settings”, does not result in a notification if the batch job has error messages in the job log, but the job is finished in “Completed” state.
Correction result: The behaviour is correct because of the “Completed” status. The option labels were changed to “in case of an abort” to clarify how the notifications work.
5.2.2 Data exchange
RFR-016566 Correction
Framework: Import data automatically
Execution of batch application
Category: Unexpected behavior
Problem: When the automatic data import is run to create batch jobs for files to import, the main batch job could have an unusual high CPU utilization.
Correction result: The problem is resolved.
RFR-016566 Correction
Framework: System Management
Application: Simplified data export, Simplified data import
Category: Unexpected behavior
Problem: In a BIS Lite export or import, an “IllegalOperationException” message could appear if the underlying BIS controller is extended using hook contract “com.cisag.pgm.bi.Controller”, hook “DependentAssociationHook”.
Correction result: The problem was resolved by modifying a detail in the extended part of the BIS controller’s ObjectInfo.
5.2.3 System – General
RFR-016567 Correction
Framework: Software Management
Application: Debug classes
View: n.a.
Action: Save and pin query template
Category: Unexpected behavior
Problem: Query templates do not work for this application, and the application’s history is not recorded.
Correction result: The problems are resolved.
RFR-016566 Correction
Framework: Software Management
Application: Debug classes
View: n.a.
Action: Save and pin query template
Category: Unexpected behavior
Problem: Query templates do not work for this application, and the application’s history is not recorded.
Correction result: The problems are resolved.
5.2.4 Workflow
5.2.4.1 Activity definitions
RFR-016566 Correction
Framework: Workflow
Application: Activity definition
View: n.a.
Action: Deletion marker on results list
Category: Unexpected behavior
Problem: Deletion marker on results list wrong setting state of combobox entry row and makes it impossible delete a row.
Correction result: Mark of delete is setting correctly on all rows.