nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Workflow error

Bomberoo

We created a custom work flow in Team Site 6.5 that sends an email to an approvers group, waits for approval from them, generates an index web page and then submits the approved file. When I try to run this workflow as an author it fails with the following error:

Invalid Workflow:
ERROR: User APPOFT95CAFP\TestTS cannot submit files in workarea \default\mail\CIO\WORKAREA\Work in task "Submit".
ERROR: 02439: Operation not permitted
Job 8157 does not exist.
ERROR: 02439: Operation not permitted

I was able to avoid this error by putting the user in the editor.uid file so my guess would be that one of the tasks requires you to be an editor, but I'm not sure which one. If anyone has any ideas that would be great.

Find more posts tagged with

Comments

Adam Stoller

Try re-reading that error message again - it's pretty clear about *which* task has the problem.

Authors cannot submit to staging - period (in 6.7 I imagine this will be configurable on a user-by-user basis)

Putting someone in the editor.uid file means you should have sufficient licenses for doing so - if you don't you are in violation of your license agreement with Interwove, plus you may be giving someone more rights that you want them to have.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Bomberoo

Well I had thought it was the submit task but to me not allowing authors to submit is just plain stupid so I figured that it couldn't possibly be that task. Is it possible to make tasks run as a different user? For example, could I run that submit task in the workflow using an editor account that was hard coded into the workflow?

Adam Stoller

Yes - you can explicitly set the owner of the task to an editor (or higher).
If the owner of the workarea is an editor (or higher) you can also [usually] use __TAG__('iw_areaowner');

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Bomberoo

ok thank you

Bomberoo

This worked beautifully, thanks for all the help, however it lead me on to another problem. The generate button on the DCT is tied to generating and starting a workflow. This is good if the user is creating a new form or editing an existing form, however, if they submit and the approver rejects the work we run into a problem. When they edit the files from the task and then click done, it sends the workflow back to the approver. Unfortunately, in the process of editing the files, when they generate it starts a new workflow in addition to the other workflow the file was allready a part of. My quick solution for now is to end the job after it is sent to authors so when they edit the file and regenerate it (sending it into another workflow) there won't be two workflows going for it. Is there a better way I can do this?

Thanks

Adam Stoller

This worked beautifully, thanks for all the help, however it lead me on to another problem. The generate button on the DCT is tied to generating and starting a workflow. This is good if the user is creating a new form or editing an existing form, however, if they submit and the approver rejects the work we run into a problem. When they edit the files from the task and then click done, it sends the workflow back to the approver. Unfortunately, in the process of editing the files, when they generate it starts a new workflow in addition to the other workflow the file was allready a part of. My quick solution for now is to end the job after it is sent to authors so when they edit the file and regenerate it (sending it into another workflow) there won't be two workflows going for it. Is there a better way I can do this?

Thanks

If the DCR is being edited within the context of a workflow (i.e., the DCR is attached to the workflow) and clicking the Generate button on the Edit DCR window attempts to launch a new workflow for that DCR - then that is a bug which should be reported to Interwoven -- it's only supposed to attempt to launch a workflow on generate IFF

The DCR is not already associated with a workflow, and
There is one or more workflows defined for command = tt_data in the available_templates.cfg