Dan e9aae6123e * Scroll to the top on each update of a process result. ... * When displaying an error, scroll to the top of the page. * Rename a few of the filter titles to better match the titles of the table on the process instances list page. * Add error_message to the task object - so if a task is in an error state and has a message, we send it to the front end. * Handle errors on the Interstitial page - so if an error happens during execution it is diplayed, and if an error happened previously, we show it. * Return the last Errored Tasks if no READY or WAITING tasks exists when calling the Interstitial endpoint.		2023-04-22 15:38:51 -04:00
..
completed.png	* Because end events won't always have information, allow the interstitial api endpoint to return the last task, even if it doesn't have any end user information. This prevents us from just redirecting everthing back to the home page and encourages better end event messaging.	2023-04-20 15:27:32 -04:00
errored.png	* Scroll to the top on each update of a process result.	2023-04-22 15:38:51 -04:00
locked.png	* Because end events won't always have information, allow the interstitial api endpoint to return the last task, even if it doesn't have any end user information. This prevents us from just redirecting everthing back to the home page and encourages better end event messaging.	2023-04-20 15:27:32 -04:00
redirect.png	* Because end events won't always have information, allow the interstitial api endpoint to return the last task, even if it doesn't have any end user information. This prevents us from just redirecting everthing back to the home page and encourages better end event messaging.	2023-04-20 15:27:32 -04:00
waiting.png	* Because end events won't always have information, allow the interstitial api endpoint to return the last task, even if it doesn't have any end user information. This prevents us from just redirecting everthing back to the home page and encourages better end event messaging.	2023-04-20 15:27:32 -04:00