Changelog

Every update to Primentra, 24 releases so far. Search it to find when something changed.

Search the changelog

Model import shows a preview: one line per difference, each with a tick box. New and changed items start ticked. Removals, new users and anything that grants administrator rights start unticked
A removed column and a new column can be linked as a rename. The values stay
Include security exports the roles with a permission on the selected models, entities or columns, with their exact levels. Include users adds the members and the entity approvers
An imported user is matched by e-mail. A new user gets no password and must set one at first sign-in. Passwords, API keys and API accounts never go into the file
An import that would leave no active administrator is refused as a whole
A column can be set to None for a role, next to Inherit, Read and Write. A hidden column is left out of the grid, filters, exports, the REST API, search, the row audit panel and approval diffs. A write to it is refused without naming it, and a new row is refused when a required column is hidden or read-only for the user. When a user has several roles, the highest level wins. Administrators see every column. Staging, integration views and direct SQL access are not covered
When the database is configured but does not answer, for example after a reboot before SQL Server has started, the app shows a screen with a Retry button and the administrator's e-mail. It used to show the setup wizard

The grid, export, REST API, global search and audit panel did not respect column permissions. They showed every column to anyone with read access to the entity. They now follow the column setting
When the database goes offline while Primentra runs, the server stays responsive and shows the database-unreachable screen. It used to stop answering every request, including the page itself
Merge never deletes. It used to delete columns, derived columns and entity permissions missing from the file. Merge on data rows now adds and updates only
A type change in a model import converts the stored values, as the entity form does
A type change to Decimal, DateTime or Domain reports the right number of cleared values. It used to report every value as cleared, in the import result and in the audit log
Derived columns point at the right columns on the other server
A role name or e-mail with extra spaces no longer makes the whole import fail
A file with an unknown data type is refused before anything runs, and the message names the column

Every model import writes one audit entry per changed entity
The mail component is upgraded to nodemailer 10.0.13. It closes four advisories found in 10.0.1 to 10.0.8, including a quadratic-backtracking denial of service in the address parser
A row the database refuses shows on the result screen, with a download
The preview says when there is more below, and a line at the top names each section with changes. Click it to jump there
The demo on a phone shows a note that it needs a desktop, with a link to open it anyway

See Every Change Before A Model Import