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

Restricting access to a usertask

MamtaMander

Hi everyone,

How to make a usertask accessible to a particular user? Is there any property for the same to be set or else what need to be done for the same?

Teamsite version that I am using - 6.5

Explaination:
I am currently working on an existing workflow where in some modifications need to be done.

I am facing one problem with the workflow. There is a usertask that need to be accessible to the Approver only (where Approver is expected to Approve/Reject the work done by an editor). But this task is visible to the editor also, and editor can very much access and Approve/Reject his/her own work, which very much defeats the purpose of having an Approver in the picture.

I am new to Teamsite, can you please help me out how can I make this only accessible to the Approver?
I have set the owner of the usertask as the Approver only, but it didn't help. What setting or property I need to use for implementing this thing.

Your response will be highly appreciable.
Thanks in advance,
Mamta

Find more posts tagged with

Comments

kshitiz

Hi everyone,

How to make a usertask accessible to a particular user? Is there any property for the same to be set or else what need to be done for the same?

Teamsite version that I am using - 6.5

Explaination:
I am currently working on an existing workflow where in some modifications need to be done.

I am facing one problem with the workflow. There is a usertask that need to be accessible to the Approver only (where Approver is expected to Approve/Reject the work done by an editor). But this task is visible to the editor also, and editor can very much access and Approve/Reject his/her own work, which very much defeats the purpose of having an Approver in the picture.

I am new to Teamsite, can you please help me out how can I make this only accessible to the Approver?
I have set the owner of the usertask as the Approver only, but it didn't help. What setting or property I need to use for implementing this thing.

Your response will be highly appreciable.
Thanks in advance,
Mamta

In a usertask only that user can work on it who you have assigned as its owner.
Are the approver and editor mentioned by you above same users or different users??

MamtaMander

They are different users

kshitiz

They are different users

Are you sure you have made the task owner as approver only?

MamtaMander

Yes ofcourse.
So, setting the owner is the only thing that we do for restricting the access to a usertask?

kshitiz

Yes. That is the way to do it.
Do you have the wft file for the workflow? Can you post that?

MamtaMander

Please check below the code snippet from the wft file.
The usertask named "Approver_1", is the task which i need to make accessible only to the approver, whose username is fetched from the UI in variable, "iw_approver". And this usertask shouldn't be accessible to "iw_user".

Issue that need to be fixed: Currently usertask "Approver_1" is very much accessible to "iw_user" as well.

About the wft file:
The wft is used for deployment of a templatized page.

Code Snippet:

__INSERT__(subGet_Approver_Task_Xml("Approver_1","__TAG__('iw_approver');","Mail_Deploy_Deployer","Mail_Approver_1_Author"));

#########################################################################
# #
#Function : subGet_Approver_Task_Xml #
# #
#Description : Creates a mail task. #
# #
#Input Parameters : strTask_Name : Name of the Task #
# strOwner_Name : Name of the Owner #
# strSucc1 : Successor of the task #
# (If task is Approved) #
# strSucc2 : Successor of the task #
# (If task is Rejected) #
#Returns : approver_task_xml : A string comprising the #
#########################################################################

sub subGet_Approver_Task_Xml
{
my ($strTask_Name,$strOwner_Name,$strSucc1,$strSucc2) = @_;
my $approver_task_xml=<< EOS;

< usertask name="$strTask_Name"
owner="$strOwner_Name"
start="f"
lock="f"
description="Approve the work done by __TAG__('iw_user');"
>

< areavpath v='$strArea_VPath'/>

< successors >
< successorset description="Approve" >

< successorset description="Reject" >

< /successorset >

EOS
return $approver_task_xml;
}

Adam Stoller

Turn on workflow debugging and generate a job specification file from the workflow template - and see what the actual task definition shows as the owner of that task.

Also look at who the owner and creator of the workflow itself is.
I believe if you change one of those (I think the creator is sufficient) then the user who initiates the workflow will not have "full administrative rights" on the instantiated job.

MamtaMander

Thanks a ton dear!
Setting the owner, resolved the issue.

Adam Stoller

Thanks a ton dear!

You're welcome darling

rodigz

hi there,

Will this disable the link for usertask? Meaning the button/link will be grayed out?

thanks.

BLOB.png