About Moving Generated Local Files to Siebel File System

This topic describes how to direct Communications Inbound Receiver to move driver-generated local files to the Siebel File System. The processing of driver events can occur on a remote Communications Inbound Processor server only if you set the RealTime input parameter for the response group to False and nonreal-time processing applies.

To enable workflows executing on a remote Communications Inbound Processor server to access driver-generated local files, Communications Inbound Receiver monitors EventFields with the following code:

LocalFileToGlobalXXX=tag|FiletoReplace 

where:

XXX must start at 0 and increase contiguously.

FiletoReplace is the file that is moved to the Siebel File System.

This code is the key to a tag-value pair with FiletoReplace replaced with the actual Siebel File System file name that is generated when the file is moved to the Siebel File System.

For example, the driver generates the following EventFields:

LocalFileToGlobal0=OriginalMsgFile|C:\OriginalMsgFile.txt

OriginalMsgFile=C:\OriginalMsgFile.txt

In this example, the local file C:\OriginalMsgFile.txt is moved to the Siebel File System. If this file receives the name ABCDEFG on the Siebel File System, then the EventFields is modified as follows before submitted to the workflow for processing:

OriginalMsgFile=ABCDEFG