Changes

==Service Packs==

====May 9th 2024 (202405.01)====

* Updated the Icon Library to include over 20K new icons.

* Fixed an issue where sub-fields were not previously listed in archive schedule files. Added '''Status ID''' and '''Status Name''' in the user archive.

<!-- 160391 - Data Archive to include user status id -->

====April 25th 2024 (202404.03)====

<!-- 160739 - Issues identified on the Routing Page and the Alternate Pages in the French version of the website. -->

<!--161066 - Variables for metadescription and metarobots on signup pages -->

====April 18th 2024 (202404.02)====

<!-- 160419 - 312343 M2 - Cross-site Scripting (Post Authentication) - Community Development VA Finding -->

<!-- 160420 - 312343 M5 - Cross Site Request Forgery (CSRF) - Community Development VA Finding -->

====April 11th 2024 (202404.01)====

* Fixed an issue where the value of the '''Computed - Auto Number''' custom field failed to increment and save as expected when records were created using the '''Copy Profile''' feature. Following the upgrade, inclusion of a '''Computed - Auto Number''' field in the copy profile will auto increment and save.

<!-- 158456 - GoS - Dev - Value in 'Computed - Auto Number' is not Saved on Creation -->

====March 21st 2024 (202403.04)====

* Fixed an issue where the autoloader failed to associate two Level 1 objects within the same UTA after a data migration.

<!-- 159899 - (Autoloader) Association issue between two L1 objects within one UTA -->

====March 18th 2024 (202403.03)====

* Fixed an issue where users were unable to download documents from "Upload - Single File Storage" fields on list views and on "Display - Text and Variables" fields when using object syntax. Users would also see a "Scanning file for viruses" message which was not applicable.

<!-- 159950 - 'Scanning file for viruses' notification on uploaded files. -->

====March 15th 2024 (202403.02)====

* Fixed an issue where the expected visibility of Level 3 activity data (called through variable syntax) was not displaying correctly. This occurred specifically when the Level 2 Advanced Data Table custom field was mapped to Level 3 activities.

<!-- 159911 - Claim tables not visible -->