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; } } }

Unable to create a Job

syzack

Hi,

When i try to create a New job and select Author Assignment, i am getting the following error. I have logged in as master and trying to give AUTHOR ASSIGNMENT. Can anybody tell me how to fix this problem.

Invalid workflow:
ERROR: User <some_user> cannot modify workarea <some_workarea> in task Author_Work
ERROR: 02439: Operation not permitted
Job 1316 does not exist.
ERROR:02439: Operation not permitted

Find more posts tagged with

Comments

Adam Stoller

Is <some user> the author or you, the master?
Does <some user> actually have access to <some workarea>?

The workflow system will prevent a job from being instantiated if it can determine that any of the tasks would be unable to run because of permission issues (generally better to find out about it right from the start than go through many tasks/hours of process only to have the workflow bomb-out because of this problem later.

--fish
(Interwoven Senior Technical Consultant)

syzack

hi,

<some user> is actually author
for <some user> i have set the permission for the corresponding workflow.

I read in some documentation this problem(error:02439) can be solved if we change the submit task owner to iwadmin,
but i am not sure if that is the solution to this.

redirectout.pdf

Adam Stoller

If this is a submit workflow (i.e. run by clicking the Submit button) - you can usually use ... owner="__INSERT__('iw_areaowner');" ... However this presupposes that you haven't managed to make an author-only user the owner of a workarea.

You can try the same tactic in a New Job workflow - but I seem to recall that iw_areaowner didn't get set in that context (might have been changed since then - don't recall). However if that's the case, you can conjure up your own code within a <template_script><![CDATA[...]]></template_script> section of the wft that utilizes iwattrib to determine who the area owner is.

If all else fails, on Unix you could probably make iwui the owner of the submittask, or create another user within the role files (higher than Author) who has access to all the branches/workareas and make them the owner of the submittask

--fish
(Interwoven Senior Technical Consultant)