Release notes — MDMongoose 0.2
Finer permissions, enum lists you build in the app, and exports you configure as nodes. Run mdm_init once
after deploying — it upgrades the permission levels and the definitions.
Seven permission levels
Read and Modify are replaced by Nothing, Reader, Modifier, Supervisor, Manager, Governor and Admin. Modifiers edit values, Supervisors lock, Managers add, move and delete, Governors decide Owner and Steward. Every action now has a Required Level — a property of the Action node that admins can change. Security
Enum is a NodeType
Give any node the type Enum and its children become the values of a list — no SQL needed. Use it in a
NodeType as Enum(<list name>). Enum, Link and Array
Export nodes
The type_<NodeType> views are gone. Instead, an Export node (Model › Exports) publishes a branch — the
same table as the Export dialog — as a materialized view (declared in the mdm_export pipeline and
refreshed incrementally), a view (created by the app when you save) or a CSV / Excel file on the
exports volume. A new mdm_export job refreshes them after every load and golden-record refresh.
Exporting with materialized views ·
Architecture › Export
Upgrade notes
mdm_initrenames Read → Reader and Modify → Modifier, and turns the defaultusers · Modifygrant on the root intousers · Manager, so users keep adding and deleting nodes. Review your own Modify grants: groups that should add or delete nodes need Manager.- Queries on
mdm_export.type_*views must move to an Export node of type Materialized view. - The app needs
CREATE TABLEonmdm_exportfor View exports;mdm_initgrants it (or runsql/grants.sql). - Redeploy the bundle before running
mdm_init: the newmdm_exportjob and the app'sexport-jobresource come with it.