3: CCM_Communication

The process has this structure:

1. Loop body script, or the CCM_DoCommunication script, which relies on the CommunicateCorrespondence function of the Communication component for processing a single correspondence. The order to process the correspondences is not determined. For more information on CommunicateCorrespondence, see CommunicateCorrespondence function.
2. Surrounding loop, which ensures that the CCM_DoCommunication script is called repeatedly.

Loop body script

The CCM_DoCommunication script calls the CommunicateCorrespondence function and monitors the result:

• If a correspondence is processed successfully, the script ends.
• If no correspondence is found, the script waits five seconds, and then ends.
• If an exception marked as Handled is thrown, the script ends.
• If an exception is thrown that is not marked as Handled, the script throws an exception.

When the script ends normally, the surrounding loop immediately calls the script again. Therefore, as long as correspondences are available, they are picked up one by one without delay. If no correspondence is available, the next check is delayed for five seconds.

Surrounding loop

The surrounding loop continues indefinitely until the process receives a Stop or Cancel signal, or the CCM_DoCommunication script throws an exception. As long as the CCM_Communication process is running, correspondences are continuously processed into electronic communications.

It is safe to run multiple communication processes simultaneously, even if they process correspondences from the same run-time database.