My Oracle Support Banner

System Becomes Unresponsive When Attempting to Input '0' in 'Confirm Account Number' Field While Doing Adhoc Internal Payment Transaction (Doc ID 2996278.1)

Last updated on JANUARY 12, 2024

Applies to:

Oracle Banking Digital Experience - Version 22.2.0.0.0 to 22.2.0.0.0 [Release 22]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
When attempting to input '0' in 'Confirm Account Number' field and perform tab out while doing Adhoc Internal Payment transaction, following API gets fired - '../digx/v1/payments/generic/internal/0?locale=en' and SOAP request passed to host. Due to this host does a like search to return all accounts like ‘%0%' which creates very large response.

EXPECTED BEHAVIOR
-----------------------
Field level validation error should be added on 'Confirm Account Number' field similar to what is present in 'Account Number' field.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login as Retail user.
2. Open toggle menu and navigate to Payments > Payments & Transfer > Adhoc Payment.
3. Select 'Transfer Type' as 'Internal', input '0' in 'Confirm Account Number' field.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.