Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: typos


That is where the idea of archetypes come comes in. Simply speaking archetype is a well-defined subtype. Project, workgroup, application, ... each of them is an archetype. For example project archetype specifies that it is in fact an organizational unit with project subtype. The archetype may also define other nuances: are projects hierarchical or flat? What color and icon should be used when displaying projects in user interface? What are the mandatory properties that each project has? What are the possible relations for the project (member, manager, owner)?

The most significant part of this functionality is user interface. It is possible to use project and application concepts even in current stable midPoint versions - and this is actually used in many midPoint projects. But it is not very convenient. The goal of the archetypes is to make is it very convenient. Archetypes should promote project, application, device or any other custom concept to the status of first-class citizens. Once archetypes are implemented the projects, applications and other custom concepts will be easy to create and maintain. They should get the same treatment as the basic built-in types.