Improving assignmentHolderRelationApproach schemadoc

Evolveum · Apr 6, 2020 · 1931ca0 · 1931ca0
1 parent 0e38df9
commit 1931ca0
Showing 1 changed file with 11 additions and 3 deletions.
diff --git a/infra/schema/src/main/resources/xml/ns/public/common/common-core-3.xsd b/infra/schema/src/main/resources/xml/ns/public/common/common-core-3.xsd
@@ -15029,8 +15029,8 @@
                 <xsd:annotation>
                     <xsd:documentation>
                         <p>
-                            Configures overall assignmentRelation approach for archetypes objects. This essentially means
-                            that is allows or disables the use of "generic" assignments for archetyped objects.
+                            Configures overall assignmentRelation approach for archetyped objects (assignment holders).
+                            This essentially means that is allows or disables the use of "generic" assignments for archetyped objects.
                             If the generic assignments are allowed (open approach), the archetyped object can be a holder
                             of any assignment that targets any assignable type with any relation
                             (Note: this is still subject to authorizations).
@@ -15039,10 +15039,18 @@
                             If this property is set to "closed" then GUI will not render that button. In that case
                             only those assignments that are explicitly allowed by assignmentRelation statements are possible.
                         </p>
+                        <p>
+                            This setting controls behavior of midPoint user interface.
+                            E.g. setting the approach to "closed" will hide the button that controls generic assignment in user's the "Assignments" tab.
+                            But it will not disable similar button in the "Members" tab of the role.
+                            This setting is only about controlling uni-directional behavior of GUI.
+                            It does not constraint the entire assignment model.
+                            That will be too complex to implement (at least for now).
+                        </p>
                     </xsd:documentation>
                     <xsd:appinfo>
                         <a:since>4.1</a:since>
-                        <a:displayName>ArchetypePolicyType.assignmentRelationApproach</a:displayName>
+                        <a:displayName>ArchetypePolicyType.assignmentHolderRelationApproach</a:displayName>
                     </xsd:appinfo>
                 </xsd:annotation>
             </xsd:element>