Restrict task in Workflow

We have a workflow which takes files from teamsite deploy to dev and staging box. I want to restrict the task once the workflow reaches Stage so that in prodcution only spcific users can push.

Here is the task that i want to restric to ONLY teamsite Admins.

owner="__TAG__('gatekeeper');"
readonly="t"
description="Set to deploy __TAG__('task_desc2');">
__INSERT__("
");

How can i do that ?

Find more posts tagged with

Comments

singh

Not sure why the code is not fully visible Smiley Sad

Adam Stoller

We have a workflow which takes files from teamsite deploy to dev and staging box. I want to restrict the task once the workflow reaches Stage so that in prodcution only spcific users can push.

Here is the task that i want to restric to ONLY teamsite Admins.
[html]
owner="__TAG__('gatekeeper');"
readonly="t"
description="Set to deploy __TAG__('task_desc2');">
__INSERT__("
");

[/html]

How can i do that ?

It's amazing how many times we have to keep saying this - if you're posting XML / HTML code you need to surround it with

[html]...[/html]

tags (literally, with the square brackets) to prevent the code from being interpreted by the forum software.

Having said all that - if you restrict the values available for gatekeeper then you should have effectively restricted the owner of the task - if you want to make sure that the job owner cannot take over this task - you need to make sure the job creator (or job owner? - it's been a while since I've had to deal with this) is set to the same value as gatekeeper.

singh

My Apologies but being new to this forum i havent seen that html tag thing even once Smiley Happy

will take care in future .. coming to topic ..

gatekeeper is set to "tsadmin".. what i thought was that if i will change the owner of the task from the job creater to tsadmin then the values should not be visible to job creater but that didnt happened Smiley Sad

"if you restrict the values available for gatekeeper then you should have effectively restricted the owner of the task" what values we are talking about here ?

Adam Stoller

My Apologies but being new to this forum i havent seen that html tag thing even once will take care in future .. coming to topic ..

gatekeeper is set to "tsadmin".. what i thought was that if i will change the owner of the task from the job creater to tsadmin then the values should not be visible to job creater but that didnt happened

"if you restrict the values available for gatekeeper then you should have effectively restricted the owner of the task" what values we are talking about here ?

If the job owner is a master user - you cannot restrict their activities.
The job owner should be able to see all the information about the job and its tasks, but (again, it's been a while since I've had to deal with this) if you make the job creator [or owner?] explicitly be the 'gatekeeper' then [unless the job owner is a master] they shouldn't be able to take actions on tasks that they do not own.

Ultimately, however, it also comes down to social pressure / training - to tell people that they should not do something and if they continue to do those things that will be consequences (lack of employment possibly being among them)

Migrateduser

Instead of having a user task, if you make this task as a group task and pull only administrators in the shared group. This may resolve your problem(Unless you have a strict business scenario to have this task as user task.)

Rajesh

singh

Can u pls share some thing on this .. i can try to change to group task isntead of user task

Phanie

Can u pls share some thing on this .. i can try to change to group task isntead of user task

Could you check please check your Private Messages.

--
Phanie