OFS Response Structure

Hello,

I've noticed that T24 OFS response has 2 different structures:
a) FIELD.NAME=VALUE:MV:SV
b) FIELD.NAME:MV:SV=VALUE

To illustrate, the responses below are from an actual FT request which generated 2 responses (the accounts are under AA)

The FT response looks like this:
The AA response looks like this:
First, is there a setting or a parameter to standardise the response format?
Secondly, is there a way to anticipate which format the response will be in?

Thank you

You can check the format on attached file. For more info, you may visit the TCSP portal Ref of OFS Request Syntax of Transactions

Most of the time I'm using the OFS.BUILD.RECORD before OFS.CALL.BULK.MANAGER. But on the TCSP portal it was recommended to use the OFS.POST.MESSAGE function. I've attached the snippet code FYR

P.S 1: If you're going to write the results on file and you will use multiple agents (>2). It is recommended to add a suffix of AGENT.NUMBER to write file per agent, then later on you merge the file on .SELECT file. This will prevent locking and can dramatically increase the speed.

P.S 2: When you're going to use the OFS on Version Routine Level, use ofs.addlocalRequest

Hi,

I think you misunderstood my question. I already know the response format for OFS. I am looking to find why there are 2 different formats (only one of the formats is referenced in Temenos docs) and if there is a way to anticipate or set which format to use.

It's a bit difficult to build an OFS response consumer when the response is coming in 2 different formats.

I don't think this is an issue, you can just easily create a condition statement for OFS response. there is an indicator in the guidelines to verify whether the ofs response is an error

Gosh. Getting the error/override response status is pretty straightforward. That's not what I'm talking about. Just so I am clear, this post is not about OFS request/response processing. It's purely about field, mv, sv and value order in the response string.
vs
Kindly read my original post again.

Anyway. Never mind. I'll just write a consumer for both formats. If I find any pattern in which format is used I will update accordingly.

Each field on t24 is either configured as single or multivalued field. Its like on xml you can create many nested info.

Kindly read first the TEMENOS GUIDELINES which is available on TCSP Portal

Are you even making an attempt to read and *understand* my question? In the original sample I gave, both responses are coming from T24 and both feature CURR.NO and RECORD.STATUS which are single value fields.
Please, I beg of you, read and understand my question. If you do not have an answer for the question, it's ok. I also don't know which is why I'm asking.
FYI I attached in my first response to you a screenshot from TCSP that shows the format where only the field value is on the right of the = sign, the field name and MV/SV positions are on the left of the = sign.
There are other instances where the field value and the MV and SV positions are on the right of the = sign.
That is all I'm asking in this post.

This is Temenos format of OFS. You need to follow their syntax as they are the one who build it. Also if you see this an issue its EASY to file an request on TCSP Portal and they will evaluate your request. If you're issue is valid, they will moved it on MAINTENANCE and create an core update for you.

FYI you're attached picture was based related to response data. "FieldName=Content:MultiValueNumber:SubValueNumber" can you make an example screenshot from tcsp documentation?

This is the valid format as per TEMENOS User guide

I give up

FieldName=Content:MultiValueNumber:SubValueNumber = I cant find it. maybe you're mistaken LOL

Fair enough.

Can we then let the ones that might have an idea to respond? What I've learnt in my years working with T24 is that nobody knows everything. That's why we have forums as this to educate and update each other. It's ok not to have all answers.

MasterL wrote: wrote:

Hello,

I've noticed that T24 OFS response has 2 different structures:
a) FIELD.NAME=VALUE:MV:SV
b) FIELD.NAME:MV:SV=VALUE

To illustrate, the responses below are from an actual FT request which generated 2 responses (the accounts are under AA)

The FT response looks like this:

RECORD.STATUS=INAU:1:1,CURR.NO=1:1:1

The AA response looks like this:

RECORD.STATUS:1:1=INAU,CURR.NO:1:1=1

First, is there a setting or a parameter to standardise the response format?
Secondly, is there a way to anticipate which format the response will be in?

Thank you

I've checked on OFS.REQUEST.DETAILS Application an actual transaction on our LIVE environment, our MSG.OUT value contains below
"RECORD.STATUS:1:1=INAU,CURR.NO:1:1=1,INPUTTER:1:1=19438_OBANK__OFS_OBANK,DATE.TIME:1:1=2010021033,CO.CODE:1:1=HT0010088,DEPT.CODE:1:1=1000"

There is TCSP portal which have the T24 User Guides, there is also Customer support which you can freely ask related to your issue. They may enhanced the OFS application related to your release that might affect your response format which is not available on user guide

Thank you for taking the time to check.

As I mentioned in the first post, there are some messages that come with the other format. Which is why I'm asking if there is a way to tell what drives which format T24 uses.

I've attached here an actual response but with bank and customer details redacted (obviously). You will notice there are two transactions in one due to the account affected being an AA account (under the AR module).
The first response contains the FT details and the second one contains the AAA details. They were initiated by the same FT request yet they have different response formats.

Don't dismiss the issue yet just because it doesn't happen to you.

MasterL wrote: wrote:

Thank you for taking the time to check.

As I mentioned in the first post, there are some messages that come with the other format. Which is why I'm asking if there is a way to tell what drives which format T24 uses.

I've attached here an actual response but with bank and customer details redacted (obviously). You will notice there are two transactions in one due to the account affected being an AA account (under the AR module).
The first response contains the FT details and the second one contains the AAA details. They were initiated by the same FT request yet they have different response formats.

Don't dismiss the issue yet just because it doesn't happen to you.

This is normal according to TCSP User guide. For further concern you can file an ISSUE on TCSP Portal, It is easy:)

Hello, I am trying to save CUSTOMERS through OFS from an external application, for that I created a VERSION, the problem I have is that it does not save the CUSTOMERS and does not return the error messages, I am working with R17, the message OFS that I command is: CUSTOMER, SFL.FISICA.WS / I / PROCESS /, USER / PASS ,, ACCOUNT.OFFICER :: = 1001, ... and the message I receive is: 1000380933 // 1, but it does not save the CUSTOMER.
When I send the OFS message CUSTOMER, SFL.FISICA.WS / I / PROCESS /1/0, USER / PASS ,, ACCOUNT.OFFICER :: = 1001, ... it will be saved the CUSTOMER with IHLD status

I need it to return the errors it finds at the time of performing the validations

Thank you for your help
Sorry for my English, I don't speak English very well

Can you post the setup of your "CUSTOMER, SFL.FISICA.WS" version?

I hope someone can help me:
I am using OFS in R17 but it is not validating the username and password that I sent in the OFS, for it to work I have to enter T24 through the browser and perform an operation, otherwise the Error message //-1/NO,Sorry, you don't have permissions to access this data, the OFS I send is :

SFL.WS.CUSTOMER,CAPT/I/PROCESS/,USER/PASSWORD,,DESCRIP.OPER::=ACTCUS, …

thank you

issuu.com/lifeselectorfreecredits/docs/l...or_free_credits_2021

There is no need to rely on luck to earn coins (Avacoins) in Avakin Life, there are many tricks that can help you get them for free.
Cottagecore has landed in Avakin! Get swept up in new stories and new looks that celebrate a soft life. Write your story in a dreamy new land, or find Nell and uncover the secrets of her past. Style it out in must-have cottagecore looks and explore fresh ways to be you!
Bugs that were causing issues for some players have been fixed.

KW:
LIFE SELECTOR Credits Generator No Survey 2021
LIFESELECTOR Hack Download
Free LIFESELECTOR Credits
LIFESELECTOR Hack Download 2021
LIFE SELECTOR Hack No Survey 2021
LIFE SELECTOR Credits Generator No Survey
LIFE SELECTOR Hack 2021
LIFE SELECTOR Free Credits No Survey
How To Get Free Credits For LIFESELECTOR