I'm sure most of you don't make as many errors as I do, but I often find that a protocol running in webport will give me a Job Failure message containing all the parameters it passed to the work protocol that then failed.  It looks like the snippet at the bottom of this message.

To figure out what is going wrong the work protocol needs to be run with the exact parameters that caused it to fail, and in some cases there are dozens or even hundred of parameters (if your form is complex).

The attached component allows you to simply copy the parameter list from the Job Failure window into the 'Parameters Reported' parameter, and they will become globals, just as if they were passed parameters.  Typically this component should be at the beginning of the protocol (and disabled once you've fixed the bug ;).

Hope people find it useful.

Leo

Job Failure

Errors

line 8, The expression was trying to access the value of the data  record property 'filename' but it is undefined or could not be calculated. One  solution is to edit the PilotScript to test whether the property is defined  before using it. This is done with the expression 'filename IS  DEFINED'.
CEvaluateExpression::onProcess: Pipeline Pilot exception  rethrown
-> get prev and next (Custom Manipulator (PilotScript)) - error  during Data Record Processing phase
CProtocolStd::onProcess: Pipeline Pilot  exception rethrown
CProtocol::onProcess: Pipeline Pilot exception  rethrown
-> Get info for prev & next (Subprotocol) - error during Data  Record Processing phase
CProtocolStd::onProcess: Pipeline Pilot exception  rethrown
CProtocol::onProcess: Pipeline Pilot exception rethrown