glime-ai[bot]
commented
4 months ago To address your concern about the workflow table settings being reset when navigating away, it would indeed be beneficial to persist user preferences such as sorting order and rows per page. This could be achieved by storing these settings in the browser's local storage or by using cookies, so that they can be retrieved and applied whenever the user returns to the workflow table.
Regarding the addition of "Last Modified" and "Last Executed" fields to the workflow table, this is a valuable suggestion that would enhance the user's ability to track changes and executions of workflows. These fields would provide quick insights into the recency of modifications and executions, which is particularly useful during the development and testing phases.
If you are suggesting these improvements for the Elsa Workflows platform, I recommend submitting a feature request on the Elsa Workflows GitHub repository. This way, the maintainers of the project can consider your suggestions for future releases.
For now, if you are looking to implement these changes on your own instance of Elsa Workflows, you may need to customize the front-end code to persist table settings and modify the back-end to include the additional fields in the workflow table.
If you need further assistance with implementing these changes or if you have any other questions, please let me know.
This comment was generated by Glime.
Currently if I sort the workflows table by a field or change the rows per page, it is reset when navigating away. Which means an extra step every time I go back to the page after checking the workflow instance. This problem could be helped by persisting the settings and/or having extra fields on the workflow table. Last modified and last executed fields would work well.
Small changes but I think they would really improve the process of editing and testing workflows.