Two user tries to open the same action

Question

Hi,
Process Default roles are assigned to "Portal Roles" instead of  "Individual user".
It was found that two users can open the same action without any warnings.
My requirement is if two users at the same time access the same action then some message should be displayed or no two users are allowed to view the same action at the same time. If one user is working on it then other user should be restricted?
How to achieve this?
Previously I was using 2004s in that senario I was getting this message
"The following action has been opened by another 1 user(s). The last access time is: Tuesday, June 30, 2009 5:40:00 AM" 
This message is not visible in CE 7.1
Do I have to configure something for that.
Regards,
Pratik

Answer 1

Hi Pratik,
Regarding your query on restricting one user if another user has already opened a task, I would say there is no simple solution to this.
We are working on similar GP Processes where a task goes to multiple users. But we do not have requirement like yours. Nevertheless I still gave a thought on your query as to how it can be achieved. I could think of using static variables in Web Dynpro code such that as soon as a task is opened (or execute method is called), a Boolean static variable is set to true. Now if any other user tries to open the task, we do a check whether the variable is true or false. If the variable is false, then show some error or the screen in disabled mode.
But this is not so good as it looks. A problem would come in a scenario where the task is opened by multiple users, with one user having control on the task. But this user closes the task without approving it. Now we are in trouble. I thought maybe what we can do is set the static variable back to false in the wdDoExit() method. But I could still see scenarios where process will not behave properly.
I would leave it up to you to give it some more thought. You might find some clue.
In your second post, you are asking "Can we provide functionality where only one user can access the action". I think this can simply be achieved by assigning a single user to the action rather than assigning a Portal Role.
Regards,
Ankur