Home
TeamSite
TeamSite, LiveSite and OpenDeploy
looking for some advice...
Andy Knipp
OK, inherited a really custom WF. Actually 36 pages of perl (printed out), which produces a job spec
that is started via $system->CreateWorkflow($wfSpec);
It has optional tasks that can be eliminated. The dynamic part of the WF can be done by using a
timeout of 0 and skipping the step. So I really do not think there is a need to keep this.
Now I am trying to decide to either pitch what I have and rewrite or make some changes.
Basically the one reason I am uncertain of is that this WF requires Editor to start (since it is a new job
functionality in 5.5.2 (6.5 rollout shortly)). Users do not like it since it is expensive to make all
users Editors.
So my questions:
anyone see WFs kicked off this way (custom menu item to perl to jobspec) rather than WFT ?
Common ? (I see maintenance as a nightmare)
If I decide to keep this can it be invoked in 6.5 by an author ? It is technically not a New Job,
CreateWorkflow uses iwjobc & I cannot find any restrictions on its use by Authors.
Tips/Pointers/RTFMs appreciated
Andy
Find more posts tagged with
Comments
There are no comments yet