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

Review Task Issue

shivali88

Hello,
I have created a MapDatasource for TSGrouppicker that I listed in the workflow instantiation screen.I got all the groups in dropdown.

In the reviewer task,I want the selected group in the dropdown to be the group the owner for the task.As of now anyone is able to review and publish the files.

The seems to be some missing patch here.
Can you please help ?

Find more posts tagged with

Comments

ISCBorisB

Hello,
I have created a MapDatasource for TSGrouppicker that I listed in the workflow instantiation screen.I got all the groups in dropdown.

In the reviewer task,I want the selected group in the dropdown to be the group the owner for the task.As of now anyone is able to review and publish the files.

The seems to be some missing patch here.
Can you please help ?

How do you set Group Task's "Shared by" Attribute?
Do you "link" it to Data Source variable?

Personally, in the case like yours I prefer to have two independent
CV's and assign DS value to "Shared By" onSave Event.

shivali88

I am not using a group Task for review but i am using a Review task.

i have used also tried using DataSource variable, and while setting them its giving all the groups, i selected the required group, but still any user or any group is able to review the Task.

i need to fetch the selected value from the custom instanciation , but how???

shivali88

I got through the Global Variable issue for custom_instantiation.
The only issue that I am facing right now is, my task owner is the one which has been selected from the Global Variable and it does show as the owner for the task ,yet anyone can approve this User task for Review.

I suppose its an issue with the roles but need a confirmation on this.

Rick Poulin

Task owner != "shared by"
As Boris said (or meant, anyway), you need to reference your variable in the task's list of reviewers (shared by), rather than in the task owner field.

ISCBorisB

I got through the Global Variable issue for custom_instantiation.
The only issue that I am facing right now is, my task owner is the one which has been selected from the Global Variable and it does show as the owner for the task ,yet anyone can approve this User task for Review.

I suppose its an issue with the roles but need a confirmation on this.

You may want to instantiate your Model in debug Mode to see WF Specs that your Model actually creates and
investigate why it behaves the way it does. If you do, note that upon Job instantiation Review Task gets
created as a Group Task. Differences exist only on the Model level. Ultimately, "Revirewers" attribute gets
rendered as Group Task "SharedBy" Collection.

IMO you have basically two options to propagate your DataSource to "Reviewrers" attribute:
   1. Include DS into Task's Available Groups and then pick this Group as the only entry into "Available Reviewers" OR
   2. Use two independent CVs for DataSource and "Available Reviewers" and assign corresponding "Reviewers" CV from DS
   CV on Model's Save Event.

I've already noted that I would personally prefer Option #2 in such case - it is IMO easier to implement and maintain
but that's just me.

Adam Stoller

I got through the Global Variable issue for custom_instantiation.
The only issue that I am facing right now is, my task owner is the one which has been selected from the Global Variable and it does show as the owner for the task ,yet anyone can approve this User task for Review.

I suppose its an issue with the roles but need a confirmation on this.

Please verify that "everyone" does not mean Master's, and/or Admin's on the particular branch -- I believe both of those are able to approve *any* task, regardless of whether they're in the shared-by list (the former definitely, the latter probably).

I've seen cases where someone complains about restrictions not working when they're testing it out with a Master user - and thus the "normal" rules don't apply.

shivali88

Thanks @ghoti
workflow was working fine, i was just testing it with admin or master's id.

Thanks a lot Smiley Happy