Jeffrey.. I am looking for options to always having to use Cache Objects/ ObjectScript, to apply data transformation exception (aka. JavaScript, etc). I know I could write a BPL (I think) to first run the DTL, then, run a basic program against the output, next. I am just trying to ascertain the limitations of the iris DTL module.
The code block action in a DTL is for writing arbitrary ObjectScript, not Javascript. It's commonly used for for data manipulation that can't be satisfied by the methods available in the FunctionSet; for example, extracting and decoding a base64-encoded PDF from an OBX:5.5 field and writing it to a file. It can also be used to interact with globals to maintain state between invocations of the DTL, or perform a database lookup, or even write values to the default device that will display in the Test tool. Very useful for debugging.
I would not recommend using it for operations that could potentially block. There's no built-in mechanism for setting a timeout so use a BPL for those cases.
Thank you Jeffrey.. I have extensive experience writing back end interface processes. I rarely unsed globals or object script on the back end basic program (Cache). IRIS/ InterOperability / BPL / DTL is fascinating to to me. But, I don't really have a working Interoperability interface process to reference (which would make understanding the nuances here much easier). I am certain there are 1000s of IRIS interfaces out there. Just wish I could see one that works. :)
.png)
No ... but what are you expecting this to do?
Jeffrey.. I am looking for options to always having to use Cache Objects/ ObjectScript, to apply data transformation exception (aka. JavaScript, etc). I know I could write a BPL (I think) to first run the DTL, then, run a basic program against the output, next. I am just trying to ascertain the limitations of the iris DTL module.
The code block action in a DTL is for writing arbitrary ObjectScript, not Javascript. It's commonly used for for data manipulation that can't be satisfied by the methods available in the FunctionSet; for example, extracting and decoding a base64-encoded PDF from an OBX:5.5 field and writing it to a file. It can also be used to interact with globals to maintain state between invocations of the DTL, or perform a database lookup, or even write values to the default device that will display in the Test tool. Very useful for debugging.
I would not recommend using it for operations that could potentially block. There's no built-in mechanism for setting a timeout so use a BPL for those cases.
Thank you Jeffrey.. I have extensive experience writing back end interface processes. I rarely unsed globals or object script on the back end basic program (Cache). IRIS/ InterOperability / BPL / DTL is fascinating to to me. But, I don't really have a working Interoperability interface process to reference (which would make understanding the nuances here much easier). I am certain there are 1000s of IRIS interfaces out there. Just wish I could see one that works. :)