One thing I have done in the past, for workflows not intended to be
started by people, but still monitored, is to reprogram the submit
button and hide all the fields they should not mess with. Then change
the titles to warnings. If a user tries to submit it, the submit button
errors out with another warning message.

Not very elegant, but effective. I have used this on workflows built
to be started via Driver (do-start-workflow) and SOAP. Field properties
are enforced at the browser level. If there is no browser, then they are

disclaimer: I have this in a project somewhere in my archives, what I
have here is reproduced from memory... what were we talking about???

tse7147's Profile:
View this thread: