procedure ExecuteScript(script : String; entryPoint : String; language : String; param : String; wantDebug : Boolean; context : Iv3Base);

Class ICDAManager

pass a CDA Object to vbscript, javascript, COM, or OCL.

script: the name of a file containing the source, or the source itself entrypoint: the name of the procedure to run, or the coclass name for com language: the name of the language to use. will be inferred from the file extension of the script if there is one. wantDebug: when using windows script host context: the object on which the scripting will occur - either a IcdaClinicalDocument, any other CDA class, any data type, or any structured text object

Note that the script can change the contents of the object passed to it. Any handles that the host retains to contents of the objects may be invalid after it executes (except for OCL, which cannot change the object)

1. Windows Script Host

If the language is "VBScript", "JScript", or any other language string the Windows Script Host recognises, or if the file extension is (".vbs, *.js,

The script procedure is invoked with a single parameter which is an IExecuteCDAEvent event. The kernel objects therwise available in when using scripts in HL7Connect will be null except for the WScript equivalent object.

The script engine is Windows Script Host, like the rest of HL7Connect. The want debug flag is passed through to the windows script host engine for whether to invoke the debugger or not.

2. COM

If the language is "COM", the script is ignored. The entry point is the coclass name of a registered class that implements the IHL7ConnectEventHandler interface (start mode is single threaded), which will be passed a IExecuteCDAEvent.

3. OCL

if the language is "OCL" or he file extension is ".ocl", the ocl provided will be executed against the message. If any assertions in the ocl script fail, an exception will be raised containing the details


© Kestral Computing P/L 2000 - 2003. HL7Connect v2.00-063 generated on 30-Nov 2015.
Keywords: ExecuteScript