I have implemented Related Actions in Records. The related actions are part of m

@vipins Hi, here goes the answers to your questions:

Any idea how I can work on it so that updated information should appear after hitting submit button in User Input Task in related action ?
To the best of my knowledge, 'user has to refresh the dashboard' as stated by other users might not be true always. First you could try to implement the approach specified by Appian - 'After a user submits a related action that was started from a record view, he/she is taken back to the record view. If you want that record view to immediately reflect any data changes resulting from the related action, add an activity chain between the related action form and the data persistence nodes. If you do this, the record view refresh waits for the data to persist so that it reflects the latest changes.' at https://forum.appian.com/suite/help/7.10/Record_Design.html#Views. Combination of this and querying the data again in the View did the job for us.
If the above approach didn't work, then you could try for implementing a user friendly work around such as having a button (say 'Refresh') and educating the user thereafter about the same.

Any solution so that previous related action should not appear after the change of status?
As specified above, the chaining until the database updates has the capability to resolve the issue at times, if the desired behaviour isn't achieved with the above functionality then you could try to opt for user friendly work around. Further I would like to suggest to explore the forum re the 'hide related action' issues which could give you a good idea.

@vipins Hi, here goes the answers to your questions:

Any idea how I can work on it so that updated information should appear after hitting submit button in User Input Task in related action ?
To the best of my knowledge, 'user has to refresh the dashboard' as stated by other users might not be true always. First you could try to implement the approach specified by Appian - 'After a user submits a related action that was started from a record view, he/she is taken back to the record view. If you want that record view to immediately reflect any data changes resulting from the related action, add an activity chain between the related action form and the data persistence nodes. If you do this, the record view refresh waits for the data to persist so that it reflects the latest changes.' at https://forum.appian.com/suite/help/7.10/Record_Design.html#Views. Combination of this and querying the data again in the View did the job for us.
If the above approach didn't work, then you could try for implementing a user friendly work around such as having a button (say 'Refresh') and educating the user thereafter about the same.

Any solution so that previous related action should not appear after the change of status?
As specified above, the chaining until the database updates has the capability to resolve the issue at times, if the desired behaviour isn't achieved with the above functionality then you could try to opt for user friendly work around. Further I would like to suggest to explore the forum re the 'hide related action' issues which could give you a good idea.