Masking Account Balances
- pk8barnes
- Topic Author
- Offline
- New Member
Less
More
- Posts: 10
- Thank you received: 1
13 years 2 months ago #8826
by pk8barnes
Masking Account Balances was created by pk8barnes
Hello All,
I am trying to mask a group of Accounts belonging to a specific CATEGORY to prevent staff of a bank seeing balances on these accounts.
Trying to use the USER profile of tellers and Bank staff to prevent viewing of these accounts is not working. I will be grateful to have alternate opinions on how t o resolve this
Thanks
I am trying to mask a group of Accounts belonging to a specific CATEGORY to prevent staff of a bank seeing balances on these accounts.
Trying to use the USER profile of tellers and Bank staff to prevent viewing of these accounts is not working. I will be grateful to have alternate opinions on how t o resolve this
Thanks
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired
Less
More
- Posts: 2859
- Thank you received: 649
13 years 2 months ago #8827
by jpb
Replied by jpb on topic Re: Masking Account Balances
Your request is not quite clear.
If you want to block access to these accounts completely for the users you can use the fields APPLICATION VERSION FUNCTION FIELD.NO DATA.COMPARISON DATA.FROM DATA.TO in either USER or USER.SMS.GROUP.
At least ACCOUNT and TELLER must be restricted (for TELLER use also ACCOUNT>CATEGORY in FIELD.NO).
If you just want to hide the balance you have to modify all your enquiries and versions.
If you want to block access to these accounts completely for the users you can use the fields APPLICATION VERSION FUNCTION FIELD.NO DATA.COMPARISON DATA.FROM DATA.TO in either USER or USER.SMS.GROUP.
At least ACCOUNT and TELLER must be restricted (for TELLER use also ACCOUNT>CATEGORY in FIELD.NO).
If you just want to hide the balance you have to modify all your enquiries and versions.
- For versions you can use e.g. a ID.RTN (defined in VERSION.CONTROL) to change the T()<1> of all balance fields to "PASSWD" (including NEW.CUST.BAL in TELLER) when your conditions meet.
- For enquiries it might work to use a routine as CONVERSION for the fields in question to hide the numbers.
Please Log in or Create an account to join the conversation.
- AMMAR.FAIDI
- Offline
- Elite Member
Less
More
- Posts: 266
- Thank you received: 14
13 years 2 months ago #8837
by AMMAR.FAIDI
Replied by AMMAR.FAIDI on topic Re: Masking Account Balances
as jpb said
you have to amend the user or a group of users by using the below :
APPLICATION = ACCOUNT
FIELD = CATEGORY
COMAPRISION NE
FROM DATA = CATEG NUMBER
B.R
you have to amend the user or a group of users by using the below :
APPLICATION = ACCOUNT
FIELD = CATEGORY
COMAPRISION NE
FROM DATA = CATEG NUMBER
B.R
Please Log in or Create an account to join the conversation.
- pk8barnes
- Topic Author
- Offline
- New Member
Less
More
- Posts: 10
- Thank you received: 1
13 years 2 months ago #8838
by pk8barnes
Replied by pk8barnes on topic Re: Masking Account Balances
Hi Ammar ,JPB and all,
I have tried using the above recommendation but it totally restricts the USER from the Account type (Category) and not only the Account Balance field.
I will be very interested in knowing more about the modification of the versions and enquiries. Kindly send me a bit more information.
Thanks
I have tried using the above recommendation but it totally restricts the USER from the Account type (Category) and not only the Account Balance field.
I will be very interested in knowing more about the modification of the versions and enquiries. Kindly send me a bit more information.
Thanks
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired
Less
More
- Posts: 2859
- Thank you received: 649
13 years 2 months ago - 13 years 2 months ago #8845
by jpb
Replied by jpb on topic Re: Masking Account Balances
Hello Paa Kay,
a way to hide the balances can be to create a routine that manipulates the T() array for the balances. This routine should be attached in VERSION.CONTROL as ID.RTN, setting NON.VERSION.RUN to Y helps avoiding troubles. Make sure all VERSIONs you use have EXC.INC.RTN set to Y.
For TELLER it would be easiest to eliminate the balance from versions and deal slips ;-)
For ENQUIRIES you have to either create a routine that set O.DATA to nothing when your conditions meet and attach it to each BAL field shown. This is to be done for each ENQUIRY individually as you have to pass the accountnumber or category with the balance (concatinated within the EQ) and return either nothing or only the balance from the routine in O.DATA.
Or you build the logic within each enquiry by defining fields that get hold of category and userdetails and then use something like IF a EQ ok showbalance empty.
Each way some work to be done.
a way to hide the balances can be to create a routine that manipulates the T() array for the balances. This routine should be attached in VERSION.CONTROL as ID.RTN, setting NON.VERSION.RUN to Y helps avoiding troubles. Make sure all VERSIONs you use have EXC.INC.RTN set to Y.
SUBROUTINE HIDE.ACCT.BAL
$INSERT I_COMMON
$INSERT I_EQUATE
$INSERT I_F.ACCOUNT
$INSERT I_F.USER
*
*---> set all BALANCES to it's original
*
T(AC.OPEN.ACTUAL.BAL)<1> = "AMT"
T(AC.OPEN.CLEARED.BAL)<1> = "AMT"
and so on
*
*---> Check if User has to be blocked
*
IF R.USER<EB.USE...> EQ ... ELSE RETURN
*
*---> read the record with actual input (not yet done by application itself)
*
FN.ACCT = "F.ACCOUNT"
F.ACCT = ""
CALL OPF(FN.ACCT,F.ACCT)
READ R.ACCT FROM F.ACCT,COMI ELSE RETURN
*
*--> change fields if category matched blocked
*
IF R.ACCT<AC.CATEGORY> EQ ... THEN
T(AC.OPEN.ACTUAL.BAL)<1> = "PASSWD"
T(AC.OPEN.cleared.BAL)<1> = "PASSWD"
and so on
END
*
RETURN
END
For TELLER it would be easiest to eliminate the balance from versions and deal slips ;-)
For ENQUIRIES you have to either create a routine that set O.DATA to nothing when your conditions meet and attach it to each BAL field shown. This is to be done for each ENQUIRY individually as you have to pass the accountnumber or category with the balance (concatinated within the EQ) and return either nothing or only the balance from the routine in O.DATA.
Or you build the logic within each enquiry by defining fields that get hold of category and userdetails and then use something like IF a EQ ok showbalance empty.
Each way some work to be done.
Last edit: 13 years 2 months ago by jpb.
The following user(s) said Thank You: pk8barnes
Please Log in or Create an account to join the conversation.
- pk8barnes
- Topic Author
- Offline
- New Member
Less
More
- Posts: 10
- Thank you received: 1
13 years 2 months ago #8918
by pk8barnes
Replied by pk8barnes on topic Re: Masking Account Balances
Thanks. Will give you feedback on the successful setup
Please Log in or Create an account to join the conversation.
Time to create page: 0.084 seconds