- Forum
- T24 Technical Discussions
- T24 Development & Customization
- Restrict user(s) from authorize transaction having limit 10 M above.
×
Discuss on Template programming, jBASE programming, Enquiries, No-File enquiry, Enquiry routines, Version, Version routines, Menus, Abbriviations, Creating local reference fields, Fast path enquiries, Creating charts and graphs, Generating Reports, Deal slips, Straight through processing, Multi Company and Multi Book setup, Tabbed screens, Composite Screens, T24 API, etc...
Restrict user(s) from authorize transaction having limit 10 M above.
- assiddiqui
- Topic Author
- Offline
- Premium Member
-
Less
More
- Posts: 128
- Thank you received: 0
7 months 3 weeks ago #23757
by assiddiqui
Restrict user(s) from authorize transaction having limit 10 M above. was created by assiddiqui
HI,
My requirement is to restrict user(s) from authorize transaction having transaction Amount greater than 10 million, it will be authorised by Manager and above. How to perform this task by using routine ??
My requirement is to restrict user(s) from authorize transaction having transaction Amount greater than 10 million, it will be authorised by Manager and above. How to perform this task by using routine ??
Please Log in or Create an account to join the conversation.
- VK
-
- Offline
- Platinum Member
-
- TAFC/J|R19/R22
Less
More
- Posts: 1008
- Thank you received: 132
7 months 3 weeks ago #23758
by VK
Cheers
VK
Replied by VK on topic Restrict user(s) from authorize transaction having limit 10 M above.
Hi
though the standard approach is to set up OVERRIDE, OVERRIDE.CLASS and DISPO, it might be a nightmare to setup and use, especially DISPO...
The quick way - with a routine - to create an INPUT routine (in non-manager VERSION) where you check transaction amount and raise an error if it exceeds the threshold.
though the standard approach is to set up OVERRIDE, OVERRIDE.CLASS and DISPO, it might be a nightmare to setup and use, especially DISPO...
The quick way - with a routine - to create an INPUT routine (in non-manager VERSION) where you check transaction amount and raise an error if it exceeds the threshold.
Cheers
VK
Please Log in or Create an account to join the conversation.
- VK
-
- Offline
- Platinum Member
-
- TAFC/J|R19/R22
Less
More
- Posts: 1008
- Thank you received: 132
7 months 3 weeks ago #23759
by VK
Cheers
VK
Replied by VK on topic Restrict user(s) from authorize transaction having limit 10 M above.
.. actually AUTH routine might be a better place for it...
Cheers
VK
Please Log in or Create an account to join the conversation.
- assiddiqui
- Topic Author
- Offline
- Premium Member
-
Less
More
- Posts: 128
- Thank you received: 0
6 months 3 weeks ago #23816
by assiddiqui
Replied by assiddiqui on topic Restrict user(s) from authorize transaction having limit 10 M above.
authorization routine is not working on FastPath enquiry, unable to raise Error and restrict transaction while authorization.
Please Log in or Create an account to join the conversation.
- VK
-
- Offline
- Platinum Member
-
- TAFC/J|R19/R22
Less
More
- Posts: 1008
- Thank you received: 132
6 months 3 weeks ago #23818
by VK
Cheers
VK
Replied by VK on topic Restrict user(s) from authorize transaction having limit 10 M above.
hi
you can add it to VERSION.CONTROL, setting NON.VERSION.RUN to Y.
you can add it to VERSION.CONTROL, setting NON.VERSION.RUN to Y.
Cheers
VK
Please Log in or Create an account to join the conversation.
- MasterL
-
- Offline
- Premium Member
-
Less
More
- Posts: 137
- Thank you received: 14
2 weeks 5 days ago #24035
by MasterL
Replied by MasterL on topic Restrict user(s) from authorize transaction having limit 10 M above.
The problem with authorization routines is that they are not designed to do any validations or block anything. Even if you raise an error in auth routine the transaction will most likely go through. If I have to limit at authorization using a version routine I would probably work with ID routine and block the user from opening the transaction in the first place (Like Temenos has implemented for same inputter/authorizer).
Another challenge with version routines is that you have to be sure the version either has the routine attached, or is linked to the version control.
I'm interested to know which solution worked.
If still an open issue you could try global constraints to raise override for all txns over 10M then create an override class and assign it only to the users that are allowed to authorize above the limit.
Another challenge with version routines is that you have to be sure the version either has the routine attached, or is linked to the version control.
I'm interested to know which solution worked.
If still an open issue you could try global constraints to raise override for all txns over 10M then create an override class and assign it only to the users that are allowed to authorize above the limit.
Please Log in or Create an account to join the conversation.
- VK
-
- Offline
- Platinum Member
-
- TAFC/J|R19/R22
Less
More
- Posts: 1008
- Thank you received: 132
2 weeks 5 days ago #24038
by VK
Cheers
VK
Replied by VK on topic Restrict user(s) from authorize transaction having limit 10 M above.
Hi
Last time I checked setting E variable in AUTH routine stops the processing.
Last time I checked setting E variable in AUTH routine stops the processing.
Cheers
VK
Please Log in or Create an account to join the conversation.
- MasterL
-
- Offline
- Premium Member
-
Less
More
- Posts: 137
- Thank you received: 14
2 weeks 5 days ago #24039
by MasterL
Replied by MasterL on topic Restrict user(s) from authorize transaction having limit 10 M above.
Oh, that's awesome. I'll try it
Please Log in or Create an account to join the conversation.
- Forum
- T24 Technical Discussions
- T24 Development & Customization
- Restrict user(s) from authorize transaction having limit 10 M above.
Time to create page: 0.129 seconds