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

Modify the functioning of take link in Group task

chiragjain

How can we modify the functionality of 'take' link in Group task

Find more posts tagged with

Comments

Adam Stoller

How can we modify the functionality of 'take' link in Group task

I don't think you can - (at least not in a supported manner) - but I'm curious: How do you want to modify it?

chiragjain

Hi thank you for the response.
Our requirement is that, if the author of the content is in the approvers group of the same and tries to 'take' the task... he should not be able to do so and instead a message to be displayed to him. The approvers group in our case is a TS group.
So is the need to modify the take functionality.

Even if we are able to remove the author from the approvers group dynamically, that would do. We tried this option using the TeamSite::WFTask::RemoveUser() method but the method did not return anything (no success or failure).
We also tried using the clt 'iwrmtaskuser' but in vain.

Please advise.

kaalraa

Chirag,

I suggest to carry on your query about the same issue in one particular thread. That would help all in tracking as what has already been suggested or whats the issue remaining.

Even if we are able to remove the author from the approvers group dynamically, that would do. We tried this option using the TeamSite::WFTask::RemoveUser() method but the method did not return anything (no success or failure).
We also tried using the clt 'iwrmtaskuser' but in vain.

Could you please attach you code snippet where you have written the logic to remove the user from GroupTask?

Thanks,

chiragjain

Hi,
I am not able to delete the thread, so continuing in this thread only.
I am trying to Remove user as follows:
my $next_task = new TeamSite::WFtask($nexttaskid);
my $output = $next_task->RemoveUser($user);
nexttaskid is the taskid for the group task
user is the user to be restricted.

Thanks

kaalraa

Hi,
I am not able to delete the thread, so continuing in this thread only.
I am trying to Remove user as follows:
my $next_task = new TeamSite::WFtask($nexttaskid);
my $output = $next_task->RemoveUser($user);
nexttaskid is the taskid for the group task
user is the user to be restricted.

Thanks

It is better if you could attach your code file, instead of the lines suggested to you on different threads.

Adam Stoller

Hi,
I am not able to delete the thread, so continuing in this thread only.
I am trying to Remove user as follows:
my $next_task = new TeamSite::WFtask($nexttaskid);
my $output = $next_task->RemoveUser($user);
nexttaskid is the taskid for the group task
user is the user to be restricted.

Thanks

According to the documentation RemoveUser should return 0 (FALSE) on error and non-zero (TRUE) on success. However, as I mentioned in one of these threads - if the user is a member of a group and the actual groupid is being used in the sharedby element - you cannot remove the user from the sharedby element - and unfortunately there's no "negative" sharedby element or attribute (might be a nice feature request though)

So you're back to wanting to modify the Take Task option in the Workflow GUI - which I stated is, I believe, not supported. You would probably have to find the actual command invoked by that link, make a copy of it in the appropriate place within iwhome/local/config/content_center/customer_src and then modify the copy to do what you want (assuming that it is not a binary) -- this would then classify as "semi-supported" in that you would be using the supported mechanism for modifying aspects of the TS GUI, but you would be doing so to modify something that isn't [currently] intended to be modified.

The onus is now on you to figure out how to do it.

The alternative is to expand the group into its constituent members and insert the users into the sharedby element - then you should be able to use RemoveUser to dynamically alter that list as needed. Frankly, I think this is the easier route to go - and it's certainly more supported. You just have to write the code for doing it (I believe examples have been posted from time to time in one or more of these forums - you might be able to find something to help start you on the endeavor)

chiragjain

Thanks
I too think adding users dynamically would be much easier job
Will try in this front.