MidPoint 4.2 “Maxwell” has been released. It brings major improvements for data provenance, reports or auditing. Last but not least, it brings also many improvements for user interface, archetypes, autoassignments and repository.
Considerable part of development cycle of midPoint 4.2 was dedicated for the project called midPrivacy. Its main goal was to look closer on data provenance problems, such as answering “simple” question: “Where is this assignment comming from?”. The result of midPrivacy is the new modeling language called Axiom. It is used for provenance metadata implemented in core midPoint layers.
Native reports is another major feature in midPoint 4.2. Even though midPoint has supported the reporting functionality since its very beginning, it wasn’t always straighforward to customize or even create new report. With midPoint 4.2 we believe it would be much easier, as the common midPoint mechanisms and GUI can be used for it. And there is a bonus. Reports can be configured in two directions – for exporting and importing.
Everyone using midPoint will probably appreciate introducing Linked objects. This improvement brings great flexibility to configure “chained” reactions. Using linked objects one can achieve automatically recomputing members of the role after the role changed, deleting children’s assignments to parent organization which was deleted, and so on.
Many different improvements were also made in graphical user interface. The most significant change is related to the search bar. Search bar used on list pages was replaced with simplified version with the aim of providing better user experience. There is also search configuration possible on the details form, e.g. while configuring filter for object collection.
In midPoint 4.2 audit and repository databases were decoupled. Simply said, since 4.2 there is support for various databases used for storing audit records and midPoint objects. Audit implementation works without using Hibernate framework. Another change in audit API is that audits can be searched using midPoint’s standard Query API.
For the whole list of new features and improvements see release details.