Name: Logging Protocol Progress

Author: Ian Kerman

Version: 1.0

Created: 11/2011

Requirements: Pipeline Pilot 8.5 or later

O/S: Windows and Linux

Limitations: None Known

With long running protocols, it can be useful to track where the protocol is in terms of processing data. Attached is a protocol with four different methods for tracking this progress.

The simplest method is to use the PilotScript function SendMessageToClient() to update the client's status message. This will work with protocols run from both the Professional Client and Web Port. The status is updated even if you close the protocol so that that current status will be shown in the Job list of both the Client and Web Port.

The other three methods are more traditional "logging" methods in that the status is recorded somewhere. I have given options to log via a file written to the server, an e-mail sent to the user, or an item written to an RSS Feed. Because these methods are more "invasive" than the Client message, there is also an option to log only every 'nth' data record.

Did I miss a method that you find useful? Post it here!