> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/release-information/portal2/2024.2.md). # 2024.2 Released 2024-03-19 ### General bugs * Added missing Swedish translations. * Container - aligning and positioning the divider for vertical and horizontal containers did not work as it should. This has been fixed. * Corrected issue where clearing of listening filters was not working correctly when portlets configured to multi-level listening, ie portlet one listening to portlet two that listens to portlet three. * Corrected several issues around refreshing the user access token, and resolved problems with unauthorized issues against external systems (such as IFS). ### Portlet bugs * Data tree - Changed the behavior of the data tree so expand/select of data tree/data tree node is saved in LocalStorage and after changing page/refresh remains as the user left it last time. * Inbox - Added the possibility to configure Auto-refresh to the Inbox portlet. * KPI card - added support for onNodeSelection listening from DataTree * Record - Corrected issue where, when editing a record, quickly double-clicking the update button could result in the row being duplicated. * Record/Table - Added a loading spinner for record and table portlet when a workflow was executing, to give end-user better feedback on what is going on. * Scheduler - Corrected an issue where changing the column name in an existing Scheduler portlet caused an error. * Speedometer - Color rules did not work when using variables. This has been fixed. * Table - Corrected table column alignment issue that occurred with Chrome update 121. * Table - fixed column misalignment when using Group By function. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.novacuraflow.com/release-information/portal2/2024.2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.