× Discuss about Archiving, Close of Business, Delivery Setup, Security Management System, Global Processing etc…

Input routine at version

  • safzalhussain
  • Topic Author
  • Offline
  • Senior Member
  • Senior Member
  • Posts: 44
  • Karma: 1
  • Thank you received: 0

safzalhussain created the topic: Input routine at version

i m trying to call an input routine at version to set a value in mv set of fieds related to PRICE.

but when i m validating a record input routine is not showing any impact..
i m unable to understand what i m missing.

here are my steps :
1. write a routine (PK.V.INP.BROK.PRICE)
2. compile and catalog
3. EB.API (offcourse after resetting a tcserver)
4. call this routine at version at i.e. INPUT.ROUTINE...... PK.V.INP.BROK.PRICE
5. at version EXC.INC.RTN........ YES
6. i also set CALL REBUILD.SCREEN in input routine as well.

but still not able to see the impact of this routine.
attached is snapshot and version record

below mentioned is input routine, which is been called in the version.
* <Rating>0</Rating>
Y.PRICE = 24.5

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

  • Posts: 2845
  • Karma: 512
  • Thank you received: 647

jpb replied the topic: Input routine at version

The INPUT.ROUTINE is "invoked just prior to the final update of files at the unauthorised stage of a transaction"
--> Routines called at this stage may be used to update local files, or to provide additional checking or override processing. At this point of the transaction, all standard default and validation processing will have taken place.

I.E. there is no effect on calling REBUILD.SCREEN at this point, if you want to see the new field content during input you have to attach a AUT.NEW.CONTENT or VALIDATION.RTN.
But this way the changed values should be stored when you commit.
The following user(s) said Thank You: safzalhussain

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

Time to create page: 0.153 seconds