× Discuss about OFS, Temenos Connectors, Various OFS modes, OFS with Versions, OFS performance, Logging, EB.PHANTOM, OFS.SOURCE etc…

OFS - local field assigning through validation

  • Azizfatkh
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 years 3 months ago - 12 years 3 months ago #9704 by Azizfatkh
Dear Colleagues,

I have an issue in which I can't assign value into a local field through validation routine when using OFS.

I'm importing application information from external source(e.g. .xls). My application version has a validation routine in which it takes COMI of one local field and generates another value into another local field. It's fine when such process is from higher local field into lower, but when I assign a value from let's say from 3rd local field of my application into 4th, that value doesn't get written into the record.

Thank you in advance!
Aziz
Last edit: 12 years 3 months ago by Azizfatkh.

Please Log in or Create an account to join the conversation.

  • Azizfatkh
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 years 3 months ago - 12 years 3 months ago #9705 by Azizfatkh
Moreover I created empty version with just single validation, yet it doesn't function. I am new to T24 so I assume it's a bug or some system process takes place and it clears my local field values which are higher from the local field in which validation takes place.

Did also debugging all the way till eg. R.NEW(AC.LOCAL.REF)<1,FIELD.POS>= R.VALUE
R.NEW has my dedicated value.
Last edit: 12 years 3 months ago by Azizfatkh.

Please Log in or Create an account to join the conversation.

  • Azizfatkh
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 years 3 months ago - 12 years 3 months ago #9706 by Azizfatkh
One more fact! My validation routine can assign values to any fields except ones which are higher(local fields)
Last edit: 12 years 3 months ago by Azizfatkh.

Please Log in or Create an account to join the conversation.

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • TAFj-R20 - 'unix'
More
12 years 3 months ago #9723 by jpb
Do you pass values for the local fields that should be set ?
Which sequence for the field is defined in your VERSION ?
What settings do you have in the used OFS.SOURCE, e.g. for FIELD.VAL ?
Which T24-Release do you use ?
The following user(s) said Thank You: Azizfatkh

Please Log in or Create an account to join the conversation.

  • Azizfatkh
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 years 3 months ago #9726 by Azizfatkh
Thanks for your response.

Yes I pass limited local field values through the script and then generate OFS message with routine for a version of my application. That version has validation routine to one local field which generates another value for another local field that comes after.

In general I want to populate values from one local field(imported) into others local fileds that come after in senquence, through OFS.

Just to try I made empty version with just one validation field. Lets say for account application I have validation for field LOCAL.REF:4:1 = 222 and i want to assign 2223 to LOCAL.REF:6:1

OFS.SOURCE just has settings for description, source type = globus, log file dir, log detail, in queue dir and syntax type = ofs. Field val is empty...

T-24 R08.001

Please Log in or Create an account to join the conversation.

More
12 years 2 months ago #9927 by tjondro.utomo
Replied by tjondro.utomo on topic Re: OFS - local field assigning through validation
I think, if you set OFS.SOURCE feild val = blank then t24 won't validate the ofs message. So, your VERSION validation routine is not executed.

As I know, common variable COMI will populated value during "validating" record in VERSION validation routine.

Please Log in or Create an account to join the conversation.

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • TAFj-R20 - 'unix'
More
12 years 2 months ago - 12 years 2 months ago #9929 by jpb
Sorry Aziz, I missed your reply.
Tojondro is right, try setting FIELD.VAL to YES

FIELD.VAL
Specifies whether field validation is to take place on the message. Most applications repeat field validations at record commitment and do not need this option. A few older applications rely on the input being edited as it is entered online. OFS field validation can be used to stop certain invalid data getting through to authorised records.

YES - - - - - Field validation takes place
NO /

Validation Rules
YES, NO, or null
Last edit: 12 years 2 months ago by jpb.

Please Log in or Create an account to join the conversation.

  • Azizfatkh
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 years 2 months ago #9943 by Azizfatkh
Thanks Tjondro and Jpb! Indeed, the field.val was to be YES.

Please Log in or Create an account to join the conversation.

More
8 years 2 months ago - 8 years 2 months ago #18679 by tjondro.utomo
Replied by tjondro.utomo on topic OFS - local field assigning through validation
Sounds like quite weired...
I am facing the same issue, with newer T24 Release (R.10). Obviously, I have setup FIELD.VAL=YES in F.OFS.SOURCE but my validation routine didn't executed.
Do any suggestion, what should I need to be check ?
Last edit: 8 years 2 months ago by tjondro.utomo. Reason: add another words

Please Log in or Create an account to join the conversation.

More
8 years 2 months ago #18680 by tjondro.utomo
Replied by tjondro.utomo on topic OFS - local field assigning through validation
Finally, actually validation routine being executed but there is logic to skip/return all during validate or input. This validation routine only accepted form HOT.FIELD browser.

Please Log in or Create an account to join the conversation.

Time to create page: 0.123 seconds