Skip to end of metadata
Go to start of metadata

Mechanisms described here are part of midPoint 3.7. However, they are considered EXPERIMENTAL and may (and probably will) change in future midPoint releases.

Sometimes it is necessary to provide users with more specific approval process and work item names than generic ones like "Adding user jack", "Assigning role captain to user jack". Such cases are, for example, when role activation is requested: it is better to tell "Activation of role captain" than "Modification of role captain". Here we show how to do that.

Each constraint can have presentation element. It contains the following:

ItemMeaningExample
messageTemplate of a message that describes the situation: to be shown e.g. in "reasons for approval" (on work item and process details), in enforcement exception or on preview changes page.Role activation was requested.
shortMessageTemplate of a short message that is to be used for the name of approval process or work item or during certification campaigns (in the future).Activation of role <xyz>.
displayOrderOrder (priority) of this message. It is used to sort messages or short messages. Specifically, name of the approval process or work item is chosen as the short message that is the first in the list of short messages - has the lowest displayOrder. 
hiddenConstraints marked as hidden are not shown. By default, this is true for "and", "or", "transition" and "situation" constraints. Presentation of hidden constraint is suppresed and presentations of embedded (child) constraints - if any - are pushed to the same level as the parent one. 
finalPresentations of embedded (child) constraints are ignored. 

This is an example:

TODO we need to add role name to the message, in order to provide meaningful information in the work item or process list.

  • No labels