Page tree
Skip to end of metadata
Go to start of metadata

MidPoint 4.0 and later, but still incomplete

This feature is available in midPoint 4.0 and later. While most parts of this functionality are developed and ready to be used, some functionality is still missing.

In case that you are interested in supporting development of this feature, or even when using this functionality, we strongly recommend activating midPoint Platform subscription.

Introduction

MidPoint objects are quite a social animals. They like to be grouped together. There is often need to show collections of objects, such as employees, active users, new proposed roles and so on. MidPoint has a flexible search and filter functionality that can be used for this purpose. However, those collections are used so often that they deserve a special place in the system. Those collections deserve its own definition, its own name and its own form of presentation. That is the reason why midPoint supports functionality for object collections and views.

Collections and views are two concepts that are very related, but still somehow distinct:

  • Object collection is a core midPoint concept. There is a special object type (ObjectCollectionType) that is used to define a collection. It is first-class midPoint object. Collection defines which objects belong to the collection. The plan is that collections can be used in the entire midPoint system, e.g. collections can be used in authorizations, policy rules may be applied to them and so on. Some midPoint objects can act as an implicit collections, especially archetypes and organizational units. Object collections are designed to be solid and stable. Something that midPoint policies can rely on.
  • View is a user interface concept. View specifies how a particular collection should be displayed. It defines the columns that should be displayed, default sorting, pre-defined filter properties and so on. Views are designed to be flexible, customizable. E.g. views can adjusted and overridden in admin GUI configuration.

Although collections and view have different purposes and they are based on different mechanisms, they are almost always used together.

Configuration

See Object Collections and Views Configuration page for more details.

Future

See Object Collections and Views Improvements page for the plan to further improve this functionality.

See Also


  • No labels