Hello ragesh, no worries glad I can help.
1.Iif the task is ended they can only see summary info not the Dynaform data. However, the last task remains open until the requester hits the next task link, or you create some other trigger to move it to the next step. So until this happens, the requester will be able to access the Dynaform data and the process will remain in TODO. There are other things you can do in the last step as well like create an output document or send a notification to the requester with the approved information. PM is very flexible in that regard.
2. I updated your process to remove the second provisioning task and tweaked it a bit as well. I noticed you needed to define a trigger for the @@FirstUser and assign it to the variable for Value Based Assignment in the first task otherwise the task will not return to the original requester. I did this also for the final task so it goes back to the original requester there as well. You will have to figure out Assignment Rules for the Request Approval task. I recommend "Reports To" methodology. It doesn't make sense for the requester to have to manually select who its assigned to for the next task.
For the Provisioning task it can be manual but you'll need to be mindful of the users and/or groups you assign to this task for it to be effective.
I've attached the updated process.
Also, make sure "requesters" are included in the assigned user list (either individually or as part of a user group) for the Request Submission and the Approval Information tasks otherwise an error will result.
And don't forget the data validation for the input tasks.
3. Yes, your current process could be affected if you import the updated process. You may wish to consider using a test environment then migrate over to production when fully tested.
Hope I this is helpful and I haven't said too much
Let me know if you have any further questions.