Is there a way i will be able to capture a screen shot of a UI task that user is

@siddharths You could do so but you will end in building up a complex mechanism for doing so and here goes the pseudocode:

Step - 1: Kick off a process as said by Naresh above.
Step - 2: As startprocesswrite can't return you anything, ensure that you get the process id(of the process created in Step - 1) back by doing a work around as follows:
\tStep - 2a:\tWhile you kick off a process, include a DB operation to save the process id.
\tStep - 2b:\tFetch the process id saved in Step - 2a. Make sure you put a condition (by checking the value of the process id) in the bind function so that process is kicked off only once and thereafter the process id is reused.
Step - 3: As and when you interact with a SAIL component, kick off a new process using startprocesswrite and pass the desired data to this new process. The functions that should be performed by using this new process are:
\tStep - 3a: Communicate with the process created in Step - 1 (probably you can use messaging), update the process variables present in this process. (Either you could update the process variables using messaging or you could setup a database table and query upon receiving message in the process where a form is shown in read-only mode with dynamic data.)

But if you want to surface the latest values always to the user, AFAIK it isn't possible. But you can do it by opting for a work around - configure a button or nice image on the form (Probably call it 'Refresh' or Refresh icon) and this button or image will help in loading the SAIL form and results in picking up the latest values from the process variables or the latest query results from the local variables. (refreshed because of the communication from the Step - 3).

Hope the above approach gives you some thoughts over different ways to implement as well as improvised solutions by other practitioners in subsequent comments. Please do let me know if you have any follow up questions.

@siddharths You could do so but you will end in building up a complex mechanism for doing so and here goes the pseudocode:

Step - 1: Kick off a process as said by Naresh above.
Step - 2: As startprocesswrite can't return you anything, ensure that you get the process id(of the process created in Step - 1) back by doing a work around as follows:
\tStep - 2a:\tWhile you kick off a process, include a DB operation to save the process id.
\tStep - 2b:\tFetch the process id saved in Step - 2a. Make sure you put a condition (by checking the value of the process id) in the bind function so that process is kicked off only once and thereafter the process id is reused.
Step - 3: As and when you interact with a SAIL component, kick off a new process using startprocesswrite and pass the desired data to this new process. The functions that should be performed by using this new process are:
\tStep - 3a: Communicate with the process created in Step - 1 (probably you can use messaging), update the process variables present in this process. (Either you could update the process variables using messaging or you could setup a database table and query upon receiving message in the process where a form is shown in read-only mode with dynamic data.)

But if you want to surface the latest values always to the user, AFAIK it isn't possible. But you can do it by opting for a work around - configure a button or nice image on the form (Probably call it 'Refresh' or Refresh icon) and this button or image will help in loading the SAIL form and results in picking up the latest values from the process variables or the latest query results from the local variables. (refreshed because of the communication from the Step - 3).

Hope the above approach gives you some thoughts over different ways to implement as well as improvised solutions by other practitioners in subsequent comments. Please do let me know if you have any follow up questions.