Author can view the task assign to a Group

Hi,

I m facing an issue related with the Group Task.

I have an content author (A) which submitted the content and sent it for the review.Approvers is the group in a workflow which will review the content. Now the scenarios :

Author submits the content.
One of the Approver (B) has taken the task (didn't approved /rejected the content).
Now if Author view the task , he is able to approve / reject the content which is owned by the Approver (B).

I have checked the permissions and "Modify tasks and jobs that the users does not own." is not enabled for the Author (A).

Teamsite : 7.2
WFM : 7.1.0.

Kindly suggest.

Find more posts tagged with

Comments

Adam Stoller

In the WFT (of WFM) try changing the value of "creator" to someone other than "iw_user".

I think this does it - if not, try changing creator back to iw_user and change owner to someone else.

ssharma48

Thanks for the reply.

Since I am using WFM which creates .ipm files.Doesnot have any wft (of WFM) where I can change the creator value.

Adam Stoller

Thanks for the reply.

Since I am using WFM which creates .ipm files.Doesnot have any wft (of WFM) where I can change the creator value.

Hmm - looking over the WFM Guide it seems as if the Creator is taken care of internally - you can set the Owner in the Workflow Properties section, but I'm not sure (a) whether that will affect the actual "ownership" of the Job and/or (b) whether that will fix the problem you are having.

It appears that there is no setCreator() method (either in CSSDK or TeamSite::WFworkflow), and unless I missed it - there's nothing regarding this for iw.cfg or related to it in the UICG for the workflow_custom.xml or any of the other config files there.

Unless someone modified the Author role (you did say the user is an Author - right?) - it doesn't look like Authors should have the rights to modify a task that they don't own. Administrators have this right ("Permission Overrides": "Modify tasks and jobs that the user does not own") - but OOTB I don't believe that any role below Administrator should have this right enabled.

I think that right was put in there almost specifically because of the issue you mention - so you might want to open up a case with Support and see if they can verify whether this is a "bug" or whether we're missing something that would prevent it from happening.