Merge remote-tracking branch 'refs/remotes/origin/support-4.8' into s…

…upport-4.8

config/initial-objects/object-collection/250-object-collection-resource-all.xml

@@ -7,7 +7,13 @@
   -->
 
 <objectCollection xmlns="http://midpoint.evolveum.com/xml/ns/public/common/common-3"
-                  oid="00000000-0000-0000-0001-000000000006">
+        xmlns:q="http://prism.evolveum.com/xml/ns/public/query-3"
+        oid="00000000-0000-0000-0001-000000000006">
     <name>All resources</name>
     <type>ResourceType</type>
+    <filter>
+        <q:text>archetypeRef not matches (oid = "00000000-0000-0000-0000-000000000703")
+            and template != true and abstract != true
+        </q:text>
+    </filter>
 </objectCollection>

config/initial-objects/object-collection/251-object-collection-resource-up.xml

@@ -31,7 +31,10 @@
     </assignment>
     <type>ResourceType</type>
     <filter>
-        <q:text>operationalState/lastAvailabilityStatus = "up"</q:text>
+        <q:text>operationalState/lastAvailabilityStatus = "up"
+            and archetypeRef not matches (oid = "00000000-0000-0000-0000-000000000703")
+            and template != true and abstract != true
+        </q:text>
     </filter>
     <domain>
         <collectionRef oid="00000000-0000-0000-0001-000000000006" type="c:ObjectCollectionType"/>

docs/admin-gui/dashboards/index.adoc

@@ -10,29 +10,35 @@ doc-type: intro
 :page-wiki-metadata-modify-user: semancik
 :page-wiki-metadata-modify-date: 2019-02-01T13:16:14.087+01:00
 :page-nav-title: Dashboards
+:page-keywords: [ 'dashboards', 'dashboard' ]
+:search-alias: "dashboards"
 :page-since: "4.0"
-:page-upkeep-status: orange
-:page-upkeep-note: This was a "planned feature" test. I have quicly edited it to be a in present tense. But perhaps more edits are needed.
+:page-upkeep-status: green
+:page-upkeep-note: This was a "planned feature" test. I have quickly edited it to be a in present tense. But perhaps more edits are needed.
+
+
+== Description
 
 From the early days of midPoint there were two hardcoded dashboards: end-user home dashboard and administration dashboard.
 That was fine while midPoint was a simple IDM system.
 But now we are into identity governance, compliance, risk management support and other business-oriented aspects of identity.
 Whenever a "business" is involved there is a need for quick and clear presentation of data.
-Therefore the old hardcoded dashboards are no longer adequate for the job.
+Therefore, the old hardcoded dashboards are no longer adequate for the job.
 
 == More Dashboards
 
 When it comes to data presentation, there is no single way how to do it right.
 Security officer will be interested in certain specific aspects of data, but that aspects make little sense for a business manager.
 And then data protection officer will need yet another way to present the data.
-Therefore we need something that will be flexible and customizable.
+Therefore, we need something that will be flexible and customizable.
 Such as customizable dashboards.
 
-In midPoint universe, dashboards are first-class citizens.
+In the midPoint universe, dashboards are first-class citizens.
 Each deployment can have as many dashboards as needed, and they can contain custom "widgets" used to present interesting pieces of information.
 Simple widgets can present data from xref:/midpoint/reference/admin-gui/collections-views/[object collections], such as number of active employees, number of failed resources, suspended tasks and so.
 That is an elegant way to create _status dashboards_ showing status of important system components.
-But collections are much more powerful, especially the ability to define collection _domain_. Therefore dynamic dashboard can be used for xref:/midpoint/features/planned/compliance/[compliance] purposes.
+But collections are much more powerful, especially the ability to define collection _domain_.
+Therefore, dynamic dashboards can be used for xref:/midpoint/features/planned/compliance/[compliance] purposes.
 Data protection dashboards may be set up.
 And so on.
 
@@ -49,7 +55,7 @@ But there is one use case when dashboards and reports work together: status repo
 System administrators often like to get regular mail summary of system operation during last 24 hours.
 But we already have a dashboard functionality for the same thing.
 And here in the midPoint land we simply hate to duplicate functionality.
-Therefore there is a printable and mailable version of status dashboard.
+Therefore, there is a printable and mailable version of status dashboard.
 And that is exactly what status report is about.
 The report takes status dashboard configuration as an input.
 But instead of displaying dashboards in an interactive way it renders them in a stand-alone static way.

docs/admin-gui/dashboards/raw/file-format.adoc

@@ -0,0 +1,10 @@
+:page-visibility: hidden
+:page-upkeep-status: green
+
+[NOTE]
+====
+It makes sense to run the task for an asynchronous widget as a reoccurring task.
+Yet there is no way how to pre-configure the task before you actually "run" the report.
+Because of this, the only way is to run the report and afterwards modify the task, so it runs periodically.
+There is a work package regarding this at bug:MID-9646[]
+====

docs/admin-gui/dashboards/raw/index.adoc

@@ -0,0 +1,2 @@
+:page-visibility: hidden
+:page-upkeep-status: green

docs/admin-gui/request-access/index.adoc

@@ -14,7 +14,7 @@ The request is then routed through an xref:/midpoint/reference/cases/approval/[a
 
 However, this approach requires _end users_ to take part in the interaction.
 End users are usually not experts on RBAC and they do not have comprehensive knowledge about role design and structures used in the organization.
-Therefore, midPoint has a simplified view of xref:/midpoint/reference/admin-gui/role-catalog/[role catalog] that is suitable for end users.
+Therefore, midPoint has a simplified view of <<Role catalog>> that is suitable for end users.
 The role catalog is used to present the roles in a similar way as an e-shop presents the products.
 The roles are sorted into categories and sub-categories.
 The user may browse the role catalog and select the roles.
@@ -143,7 +143,7 @@ Menu in role catalog consists of 3 types of items also defined in configuration:
 * Collections of objects
 * Roles of teammate
 
-=== Role catalog
+=== Catalog
 
 Role catalog is defined via reference to organization tree.
 Org. tree is then used to load hierarchical menu.

docs/concepts/query/midpoint-query-language/errors/index.adoc

@@ -162,7 +162,7 @@ a| The schema defines enumerated value for this attribute. In this case the allo
 
 | Troubleshooting hints
 a| * Search for allowed values in schema definition. Schemas are described in
-xref:../../../../schema/schemadoc.adoc[SchemaDoc].
+xref:/midpoint/reference/schema/schemadoc.adoc[SchemaDoc].
 Select version according your midPoint version. +
 In this case search in schema "common/common-3" for "LockoutStatusType"
 
@@ -201,5 +201,6 @@ For polystring you need to use `origIgnoreCase` matching rule.
 
 | Troubleshooting hints
 a| * For more information about matching rules in query see xref:../introduction.adoc#_matching_rules[matching rules chapter] in introduction to Midpoint Query Language.
-* List of all matching rules is defined in xref:../../matching-rules.adoc[matching rules] page.
+* List of all matching rules is defined in xref:/midpoint/reference/concepts/matching-rules.adoc[matching rules] page.
 
+|====

docs/concepts/query/midpoint-query-language/index.adoc

@@ -30,7 +30,7 @@ image:advanced-query-select.png[Select Advanced query]
 You can test the queries directly in GUI. Starting in All users view. It is easy and straightforward.
 As an example, to select all users with given name starting with "J" just enter `givenName startsWith "J"` to search bar and click search button.
 
-Examples how to use the midPoint query in GUI can be found in xref:/midpoint/guides/gui-midpoint-query-examples[Advanced search - EXAMPLES].
+Examples how to use the midPoint query in GUI can be found in xref:/midpoint/reference/concepts/query/midpoint-query-language/query-examples[Advanced search - EXAMPLES].
 
 
 === Using in Configuration

docs/concepts/query/midpoint-query-language/introduction.adoc

@@ -142,7 +142,7 @@ The exact syntax of queries for values of different types is described in the fo
 
 | dateTime
 | `metadata/createTimestamp >= "2024-03-01"`
-| DateTime values are enclosed in quotes (') or double quotes ("). It can be compared as dates or date and time - written in format of xref:https://en.wikipedia.org/wiki/ISO_8601[ISO-8601].
+| DateTime values are enclosed in quotes (') or double quotes ("). It can be compared as dates or date and time - written in format of https://en.wikipedia.org/wiki/ISO_8601[ISO-8601].
 
 |
 | `metadata/createTimestamp >= "2024-03-01T15:30:00"`
@@ -403,7 +403,7 @@ All roles and organization units which are organization tree roots.
 
 This chapter provides information and examples of queries in midPoint Query Language, mainly used in objects while configuration of midPoint itself.
 
-Additional examples can be found in xref:/midpoint/guides/gui-midpoint-query-examples[Advanced search - EXAMPLES].
+Additional examples can be found in xref:/midpoint/reference/concepts/query/midpoint-query-language/query-examples[Advanced search - EXAMPLES].
 
 === Searching by Archetype Name