Fixes
Validate Corporate Ref No Only Against Root Transactions (GMK-7114)
The system now allows banks to issue guarantees with any CustomerRefNo. For new guarantees created by corporates, duplicate checks are performed only against root transaction records, preventing false duplicate errors from issuance records.
Automatically Clear Credit Line on Send for Bidding in Market (GMK-10280)
The system now automatically clears the credit line field when the user clicks "Send for Bidding," ensuring that the bank name matches the accepted bid and preventing mismatches during guarantee application.
Display Local Bank Details for Indirect GTI Created via Data Transfer (GMK-10671)
The system now correctly links the Q-Code to the address book for indirect GTI guarantees, displaying the local bank name, address, and country as expected.
Retain Local Guarantor When Changing Credit Line for Indirect Guarantees (GMK-10674)
The Local Guarantor field now retains the user-entered value when the credit line is changed for indirect guarantees on the Edit Guarantee Transaction Details screen (SC811E).
Display Beneficiary Group for Transactions Created via Qform or Data Transfer (GMK-10785)
The Beneficiary Group value now appears on the view transaction page for transactions created via Qform or data transfer. The Beneficiary Group field is also added to both the View and Edit Qform pages.
Handle Multiple Address Book Matches for BIC in LCE Transactions (GMK-10946)
If multiple address book entries match the same BIC ID for incoming LC transactions, the system will no longer insert name and address from the address book. Instead, it will refer to the SWIFT BIC directory for accurate information.
Guarantor Type Error for Data Transfer Guarantees (GMK-11021)
Resolved an issue where guarantees created through Data Transfer under a Credit Line with Guarantor Type "Bank and Insurance" resulted in errors if the Guarantor Type was set to either "Bank" or "Insurance". The system now correctly accepts these types without error.
Fixed Auto Processing Issue for Message Bundle with Late Attachments (GMK-11095)
Resolved an issue where the platform failed to auto-process the message bundle when an actual attachment came after the FIN and Companion files. The system now correctly processes the bundle, regardless of the sequence of uploads.
Add 45L Variable for Underlying Transaction Details in Insert Variable Popup (GMK-11105)
The 45L variable for Underlying Transaction Details has been added to the Guarantee Text Insert Variable popup, allowing users to insert it when editing guarantee text.
Fixed Contract Module Error on Transaction List in QA Environment (GMK-11145)
The issue causing an error when accessing the Transaction list in the Contract module has been resolved. Users can now view existing transactions as expected.
Alarm Notification for LCE Expiry Date Condition Trigger (GMK-11189)
The alarm job now correctly triggers notifications only for the main LCE transaction based on the expiry date condition, preventing notifications from being sent to associated document sets.
Guarantee List Visibility Issue with Categories (GMK-11196)
The guarantee list now displays correctly when filters with categories are applied, resolving the issue where the list was previously not shown.
Length Exceeding Issue for Tag 37J in SWIFT Messages on Q Form (GMK-11207)
The length of Tag 37J is now limited to 12 characters (rounded to 2 decimal places) in MT<784> and MT<760> messages on Q form, aligning with the SWIFT standard and preventing message rejection by the bank.
23H Function Options and Dependencies in SWIFT Ancillary Messages Aligned (GMK-11371)
The platform now correctly maps the DTA options to the OTHERFNC Swift option in 23H for M798<726+759> messages. Additionally, missing options (PREDENOT, REXTMATU) are added to the list, and the system ensures that the 23H option is validated against the selected 22D option, preventing message rejection.
Fixed error 600 for Amendment/Reduction on Multiparty Transactions with Amount Change (GMK-11471)
Error 600, which occurred when changing the amount on an amendment for a multiparty transaction involving multiple currencies, has been resolved. Users can now amend and change amounts without encountering the error.