Communication Requests

When the Communication program is entered, the Communication Request tab shows the outstanding Communication requests. These requests can either be 'Transmit' jobs or 'Receive' jobs, which is transmitted and which not, can be seen in the second column.

Fields on the Communication Request tab

All the fields on the Communication Request tab are explained below.

• Communication Type - The communication type of request that is used for the defaults.
• Transmit - This shows whether it is an outgoing or an incoming communication.
• Company - This is the company that was involved in the communication.
• e-mail - This is the e-mail address that was contacted about the communication.
• Filename - Name of the file that has to be transmitted.
• Message - Field contains a message if the communication on this request failed.
• Frequency - The frequency of the communication request.

A Communication Request

A single clicking on a communication request will display the New Request screen with the details of the communication request.

The fields on the Communication Request screen are explained underneath:

• Communication type - This determines how the communication takes place. The communication type references together with the company number to the communication type table.
• Company - This is the company number of the company that created the request.
• E-mail - After submission/receipt of the file, an e-mail will be sent to this e-mail address.
• In/Output - This determines whether it is an incoming or an outgoing request.
• Local filename - This is the filename as stored locally on our system in the 'waiting' directory or in the 'receive' directory.
• Remote directory - This is the place where remotely a file can be found or stored. It overwrites the default in the communication type.
• Remote filename - The same as directory only then the filename itself.
• Wait on local file - Send the current request after the file in this field is sent.
• Try after/before time - If communication (mostly incoming) can only take place between certain times, or one wants to prevent that the system is constantly trying to communication to a remote site a try before/after time can be filled in.
• When - In the when field, one can determine on what days communication should take place
• Day of month - What day of the month the communication should take place. Normally this is only used for incoming communication requests that go over dial-up lines.
• Days to wait before - The number of days after the last successful transfer that the program will not start the communication. For example, get a full price file every 100 days, get an update price file every 10 days.
• Message text - A message why communication has failed.

The Communication Request screen gives the possibility to:

• OK - Save the Communication request.
• Cancel - Cancel any changes made and return to the Communication Request tab.
• Delete the request - Delete the request
• View the file - View the file
• Transmit the file - Transmit the request
• Help - Enter the help system.

It is also possible to change several fields on the request.