Unmasking Individual Fields Which Belong To A Table Not Working
(Doc ID 2985704.1)
Last updated on NOVEMBER 10, 2023
Applies to:
Oracle Financial Services Lending and Leasing - Version 14.12.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Unmasking of fields which belong to the same table is not working.
Currently when user unmask a certain field. For example, CUS_BIRTH_DT, user want to unmask this field. But when user run the batch job REDPRC_BJ_100_01, it generates the policy which is drop the policy at view level instead of individual column level.
EXPECTED BEHAVIOR
-----------------------
Customer wants functionality to unmask of fields which belong to the same table instead of policy generate to drop at view level.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.For Unmasking Masked Fields - Set Parameter for Data Masking for Required Fields as N.
2. Executing the batch job for policy creation - SET-RED - REDPRC_BJ_100_01.
3. Compiled Policy File generated.
4. Check Required Fields were Unmasked and Original Values were displayed.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot unmask particular field using the batch job, instead it generates the policy which will drop at view level instead of column level.
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 |