(/s/) Community Learn Products Training Downloads Suggest (/s/ideatio

FAQ (/s/faqs)  >  How to auto approve specific override raised via IRIS API

   Rate    Like    Bookmark

(/s/profile/0052K00000ASwrtQAD) How to auto approve specific override raised via IRIS API
Celine Seba Preeti Lawrence (/s/profile/0052K00000ASwrtQAD)  •  Aug 24, 2022  •  Transact > Others > Core Infra
  From R16 to R21

      151

The steps provided explain how a specific override raised for a VERSION API can be auto-approved provided the VERSION is used specifically for this
API.

We request you to follow the below steps such that a specific OVERRIDE gets auto-approved whenever it is raised for an FT posted via the version (say,
FUNDS.TRANSFER,FLOWE.API.1.0.0) and OFS.SOURCE record GCS or IRISINTERNAL (based on the queue name used in the IRIS war's jms.properties file).
1. Edit the VERSION record (screen used) for the IRIS API by setting the AUTO.OVERRIDES field to YES.
For example, if the FT version corresponding to the IRIS API is FUNDS.TRANSFER,FLOWE.API.1.0.0, then, please set the AUTO.OVERRIDES field to YES of this
VERSION record as shown below.

81 AUTO.OVERRIDES.... YES
Commit and authorize this VERSION record.
2. Find out the OFS.SOURCE used for the API posted. This can be identified by checking the jms.properties file present under the <iris_war>/WEB-INF/classes
directory. In the jms.properties file, kindly find the queue name corresponding to the property "internal.reqque.jndiname" and identify the OFS.SOURCE used
for this queue and corresponding MDB in TAFJEE ear file. As per default configurations, in jms.properties file, the property "internal.reqque.jndiname" will be
assigned to the "t24IRISInternalQueue" and this queue will be mapped to the OFS.SOURCE IRISINTERNAL
3. Create a subroutine with content as below where TEXT field is set to Y. This is configured to have the specific override to be auto-approved when the
override is triggered for the FT version and OFS.SOURCE corresponding to the API.
Example subroutine:
**********************************************
    SUBROUTINE ACCEPT.OVERRIDE
* Can be used to give any conditions as required.
    TEXT = 'Y'
    RETURN
***************************************************
Compile this JBC routine. Create a PGM.FILE record for ACCEPT.OVERRIDE id with type as "S".
4. Edit the OVERRIDE record ACCT.BAL.LT.LOCKED as shown below.
OFS.SOURCE : IRISINTERNAL (OFS.SOURCE identified in step 2)                                   
APP.VERSION : FUNDS.TRANSFER,FLOWE.API.1.0.0 (Version identified in step 1) 
SUBROUTINE : ACCEPT.OVERRIDE (Subroutine created and compiled in step 3)
With this setup in VERSION and OVERRIDE record, when a transaction is passed through the OFS.SOURCE "IRISINTERNAL", and the "AUTO.OVERRIDES" field is set
to YES in the VERSION record of FUNDS.TRANSFER,FLOWE.API.1.0.0, then when a transaction is passed through this VERSION, the subroutine in the SUBROUTINE
field is triggered.
This subroutine, if it returns a value Y in the TEXT variable, then this particular OVERRIDE will be accepted automatically.
5. For the ACCEPT_OVERRIDE class generated, kindly generate a T24 component package jar for the same, include the jar in the t24lib directory used by the
application server. In case of jboss, place the jar with this class in jboss/modules/com/temenos/t24/main/t24lib directory and ensure the jar name is
present in the corresponding module.xml.
6. Restart the appserver and test the API.
Below is an example where the request body is posted without the expected OVERRIDE id in the payload.
{
"header": {
"override": {
},
"audit": {
}
},
"body": {
"debitAccountId": "90832",
"debitCurrencyId": "USD",
"debitAmount": 119,
"creditAccountId": "11193",
"creditCurrencyId": "USD",
"transactionType": "AC"
}
}
The API response received for the transaction posted through IRISINTERNAL OFS.SOURCE and the VERSION for which the AUTO.OVERRIDES was setup - here,
this specific override raised with the variable value is auto accepted.
{
"header": {
"transactionStatus": "Live",
"audit": {
"T24_time": 8080,
"parse_time": 1,
"responseParse_time": 2,
"requestParse_time": 15351,
"versionNumber": "1"
},
"id": "FT19107YTPJS",
"status": "success"
},
"body": {
"transactionType": "AC",
"debitCurrencyId": "USD",
"processingDate": "2019-04-17",
"creditCurrencyId": "USD",
"debitAccountId": "90832",
"debitAmount": 119,
"creditAccountId": "11193",
"overrides": [
{
"override": "ACCT.UNAUTH.OD}Unauthorised overdraft of & & on account &. *(IRISINTERNAL APPROVED)*{USD}862}90832{USD{862{90832{100100{213{{"
}
]
}
}
Thus, it is not required to send the override with the variable value in the request payload.

  OVERRIDE (/s/articlelistview?tag=OVERRIDE) ,  IRIS API (/s/articlelistview?tag= IRIS API) ,  Auto approval (/s/articlelistview?tag= Auto approval)

0 Comments

Post Question

Share an update... Share

Sort by:

Most Recent Activity Search this feed...

Collaborate here!
Here's where you start talking with your colleagues about this.

ompany Legal Follow

nvestor Relations Cookie Policy
https://www.temenos.com/about- (https://www.temenos.com/legal- (https://www.linkedin.com/company/temenos) (https://www.linke
s/investor-relations/) information/cookie-policy/)

ress Releases Privacy Policy

https://www.temenos.com/news/) (https://www.temenos.com/legal-
information/privacy-policy/)

Supplier Information
(https://www.temenos.com/information-
for-suppliers/)

Terms & Conditions

(https://www.temenos.com/legal-
information/website-terms-and-
conditions/)

Copyright © 2012-2023 Temenos Headquarters SA