Accessing data in another incomplete task

@mathieud It might sound bit weird and awkward and in fact I personally wouldn't prefer to so - But how about running a write to datastore smart service function under the editable components so that their values will be saved straight into database and querying the database in the other task? Ideally the values should be saved to ACPs and then PVs and finally into database, but as your usecase demands the data of an active task, the only solution might be to update the database as soon as the user fills in the fields in the Task. In this case you won't need a Save functionality you have described in your question as we are doing it at the field level and further we can make the user stay unaware about this(as he/she might be confused with Save vs Save Changes).

@mathieud It might sound bit weird and awkward and in fact I personally wouldn't prefer to so - But how about running a write to datastore smart service function under the editable components so that their values will be saved straight into database and querying the database in the other task? Ideally the values should be saved to ACPs and then PVs and finally into database, but as your usecase demands the data of an active task, the only solution might be to update the database as soon as the user fills in the fields in the Task. In this case you won't need a Save functionality you have described in your question as we are doing it at the field level and further we can make the user stay unaware about this(as he/she might be confused with Save vs Save Changes).