I am using a startprocessWriter plugin which is available in the shared componen

You can use a!queryProcessAnalytics() to run a task report which can then creat a link to that task but this would still require some sort of refresh button to keep fetching the data until the task is available. There's not a clean way of doing what you're asking.

I recall that is you chain the triggered process model from start to end then when you're returned to the Dashboard then any changes made by that process model will be reflected in the dashboard. If you raise the Task in a sub-process, asynchronously from the main process, then it should available when you come back to the dashboard. Because of the async nature you'd be advised to inject a short wait (say, 3 seconds) in the chained process model, after the task sub-process has been initiated, to avoid the resultant race condition.

Thanks Tim/Stewart. It does look like there is no clean way of doing this. I will pbly just show a message asking the user to check their tasks or something.

@Siddharth, do you find the startProcessWriter to be too quiet? As in, it won't report anything even if it couldn't start a process. Of course, there is a limitation of it being a Writer function, but I would prefer it to at least throw an exception (which will pop-up to end-user) in case there is something wrong and the process couldn't be started. What's your take?

@Rawich - Definitely agree with your point. There is no feedback whatsover to the end user which can be a problem.