|
From: David G. <dg...@co...> - 2003-08-15 03:36:31
|
Hello to the Great and Powerful List, I would like to use the journal to track all documents through the system. In order to do this, I'll need to do the following: 1. If I encounter an application error, I'd like to force a FAIL status into the Journal, with an appropriate error message. Is there a way to do this? 2. I'll be using pretty large documents for some of my operations, so I don't want to track it in every stage; only those stages where it will be transformed in some way. Is there anyway to know from the journal which stages track document? This will simplify things once I turn over monitoring of the system to the client. 3. Also, is the document tracked on entry to the stage or on exit from it? In other words, is tracking saving the document before any transformation is applied by the stage, or after it's transformed? 4. I would like to organize pipeline fragments to operate as subroutines that can be called by multiple stages, which I believe that I can now do with the updated CallStage functionality. I would also like to place these fragments in a separate file so that I can use them in multiple pipeline configurations. Can this be done? Thanks, David -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... |