How to restrict instance in swimlane to initiating User only?

Question

Hi,
In my process, using BPM 11.1.1.6, there are two swimlanes. The first swimlane (SUBMITTER) allows a user to instantiate an instance, and after some service tasks, the user moves to the next human task, in the same lane. On submission, the instance moves to the second (APPROVER) swimlane. However, if the submitter has not yet submitted the second human task (say he just saves it) then ALL other SUBMITTERS in the same SUBMIITER lane, can see his data! Apparently, this is because the instance is given the SUBMITTER Role, and not assigned to the instantiating person.
How can we restrict the instance to be assigned or restricted ONLY to the instantiating user (during its life in the SUBMITTER Lane), so that other submitters cannot see his instance?
Any help is appreciated.
Thanks!
ps: We are instantiating the task via APIs, so we have flexibility to make an API call if we can know which API call will fix this. Thx.

Answer 1

One thing you'd want to double check before continuing is to see how the predefined variable "creator" is set coming into the human task is set (not sure what this is set to when the API is used).
Assuming the "creator" (or some other string variable) is set to your initiator's userid, here are the steps to assign this person to the task in a subsequent human task.
1. Open the human task.
2. Click the "Assignment" tab.
3. Click the icon with the person in it -> click the "Edit" icon.
4. In the dropdown, select "Names and Expressions" -> make sure that the "Value-based" radio button is selected -> click the + icon on the right -> under "Identification Type" select "User" -> under "Data Type" select "By Expression" -> under "Value" click the "..." button.
5. Expand the "task" -> scroll down and select "task:creator" (or whatever string variable you have set to the userid of the person who created it in the API) -> click "Insert Into Expression" -> click "OK" -> "OK"
Hope this helps,
Dan