Hi, How can I refresh the Record Summary View when I click on Related

The problem is that the interface returns to the view just before the task gets reassigned. This already has been discussed many times. Please use the search.

Go through the below post.
forum.appian.com/.../e-169275

@vikrantb Would you please be able to provide some information about the design pattern chosen by you? That is, how you are reassigning the tasks in the Related Action(did you make use of any plugin), how you are querying the tasks in the dashboard etc.

If you are able to provide the requested info, we can work it out as per my knowledge.

Also please do bear in mind that we can try to achieve the desired functionality by going for work around (we can trigger a process from the SAIL interface by making use of fn!startprocesswrite() and thereby refresh the tasks datasubset) just in case if the Related Action doesn't do the job.

To reiterate, the comment 'To see the updated values, user has to refresh the dashboard.' made by a practitioner in the post at above suggested link isn't true as per my knowledge because this is dependent on design.

Hi Vikrant, please try chaining all the way through the process. If you chain from the user input task through the end node, it will ensure that the data is refreshed in your record view before it returns to the summary view.

Hi All,
Thanks for inputs. Now I have created a button on Summary view and I am invoking a process on this button click. I am passing task id to the process which reassigns the tasks to loggedinuser. But now the task details are getting refreshed when I unit test the summary view in designer, but it does not refresh while viewing the summary view of a record.

@vikrantb I see that you have moved from the 'Related Action' approach to triggering of process in the interface itself. If you have moved to the later just because of the reason that data isn't refreshed, it might not be correct. Just to let you know both the approaches possess the capability to make the SAIL interface surface the latest data.

Re the problem you are experiencing currently, would you be able to attach the code snippet (at-least at a high level) of the interface so that we can actually try to see if any problem exists?

Here goes my views about the current issue. You won't see this problem, provided if you perform following steps post triggering of process:

1. Maintain the activity chaining throughout the process, that is, until the Reassign Task is completed.
2. Refresh the analytics datasubset as and when the triggering of process is completed. That is, in the 'saveInto' of Button Component and next to the process triggering step, make a fresh query to analytics and push the resultant data into the analytics datasubset. Or you may also include this operation in with() as well.

As long as the above two steps are performed, there won't be any issues as per my knowledge.

Hi,
attaching the code.

ruleForSummaryDashboard

activeTasksForRecord

reassignTask