TIBCO(R) Order Management 6.1.0 Hotfix-001 is now available

This hotfix can be downloaded from the TIBCO Support Web User Interface using your username and password for the TIBCO Support Web. Once logged in, you can find the hotfix under the Downloads Menu: "AvailableDownloads/ActiveFulfillment/6.1.0/Hotfix-1"

Files available for download:

TIB_om_6.1.0_HF-001_readme.txt
TIB_om_6.1.0_HF-001_rhel.zip
TIB_om_6.1.0_HF-001_debian.zip
TIB_om_6.1.0-HF-1_hotfix_readme_addendum.pdf
TIB_om_6.1.0.md5

Please take a look at the Readme file for the instructions on how to apply the hotfix.

================================================================================

Closed Issues in 6.1.0_HF-001

AF-21027
In OM 6.0.0 HF6, after generating an amendment plan, intermediate milestones that 
were previously completed are displayed as pending.

AF-21006
When "enableUniqueUDFNames" is set to true, SetPlanItem creates a new UDF with 
the same name and a different value instead of updating the existing UDF.

AF-20918
In OM 6.1.0, the database creation script creates a LOCAL index on the 
"NOTIFICATION" table, which is not partitioned.

AF-20891
In OM 6.0.0-HF5, starting microservices such as Orchestrator and AOPD with 
Prometheus monitoring enabled generates errors.

AF-20726
In OM 6.0.0-HF4, only "setReconnectOnException(true)" is enabled on the 
"JmsCachingConnectionFactory," which discards and recreates the cached connection 
after a JMS exception. If the EMS server remains unavailable, 
connection attempts fail immediately.

AF-20682
In OM 6.1.0, plan item milestones do not update their dependencies as expected.

AF-20554
TIBCO Order Management microservices fail to start when the SSL password is 
encrypted in the "application.properties" file. Even though it's now possible to 
use an encrypted value for "server.ssl.key-store-password" within that file, 
the same approach does not work for "javax.net.ssl.trustStorePassword".

AF-20552
The "enableOPDErrorHandling" configuration is missing in TIBCO Order Management 
version 5.1.0.

AF-20551
The "tibco.aff.orchestrator.planItem.execute.reply.dead" queue contains messages 
with orders that cannot be properly processed by Order Management services.

AF-20550
The GetOrderDetailsRequest SOAP service generates an error when the udf value is 
empty in an order.

AF-20548
The time received in the status change notifications is incorrect and different 
from the one that is configured in the server.

AF-20546
The missing information about the ERROR code and ERROR message has been added to 
Swagger UI for following APIs:
- WithdrawOrder
- CancelOrder
- SubmitOrder
- AmendOrder
- GetOrderDetails

AF-20516
PlanItems with intermediate milestones in Planfragment cannot transition to
complete until the intermediate milestone is completed.

AF-20515
Amendment orders remain in a suspended status with a 500 Internal Server Error 
in AOPD when multiple amendment requests with cancel actions are sent in parallel.

AF-20514
TIBCO(R) Order Management 6.0.0_HF-004 processes orders at a significantly slower
rate, with performance degradation linked to high CPU utilization, 
long-running HTTP requests, and waiting threads in AOPD and Orchestrator.

AF-20513
TIBCO(R) Order Management 6.0.0_HF-005 generates a circular dependency for 
cancellation amendment orders, causing orders to remain in a suspended status.

AF-20474
In OM 6.1.0, submitting an amendment during the feasibility phase results in an 
"Invalid amendment detected for line" error, and the order remains in the 
feasibility state.

AF-20445
Activity logs on OMSUI do not sort correctly by date and time.

AF-20435
OM 6.1.0 does not provide an XSD schema for Notifications, making it difficult 
to parse JSON notifications to XML in TIBCO BusinessWorks, especially when 
handling optional elements.

AF-20434
Orchestrator does not send the value element for UDFs when the value is empty.

AF-20428
In OM 6.0.0, when the Orchestrator pod is stopped during order processing, 
messages on the "tibco.aff.orchestrator.planItem.execute.reply" queue are lost, 
and affected plan items remain in the "EXECUTION" state.

AF-20326
In OM 6.1.0, the XSD schemas delivered with the installation are missing the 
orderID element in the "orderRequestType" complex type and the orderPriority element 
in the "headerRequestType" complex type.

AF-20270
TIBCO(R) Order Management 6.0.0_HF-005 generates a circular dependency for 
cancellation amendment orders, causing orders to remain in a suspended status.

AF-20269
In OM 6.0.0-HF04, you cannot close the END milestone of a plan fragment if any 
intermediate milestone is incomplete.

AF-20267
The amendment plan is generated in an incorrect sequence for compensate plan items.

AF-20266
REDO plan items do not follow sequencing after amendment.

AF-20265
The activate request is not sent when a cancel order is placed, causing the order to get 
stuck in suspended status. This leads to incorrect plan generation.

AF-20162
Plan items do not start even though all the dependent plan items are completed.

AF-20031
In OM 6.0.0-HF4, the "ORDER" and "ARCHIVAL" schemas are missing indexes on 
foreign key constraints for the "ORDER_EVENT" and "ORDER_RETRY_REQUESTS" tables 
in the Oracle database scripts.

AF-19972
Added the ability to remove a single "COMPLETED" or "CANCELLED" order using 
"orderRef/orderID".

AF-19970
After the amendment, the plan calculation in COMP planItem is not displayed correctly.

AF-19874
The amendment is still in the start state in the database but is not visible in 
the Order Management System UI amendment section.

AF-19863
"Select All" checkbox from OMSUI Order dashBoard does not work.

AF-19857
Passwords must support Advanced Encryption Standard (AES).

AF-19856
The "Search by dates" filter of the Order Management System UI is enhanced to 
perform advanced search.

AF-19834
Vulnerability scans report multiple critical and high-severity issues. 

AF-19831
In the Order Management System UI, the "Filter by Amended Orders" option is added. 
This enhancement helps filter orders for which amendments have been set.

AF-19830
The Swagger API documentation for the "GET /v1/planfragmentmodel/all" operation 
is incorrect.

AF-19828
In OM 6.0.0-HF2, pods connecting to EMS via SSL might fail to start.

AF-19826
On the Plan Items tab of the Order Management System UI, the sorting functionality 
for the Status, Plan Item ID, and other columns do not work as expected.

AF-19825
In OM 6.0.0-HF3, plan generation in AOPD fails with a "java.lang.StackOverflowError"
message.

AF-19824
A plan item does not transition to "COMPLETE" status after receiving a finish 
notification.

AF-19823
In OM 6.0 HF3, requests to OM services experience delays and remain stalled for 
several seconds even when there is no system load.

AF-19822
Incorrect "tenantId" and "planItemId" in the "PlanItemExecuteRequest" notification 
in Orchestrator logs.

AF-19819
In OM 6.0 HF3, the Archival Service returns a "Exception occurred in parsing" error
and a 400 status code, causing the bar chart to fail to load.

AF-19818
The ojdbc driver is upgraded to "ojdbc11-23.5.0.24.07" to ensure compatibility 
with Oracle 19c.

AF-19817
An enhanced query is introduced to add missing indexes in TIBCO Order Management.

AF-19815
The system is extremely slow when processing bulk orders. 
To improve performance, some indexes have been added.

AF-19814
The SetPlanItem call to DataService times out.

AF-19812
In OM 6.0.0, "SetPlanItem" and "GetPlanItems" requests using JMS do not return an 
"Order Not Found" reply on the queue when a non-existent order ID is used; 
instead, the request times out.

AF-19811
In OM 6.0.0 HF2, even when all plan items are in the "COMPLETE" state, the order 
remains in the "SUSPENDED" state.

AF-19805
In OM 6.0.0-HF3, error handling does not behave as expected during retries.

AF-19803
In OM 6.0.0 OMSUI, special characters are not supported in the admin password.

AF-19801
Requests for "GetPlanItems" and "SetPlanItems" using JMS result in a timeout.

AF-19797
Support for TIBCO Enterprise Message Service 10.x is added.

AF-19795
Detecting vulnerabilities in OM 6.0.0 HF-03.

AF-19794
A NullPointerException occurs during Plan Development Notification processing 
in the Archival service.

AF-19785
The endpoint with authentication functionality sends user credentials in the 
URL parameter despite using the HTTP POST method.

AF-19743
Support for Docker Compose version 2.36 has been added.

AF-19737
Withdraw requests for orders in the Order Management System UI failed, throwing an 
exception during order message deletion.

AF-19510
After a second amendment, the system displays the error 
"Action and UDFs cannot be modified simultaneously in an order line."

AF-19508
After a second amendment, the system creates an unexpected milestone dependency.

AF-19506
After the fourth amendment, the system returns an unexpected error.

AF-19504
After an amendment, the system unexpectedly creates "REDO" plan items.

AF-19502
In FOM 4.0.2-HF13, after amending an order, it gets stuck.

AF-19501
After an amendment in FOM 4.0.2 HF07, the system incorrectly calculates plan 
for the COMP plan item.

AF-19499
After a second amendment, dependencies are incorrectly updated.

AF-19497
Some FOM orders remain stuck in the "EXECUTION" state with no errors, even after
certain plan items are completed.

AF-19494
After upgrading to FOM 4.0.2 HF5, some amendments no longer function as expected.

AF-19492
When processing an amendment with "DisableAffinityBrokeUDFImpact" enabled, 
the system creates unexpected REDO plan items for previously completed affinity plan items,
resulting in duplicates.

AF-19490
After the second amendment, the REDO plan items are not triggered for the 
completed plan items.

AF-19488
In FOS 4.0.2, after canceling one order line in an amendment, affinity plan items 
are unnecessarily re-executed and do not retain their previous state.

AF-19487
After a second amendment, the system unexpectedly adds "REDO" plan items.

AF-19485
After an amendment, the system does not follow the correct sequencing between 
"REDO" and "COMPENSATE" plan items in the amended plan.

AF-19481
Unexpected REDO plan items are generated in the plan after you amended 
a plan with affinity plan items.

AF-19479
After the fourth amendment, the system generates dependency errors.

AF-19477
After the fourth amendment, plan item and its corresponding dependency are 
missing from the order plan.

AF-19475
An unexpected error occurs during the amendment of an order line.

AF-18884
UDF updates made in Data Service are only reflected in the Orchestrator and 
do not appear in Archival or OMS-UI.

AF-17497
In FOM 4.0.2-HF11, the maximum number of amendments on an order is limited by 
the length of the "PLANITEMID" column (varchar(255)).

AF-16685
Cannot migrate global indexes to local when created due to unique constraints.

AF-14126
Security scans report vulnerabilities including inadequate account lockout, 
cross-site scripting, unencrypted login requests, and insecure cookie attributes.

AF-14079
When starting OMS-UI, the logs display multiple warning traces.

AF-8746
Documentation does not provide sufficient detail on failover behavior and configuration.

================================================================================

TIBCO(R) Order Management 6.1.0 Hotfix-001 is now available