Object: EHL7.CommandoProcessor
FileName: EHL7.dll
PROPERTY
Name: InboundPath / OutboundPath / ErrorPath
DataType: String
Mode: Read / Write
Description:
InboundPath - The folder / path name where the processor should look for HL7 message files
OutboundPath - The folder / path name where the processor will save HL7 messages
ErrorPath - The folder / path name where the processor will place Files which do not contain HL7 messages.
These 3 properties ALL must point to different, valid, folders on the file system.
Programmers Note: It should be noted that these folders are used as references only. The author of the CommandoScript project may not use them at all.
For instance, the InboundPath property is used by the CommandoProcessor object to look for HL7 message files. However, this is true ONLY on profiles that have been created as 'Message Processors', if the profile is designated as a 'Pre-Processor' only, then this property is ignored by the processor object (as would the ErrorPath property for the same reason). See the Commando documentation for the types of message processor profiles that can be created.
Another example: The OutboundPath property is not referenced directly by the CommandoProcessor object at all except to verify that it exists and is valid. However, in the CommandoScript project embedded in the processor the OutBoundPath property is the default value used when the script author calls the oUTILITIES.SaveHL7Message() method. Likewise, the ErrorPath property is the default value used if the CommandoScript author calls the oUTILITIES.ErrorHL7Message() method. In both of these instances, however, the script author can override the default setting and redirect the output to another folder. If this is done, it falls on the script author to verify that the folder(s) they use do in fact exist (one way to do this is for them to create a custom configuration program for their script).
See Also: ShowCommandoProfile(), The Commando HL7 Workbench