Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Masking / Conditional Hide Bank Account Holder Field on Employee Self-Service Page

Summary:

Masking / Conditional Hide Bank Account Holder Field on Employee Self-Service Page

Content (required):

Dear Experts,

Our client has shared accounting cases (joint bank account) with huge employee count. Hence, we had enabled Account Holder and Secondary Account Holder fields on Employee Self-Service(ESS) UI for many legislations.

Default cloud application is behavior is - in case employee creates bank account which already exists in database, system will throw a warning message and on acceptance of the same, application refreshes the UI with primary account holder name.

Example: Employee A has already defined bank account 1234 and later Employee B also (by mistake) tries to create bank account 1234 - in such case, Employee B receives warning message if they are ok to define Joint Account. If Employee B accepts the message and proceed further, application refreshes the page and updates the Account Holder as Employee A.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!