Henry Dunn can you provide more information on the sql statement to to change the work order statutes.
regarding earlier post:
We've build a custom generic batch using select/process algorithms & plug-in scripts that will allow progression of a work order, work activity (or any other WACS object with a lifecycle context) through the different statuses - subject to the BO lifecycle view rules. In the production schema you need to create the record in the initial planning state, but can then move it in one hit to the target status.
Eg if we have a work activity in planning that we want to complete, we can automatically let it progress through PENDAPPROVAL, APPROVED, ACTIVE, EXC-CMPL-EVT, COMPLETE using a simple SQL statement. This will be handled by the BO rules in the same fashion as if you did it through the front end.