Merge remote-tracking branch 'origin/master'

Evolveum · Mar 15, 2023 · 2166379 · 2166379
2 parents bea3108 + 7fb4e36
commit 2166379
Show file tree

Hide file tree

Showing 16 changed files with 133 additions and 8 deletions.
diff --git a/docs/admin-gui/admin-gui-config/index.adoc b/docs/admin-gui/admin-gui-config/index.adoc
@@ -846,9 +846,10 @@ Panels applicable only for resources (detail page):
 
 WARNING: This feature is available since midPoint 4.6
 
-Panel for wizard contains same configuration structure as xref:/midpoint/reference/admin-gui/admin-gui-config/#panel-configuration[panel configuration].Only configuration for containers is supported and was tested. We can use container configuration for wizard panel which show panel with form.
+Panel for wizard contains same configuration structure as xref:/midpoint/reference/admin-gui/admin-gui-config/#panel-configuration[panel configuration]. We can use configuration for collection with definitions for columns, or we can use container configuration for wizard panel, which show panel with form.
 
 Very important attribute is _applicableForOperation_, that have to have value *_wizard_* for wizard panels.
+This enum value is available since midPoint 4.7. This value specifies that the panel will only be used in the wizard and this panel will not appear in the detail menu.
 
 Example of configuration for wizard panel, which display form with basic configuration of resource object type (visible only attributes _displayName_, _description_, _kind_, _intent_, _securityPolicyRef_ and _default_):
 
@@ -921,6 +922,10 @@ Panels applicable for resource wizard:
 | `rw-connectorConfiguration-partial`
 | Configuration after discovering that can contains suggestions for configuration attributes
 
+| Resource object types
+| `rw-types`
+| Panel display a table with all the objects available in the selected resource, manage existing or create a new one
+
 | Basic information about the object type
 | `rw-type-basic`
 | Basic configuration of resource object type
@@ -953,14 +958,27 @@ Panels applicable for resource wizard:
 | `rw-activation-validTo`
 | Definition of the circumstances for the end of the object's validity
 
+| Associations
+| `rw-associations`
+| Panel display table of associations for selected object type, you can delete or modify existing or create new association
+
 | Configuration of the association
 | `rw-association`
 | Configuration of the settings for association
 
+| Inbound mappings
+| `rw-attribute-inbounds`
+| Table of inbound mappings of selected object type
+
 | Configuration of inbound mapping
 | `rw-attribute-inbound`
 | Definition of the resource attribute from which the data wil be provisioned, and midPoint attribute which they will be provisioned to
 
+| Outbound mappings
+| `rw-attribute-outbounds`
+| Table of outbound mappings of selected object type
+
+
 | Configuration of outbound mapping
 | `rw-attribute-outbound`
 | Definition of from which attribute(s) in midPoint the data will be provisioned to which attribute on resource
@@ -969,6 +987,11 @@ Panels applicable for resource wizard:
 | `rw-attribute-limitations`
 | Configuration of the limitations, that are used to restrict some properties of an attribute
 
+| Attributes
+| `rw-attributes`
+| Attributes table of selected object type
+
+
 | Configuration of the override
 | `rw-attribute`
 | Configuration of the basic settings for override attribute
@@ -977,13 +1000,74 @@ Panels applicable for resource wizard:
 | `rw-credentials`
 | Configuration of the credentials that defines how account credentials are synchronized for current object type
 
+| Reactions
+| `rw-synchronization-reactions`
+| Table of synchronization reactions of selected object type
+
 | Main settings of reaction
 | `rw-synchronization-reaction-main`
 | Basic main configuration about the reaction
 
 | Optional reaction configuration
 | `rw-synchronization-reaction-optional`
 | Panel contains more advanced optional configuration for enrichment of the synchronization reaction
+
+| Correlation rules
+| `rw-correlationRules`
+| Table of correlation rules of selected object type
+
+| Correlators
+| `rw-correlators`
+| Table of correlators of selected correlation rule
+|===
+
+Panels applicable for role wizard:
+
+WARNING: This panels are available since midPoint 4.7
+[%autowidth]
+
+|===
+| Panel | Identifier | Description
+
+| Basic information
+| `arw-basic`
+| Basic information about your abstract role
+
+| Select application
+| `apprw-access`
+| Select application your role will grant access to
+
+| Select application roles
+| `brw-access`
+| Select application roles your role will include
+
+| Configure governance
+| `arw-governance`
+| Select governance users of your new role
+
+| Configure members
+| `arw-members`
+| Select members of your new role
+
+| Construction resource
+| `arw-construction-resource`
+| Select resource in which your role will manage access
+
+| Resource object type
+| `arw-construction-objectType`
+| Select type of object your role will modify
+
+| Association
+| `arw-construction-associations`
+| Select object(s) on resource to be associated with the user when your role is assigned
+
+| Outbound mappings
+| `arw-construction-mappings`
+| Create mappings for setting specific values when your role is assigned
+
+| Outbound mappings basic information
+| `arw-construction-mapping`
+| Basic information about outbound mapping created in panel `Outbound mappings`
 |===
 
 

diff --git a/docs/mark/index.adoc b/docs/mark/index.adoc
@@ -170,13 +170,48 @@ h|Del
 |===
 
 
-== Object Marks and Shadows
+== GUI: Object Marks and Shadows
 
 NOTE: In midPoint 4.7 object marks are only supported for shadows.
 
 === Marking Shadows in Resource Details
 
+MidPoint GUI allows manually marking shadows in resource details view
+using *Add Marks*, *Mark as Protected* actions in *Accounts* and *Entitlements*.
+
+==== Workflow screenshots
+
+.Go to Resource -> Accounts
+image::resources-accounts-00.png[]
+
+.Click on Menu for Shadow
+image::resources-accounts-01.png[]
+
+.Select Add Marks
+image::resources-accounts-02.png[]
+
+.Select Marks to be added to shadow
+image::resources-accounts-03.png[]
 
 === Marking Shadows in Simulation Results
 
+MidPoint GUI allows manually marking shadows in Simulations results -> Processed Object views.
+This is done by clicking menu icon and selecting Add Marks. Note that mark
+is applied to real shadow (not simulated result). This allows for use-cases such as running simulations
+and excluding particular shadows from real run.
+
 NOTE: In Simulations GUI mark is applied to actual underlying object
+
+==== Workflow screenshots
+
+.Click on Menu icon for shadow
+image::simulations-processed-object-01.png[]
+
+.Select Add Marks
+image::simulations-processed-object-02.png[]
+.Select Marks and click Add
+image::simulations-processed-object-04.png[]
+
+=== Listing marked shadows across resources
+
+In order to view all shadows marked by specific mark, you can navigate in midPoint GUI, to *Marks*, open specific object mark details and click on *Marked Shadows*. 
diff --git a/docs/mark/mark-shadows-01.png b/docs/mark/mark-shadows-01.png
diff --git a/docs/mark/mark-shadows-02.png b/docs/mark/mark-shadows-02.png
diff --git a/docs/mark/mark-shadows-03.png b/docs/mark/mark-shadows-03.png
diff --git a/docs/mark/mark-shadows-04.png b/docs/mark/mark-shadows-04.png
diff --git a/docs/mark/resources-accounts-00.png b/docs/mark/resources-accounts-00.png
diff --git a/docs/mark/resources-accounts-01.png b/docs/mark/resources-accounts-01.png
diff --git a/docs/mark/resources-accounts-02.png b/docs/mark/resources-accounts-02.png
diff --git a/docs/mark/resources-accounts-03.png b/docs/mark/resources-accounts-03.png
diff --git a/docs/mark/simulations-processed-object-01.png b/docs/mark/simulations-processed-object-01.png
diff --git a/docs/mark/simulations-processed-object-02.png b/docs/mark/simulations-processed-object-02.png
diff --git a/docs/mark/simulations-processed-object-03.png b/docs/mark/simulations-processed-object-03.png
diff --git a/docs/mark/simulations-processed-object-04.png b/docs/mark/simulations-processed-object-04.png
diff --git a/docs/misc/reports/configuration/index.adoc b/docs/misc/reports/configuration/index.adoc
@@ -94,7 +94,7 @@ Possible values: _csv_ and _html_.
 
 | csv
 | *CsvFileFormatType*
-| Configuration attribute for csv export.
+| Configuration attribute for CSV export.
 
 
 | html
@@ -167,14 +167,20 @@ Possible values is _all, allNonNull, minimal, nonNumeric_ and _none._
 
 | _createHeader_
 | *boolean*
-| Create header in csv output file.
+| Create header in CSV output file.
 | true
 
 
 | _encoding_
 | *string*
-| Encoding of csv file.
-| utf-8
+| Encoding of CSV file.
+Most common encodings (UTF-8, windows-125x, ISO-8859-x) are supported.
+
+See https://www.iana.org/assignments/character-sets/character-sets.xml[IANA list of charsets]
+for proper values - generally, both IANA and MIME names are supported as well as many aliases.
+Details of supported character sets depend on the concrete JDK used to run midPoint,
+but it is unlikely that your charset is not supported.
+| UTF-8
 
 
 |===

diff --git a/docs/simulation/tutorial/index.adoc b/docs/simulation/tutorial/index.adoc
@@ -429,7 +429,7 @@ For simplicity, let us use a CSV resource instead.
 
 === Step LDAP-1: Viewing the Raw LDAP Data
 
-. Copy the link:https://github.com/Evolveum/midpoint-samples/simulation/tutorial/ldap.csv[LDAP CSV file] to the directory for CSV files for this tutorial (e.g. `~/sim-tutorial`).
+. Copy the link:https://github.com/Evolveum/midpoint-samples/tree/master/samples/simulation/tutorial/ldap.csv[LDAP CSV file] to the directory for CSV files for this tutorial (e.g. `~/sim-tutorial`).
 . Check that the `filePath` in link:https://github.com/Evolveum/midpoint-samples/tree/master/samples/simulation/tutorial/resource-ldap-1.xml[LDAP definition #1] matches the location of the copied LDAP CSV file.
 . Import the LDAP definition #1 into midPoint.
 Note that the lifecycle state of the resource is `proposed`, so the whole resource definition is in the development mode.
@@ -906,4 +906,4 @@ After we are satisfied with the result, we can switch the mapping to production
 == Conclusion
 
 In this tutorial, we showed how to use new xref:/midpoint/reference/simulation/[simulations] feature to realize a simple scenario of connecting one source and one target resource.
-You can find more detailed information #TODO here#.
+You can find more detailed information #TODO here#.