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

Need help in Workflow --> User Task

Raymand

Hi,
I created a workflow with UserTask is one of the tasks. Task Owner of the User Task is say "B". This task is having Options "Approve" and "Reject"
My question was :
whenever workflow triggers, the user task options are enable not only to the user "B" but also to the Job Owner.
Is it the default feature in Usertask that the options would available for Job owener also along with the UserTask owner.

Need your clarification. How can we take off the UserTask permissions to the Job owner.

Thanks!

Find more posts tagged with

Comments

nipper

Is this a WFT or a WFM workflow ?

Adam Stoller

What version of TeamSite (including service pack and patch information)?

Raymand

Hi,
Thanks for your your reply. Sorry I missed the environment information

Solaris 5.8
TeamSite 6.5.0
Developed the workflow through Workflow Template (WFT).

Thanks

Adam Stoller

Hi,
Thanks for your your reply. Sorry I missed the environment information

Solaris 5.8
TeamSite 6.5.0
Developed the workflow through Workflow Template (WFT).

Thanks

This is a known issue that can usually be worked around by changing the job owner and/or creator in the WFT code to not be 'iw_user'.

Raymand

Thanks a lot Ghoti. Your replies are very helpful. You are a genius

Appreciate your help.
Thanks!

PaulW

I also have this issue TS6.7.1. I am using workflow modeller.

Is there any other way to resolve this, other then removing iw_user as the job owner? Is there a bug filed for this? or is this how it's meant to operate?

Faizi

I also have this issue TS6.7.1. I am using workflow modeller.

Is there any other way to resolve this, other then removing iw_user as the job owner? Is there a bug filed for this? or is this how it's meant to operate?

The task owner of an user task should be a particular user/group, instead of iw_user.
If it is an user task which perform approve or reject then the owner of task should be a particular user/group.
Also, User's privilege should be defined in a proper order that who is responsible for what and who can perform what.

Adam Stoller

The task owner of an user task should be a particular user/group, instead of iw_user.
If it is an user task which perform approve or reject then the owner of task should be a particular user/group.
Also, User's privilege should be defined in a proper order that who is responsible for what and who can perform what.

I think there is some confusion here - my previous post was talking about the JOB owner - not the TASK owner.

Having a task owner be set to iw_user (the person who initiated the job) may be perfectly correct in many cases - but if you're trying to prevent the person who initiated the JOB from being able to transition tasks for which they are not the owner - then you have to fiddle around with the JOB owner / creator settings (at least pre-671 -- 67x may control this more centrally via role permissions, but I'm not sure - haven't spent much time looking into it recently)