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 - Editor Take Ownership

jerm

Is there a way for the Editor to Take Back Ownership after a Task is either assigned to a Group or to another User? So far we can add the Editor to the Group Task, but this way adds the task in the Editor's Todo List.. they don't like this.. Is there another way through permissions or something?

Find more posts tagged with

Comments

mgal

If the task before the grouptask is a usertask the owner of that usertask can always take back the grouptask. Please let me know if that is what you are looking for

jerm

Before the Grouptask there are two externaltask's for deploy and email notifications. Prior to this is the user task, which is assigned to the Editor (who created the Job). Once this task is assigned to the grouptask, the Editor can View>All Jobs and try to Take Ownership, but it just does nothing. Is there some permission config file we can use to allow Editors (who create Jobs) to Take Ownership of the Group Task?

nipper

If the task is not assigned, the editor can take it if he is a member of the group it is assigned to.

Taking control of a task is not given to many people. I think it is Master only.

Andy

jerm

Thanks.. We also thought about that idea, but this would mean all Editors would need to be assigned to this group, which would mean all Editors would show Tasks assigned to the Group; The business doesn't want this.

Adam Stoller

You could probably set the sharedby elements in the grouptasks to include both an OS group *and* the specific editor (job owner? area owner?) - that way the editor would not have to be a member of the OS group in order to be able to Take Ownership of the task

--fish
(Interwoven Senior Technical Consultant)

jerm

Thnx Fish.. We do have the job creator in the shareby using the <user> tag already.. but the project manager is saying they should not see this task in their todo list. I really was hoping to find a way to allow the job creator to be able to take ownership for any task in his Job, including OS Groups he/she is not a part of using permissions or something. Is there a way to do that at all?

Thanks for your help.

Edited by jerm on 07/31/03 05:14 AM (server time).