When assigning a user (principle) into a Role within a Set-up Participant task, the Team is immediately updated

[hstojan]

At Boston Scientific, when assigning a user (principle) into a Role within a Set-up Participant task, the Team is immediately updated. However, It should not be persisted until task is completed.

User may not complete task at that point.  It goes against general principles to persist information prior to completing the task.  Boston Scientific does some business rule validations at this point that could render the assignment as not allowed.  For example, the same user may not be assigned as the approver to multiple roles.

[DonSenchuk]

Because I don't have users attempting to assign themselves as approver for their own work, I haven't needed to explore restrictions in the Set Up Participants tab of the workflow activity. I thought that when setting up the Resource Pool and Role Setup tabs of the workflow activity, the members available to choose would be limited to the roles outlined.

However, even if that is not the case, using APL it should be easy to deny permission for the user to approve his own work in a subsequent task.

1. Jim is the assignee of Task 1.

2. Jim puts himself in as the approver in the Set Up Participants tab.

3. Jim completes Task 1.

4. Task changes lifecycle state to 'Under Review'.

5. Task 2 (the review task) goes to the participant(s) chosen in step 2.

5. The APL for the group/role that Jim is in does not allow him to do anything to any task at LC Under Review.

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.