QFD 23.03.230505.1

Owned by David Chmielewski
Jun 08, 2023
2 min read

Version QFD 23.03.230505.1
Release Date 06/08/23
Description Hotfix

Release Notes

Category Summary Description Labels Acceptance Criteria Release Notes Documentation Link Story ID
Fix Assignment Classification Errors

Certain assignments are being incorrectly classified as User assignments which is leading them to be pulled incorrectly in the assignment groups.

  • Pending Credit Bureau Maintenance Service
    • Flow -ExecuteCreditBureauMaintenanceService
  • Pending Account Status Maintenance Service
    • Flow - ExecuteAccountStatusMaintenanceService
  1. When the Pending Credit Bureau Maintenance Service assignment is created it is classified as a "Pending" assignment.
  2. When the Pending Account Status Maintenance Service assignment is created it is classified as a "Pending" assignment.

Resolved an issue where Pending assignments were incorrectly set up as a User assignment. The Pending Credit Bureau Maintenance and the Pending Account Status Maintenance Service assignments were incorrectly classified as a user assignment.

 QPS-8617
Fix Recovery Rights Evaluation

The system used to send and indeterminate recovery rights check to process liability which is really not correct.  We should send chargebacks on those if the system could not figure it out.  When this was changed to send to recovery it introduced another bug.  If a recovery strategy has a hard failure but also has indeterminate results its sending it to recovery instead of process liability.
  1. When an automated recovery option only has indeterminate results for the recovery option it should be sent to recovery.
  2. When a automated recovery option has a hard failure the HasChargebackRights flag should be set to false and the dispute should be routed to process liability.
  3. When a client is not Colombia and the check box is not selected for 7700 checked for this recovery option it should not evaluate RC7700 in the automated recovery rights.

Resolves a issue where Mastercard fraud cases without rights are routing to disposition case to be reviewed.

 QPS-8413
Compatibility Update JackHenry Silverlake Parse XML

As a Jack Henry user, the trace number property should be mapped properly so users can reference the property when needed. 

 [Jack_Henry]
  1. ACHTrnSrchParametersResponse references pyAnyNS.Custom (CL- Int-JackHenrySilv-ACHTrnSrch-Custom_CType) for Custom under ACHTranSrchArray.

Updated the JackHenry Silverlake Parse XML call to ensure the trace number property is mapped correctly.

 QPS-8234