Two level approval

Question

i have 2 level approval , first team 'A' has to approve and after they approves it should go to team 'B' . If i'm on same page it shows "team b" form . if i comeback to the same request again after sometime it starts from "team A" form again instead of "team b" form

Mike Schmitt · Answer

Hi, 
 Please provide a bit more detail if you're hoping to find help here. Specifics regarding your current setup (interface(s) and/or process model(s)), and please be exactly clear as to A) exactly what steps you want the user(s) to experience , versus B) exactly what they are ACTUALLY seeing currently (and how EXACTLY that doesn't match your expectations) . 
 Currently in your last sentence I can't tell, for instance, whether the "it starts from Team A again" is the desired experience you're trying to implement or the current behavior (as if to say it's a bug).

Mike Schmitt · Answer

You will need to configure your process model correctly to handle the two separate approval tasks. It would be easiest to set them up as separate tasks in the process model (and I would avoid using a process with a Start Form for this, as it only increases confusion). You haven't shared any detail about your current process model's configuration yet, so for now I can't make any more specific advice than that.

Mike Schmitt · Answer

If you're using the same interface for Team A and Team B tasks (which would be fine), you'll need to pass in a parameter from the process to inform the interface which version of the task it's on. Aside from that, I don't see anything obviously wrong. 
 This should be a pretty straightforward configuration. It shouldn't be too difficult for your design team to troubleshoot this using a bit of trial and error, running some test instances in your development environment, etc.

Mike Schmitt · Answer

ZAINAB said: If we click on related action again 
 Team B would need to access it from their Task List . They should not click on the Related Action.

Mike Schmitt · Answer

Why can't Team B just open it from their Task List? The way your process is configured, they will already have the task. You can just have them open that.

Mike Schmitt · Answer

Nope, I just mean this in general. 
 Usually you would just assign that task to a Group consisting of the "Team B" members (and NOT using the "multiple task instances per assignee" option) - ALL of the members of the team will see the task in their TASK LIST , and ONE of them would open it and click "Accept" , and then complete it.

Konduru Chaitanya · Answer

Hello Fursat , My guess here is that you do not have an XOR which will evaluate the current approval status of your case/request. You might need a XOR prior your form A which will evaluate a status parameter that you pass through your related Action. Once your XOR should be deciding which form to display based on the current status. My questions, 1. If you are using the same process for both the teams then how are you handling the security. What do you mean by comeback and open. are you part of both the teams? 2. Why build the same process for both actions when you can minimize the nodes and create two different tasks for the related actions and show based on your status and group. 3. If you want to use the same process, How is team B accessing their form? Because the process that you are using will only open the form 1 if the users are clicking on the related action. If they are using it from Task list then you should not be facing this problem. If you want to keep the process same and want the users of Team B to take action you need to provide them a task list where they can see the form 2. In the assignments tab configure your team B.