It has set Industry record in migrating over 150 branches every week for various Banks. Nelito has set up an Excellence Centre with Finacle 7x and 10x infrastructures at its Head Office and has been able to create talents in-house. The number of resources is over 300 by the year 2004, 450 by the year 2005 and over 600 by the year 2006. The Finacle practice was started with barely 10 resources in February 2004. Nelito started its Finacle journey in the year 2004 by becoming partner to Infosys Technologies and Hewlett-Packard. As a result, the remaining lines of codes after the CALL() function never shows up in the trace file.Nelito has a vast experience in successfully implementing Third Party CBS like Finacle Core Banking Solution for different sized banks. The fact that the called script already uses TRACE OFF at the end of the script, this also takes effect in the main script of the calling script. The called script is displayed as seen below: So all I did was to call TRACE ON immediately after the CALL() line. While going through the file, I discovered a part of the trace was not displayed, even though the TRACE was ON at the beginning of the script.Īfter much digging, I observed that a called script had already turned TRACE OFF. Of course, I needed to go through the generated trace file in the user log directory so as to know the cause of the problem. Ideally, dividend transaction should not be allowed for accounts whose Open Date is less than six months from the date of the transaction (Note: this depends on the bank policy).īut an account that was over six months old gave an error “Dividend Transaction Not Allowed ON A/C less than Six Months”. An outward clearing menu (HOCTM) was reported to give an error. Hope that was helpful? You can leave a comment below.Ī case was recently reported to me to resolve in the office. This is to make sure that when function appFnExecuteScript() returns it from the back end script, HTML document object is able to access it as a field.įinally, with the two scripts in the right directories on the server, the validations should take place when those events are fired on the menu.
This must have been created in the front end jsp ( tmdet_custom.jsp) as a hidden field as shown: Sv_m = urhk_SetOrbOut("SuccessOrFailure|F") Sv_m = "*** TDA Type Accounts *** Debit Not Allowed" Once this fields are gotten in the back end script, necessary validations can take place and the result returned to the front end as shown below: This values are gotten in the back end script from the INPUT class of the BANCS repository (as and _Dr) Var inputNameValues = "acctId|"+acctId+"|pTranType_Dr|"+pTranType_Dr This is made possible from the inputNameValues variable in the front end JSP. In the back-end script checkfortd.scr, notice the use of and _Dr. In the custom/jsp directory of finwas server, look for tmdet_custom.jsp. If that page does not already exist, this is a good time to create it.įrom the JSP source you downloaded above, you will observe three different functionsĪs their names imply, these functions are used by finacle for pre_ONCHANGE, post_ONLOAD and pre_ONCLICK events on the page.Īdd the necessary logic to the functions as seen in the source file ( tmdet_custom.jsp). Window showing field name for the Debit radio buttonįrom the figure above, the page name of my HTM details page is tmdet Similarly, get the field name of the Debit radio button. Window showing page name and the Acct ID field name.ģ. Also get field name from the below window. On the front-end and with your cursor on the field to validate, get the JSP page name of the menu by pressing CTRL+G.( A small window pops up as shown below)Ģ. The solution is to use the very useful javascript function( appFnExecuteScript()) to send parameters from the front-end JSP page to the back-end finacle script for the validation. But the challenge is that, that can only be done from within finacle script, and not from the front-end JSP. What can be done is to get the account and use a finacle user hook (eg urhk_getAcctDetailsInRepository()) to check the scheme type of the account and alert an appropriate message. Debit should not be allowed on such accounts. It is required to validate TDA type of accounts for Debit transactions in HTM. There are times when you may need to pass variables from the front-end of a finacle product menu to a back-end script for validations and send the output back to the front-end.