Hi ,

I am assuming in your solution your are implementing approval on the form.

 

I would recommend using Nintex task form with workflow "Assign Task" action, with the task form Approver can see initial information by connecting Task forms to list fields.

 

Additional information can be added by approver on the task form by allowing additional fields to be editable on the task form, you can use rules to hide or disable fields if needed. This can be implemented at each approval stage.

This way the implementations is easy and robust and gives same user experience

Let me know if you have questions

Ashish

---

hi @ghaiashish

Unfortunately, the solution I'm working on will not be using an 'Assign Task' action in the workflow. Instead, I will be displaying panels on the form based on the SharePoint group and sending emails once it is their turn to view and input information on the form.

Essentially, there is one panel at the top that is visible to everyone. Once that panel is submitted, it will send and email to the next group and display more fields. My trouble is, the people picker field will not default to the new user.

---

Thanks for your response ,I understand you are using responsive form,  please try following rule:

 

1. "OriginatorResponsible" can be person or group you need to configure people picker to allow groups in case of groups



2. The rule is based on 'form controls' and not SharePoint column



3. Use current user from 'context'



4. 



5. 
   
   

    

   
   
   



6. You can use any condition that suits your process - with above rule you need to fill the first group and it will change users/groups automatically as you move through the process

Regards,
Ashish

 

---