Merge branch '2024.2' into '2024.3'

antora.yml

@@ -9,6 +9,7 @@ asciidoc:
     bonitaTechnicalVersion: '10.2.0' # latest public community version
     minimalRequiredJavaVersion: '17'
     javadocVersion: '10.2'
+    keycloakDocumentationVersion: 21.1.2
     openApiUrl: 'https://api-documentation.bonitasoft.com'
     cscRootUrl: https://csc.bonitacloud.bonitasoft.com/apps/CustomerServices
     cscDownloadUrl: '{cscRootUrl}/downloads'

modules/ROOT/pages/index.adoc

@@ -49,12 +49,12 @@ xref:ROOT:runtime-installation-index.adoc[[.card-title]#Runtime installation# [.
 
 [.card.card-index]
 --
-https://community.bonitasoft.com/questions-and-answers[[.card-title]#Questions & Answers among Bonita Community# [.card-body.card-content-overflow]#pass:q[Ask your question, provide an answer]#]
+https://community.bonitasoft.com/c/q-a/6[[.card-title]#Questions & Answers among Bonita Community# [.card-body.card-content-overflow]#pass:q[Ask your question, provide an answer]#]
 --
 
 [.card.card-index]
 --
-https://community.bonitasoft.com/project[[.card-title]#Community projects# [.card-body.card-content-overflow]#pass:q[Do not start from scratch and use artifacts shared by the Community members]#]
+https://community.bonitasoft.com/c/project/5[[.card-title]#Community projects# [.card-body.card-content-overflow]#pass:q[Do not start from scratch and use artifacts shared by the Community members]#]
 --
 
 [.card.card-index]

modules/ROOT/pages/portal-removal.adoc

@@ -7,8 +7,8 @@ The removal of this part of the product implied removal, deprecation or conversi
 
 Some that can be mentioned are: +
 
-- Custom profiles are xref:ROOT:release-notes.adoc#_new_bonita_applications[converted into Living Applications], using Bonita Layout and Bonita Theme
-- xref:ROOT:release-notes.adoc#_new_bonita_applications[Process Manager profile], which has been removed and will be re-done in a future release
+- Custom profiles are xref:2021.2@ROOT:release-notes.adoc#_new_bonita_applications[converted into Living Applications], using Bonita Layout and Bonita Theme
+- xref:2021.2@ROOT:release-notes.adoc#_new_bonita_applications[Process Manager profile], which has been removed and will be re-done in a future release
 - Removal of Analytics page, which will be remade in a newer technology
 - The Living Application Layout, which has been replaced by the Bonita Layout
 - The Look & Feel files, which were used to define how the Portal will be displayed, are removed from the database. The default Look & Feel is re-packaged directly in the `server/webapps/bonita/portal-theme` folder in the Bundle

modules/api/pages/using-list-and-search-methods.adoc

@@ -51,6 +51,7 @@ sob.or();
 sob.differentFrom</b>(HumanTaskInstanceSearchDescriptor.ASSIGNEE_ID, myUser.getId());
 ----
 
+[#case_sensitivity]
 == Case sensitivity
 
 

modules/applications/pages/custom-applications-index.adoc

@@ -16,7 +16,7 @@ _Structurally_, an application is made of various xref:ROOT:project-structure.ad
 
 Bonita comes with four xref:ROOT:bonita-applications-interface-overview.adoc[Bonita Applications]. +
 
-We encourage our users to create their own *custom applications* so as to create the best user experience for their specific use-cases. +
+We encourage our users to create their own *custom applications* in order to benefit from the best user experience for their specific use-cases. +
 The application can be put together by the citizen developer or a professional developer. +
 You just need to make sure that all the elements have been developed before you can use them in the application descriptor. +
 For testing purposes, Bonita provides a layout and several themes, before you create your own.
@@ -82,7 +82,7 @@ xref:ROOT:admin-application-overview.adoc[[.card-title]#Bonita Administrator App
 
 [.card.card-index]
 --
-https://community.bonitasoft.com/project?title=&field_type_tid=All&field_project_category_tid=1341&field_certification_tid=All&sort_by=created&sort_order=DESC[[.card-title]#Community projects# [.card-body.card-content-overflow]#pass:q[Browse the Community members' applications to get inspired]#]
+https://community.bonitasoft.com/c/project/5[[.card-title]#Community projects# [.card-body.card-content-overflow]#pass:q[Browse the Community members' applications to get inspired]#]
 --
 
 [.card.card-index]

modules/applications/pages/ui-designer/languages.adoc

@@ -62,8 +62,8 @@ Instructions below assume that the language you want to add is already available
 
 Instructions below explain how to add a language to the Bonita Runtime. Steps below involve using content created by Bonitasoft community and therefore not officially supported.
 
-[discrete]
-==== Download the language files
+
+=== Download the language files
 
 . Go to http://translate.bonitasoft.org/[Bonita translation project].
 . Select the language you are interested in.
@@ -72,8 +72,7 @@ Instructions below explain how to add a language to the Bonita Runtime. Steps be
 . For each file in the folder: open it and in the *_File_* menu click on *_Download_*. Each `.po/.pot` file has a language indicator and a locale indicator. For example, the files for the Brazilian Portuguese language end with `pt_BR.po`.
 . For Subscription editions, you also need to get the files from `{bonitaVersion}/bonita-web-sp/portal` folder.
 
-[discrete]
-==== Install the files and configure java
+=== Install the files and configure java
 
 . Create a new folder depending on the situation:
  ** `[TOMCAT_HOME]/server/i18n/`

modules/bonita-overview/pages/project-structure.adoc

@@ -154,5 +154,5 @@ In the Studio, extensions are managed in a xref:managing-extension-studio.adoc[d
 [NOTE]
 ====
 Even if it is possible to manually import extensions in Bonita Studio, it is highly recommended to publish your extensions on public or private maven repositories.
-xref:process:connector-archetype-tutorial.adoc#_6__publish_the_connector_on_github_packages[Here] is an example on how to deploy an extension on GitHub packages.
+xref:process:connector-archetype-tutorial.adoc#publish_connector_to_gh_packages[Here] is an example on how to deploy an extension on GitHub packages.
 ====

modules/getting-started/pages/create-application.adoc

@@ -61,4 +61,7 @@ Confirm that the application is available :
 
 ====
 
-To learn more about Bonita components and concepts, we recommend the https://www.youtube.com/playlist?list=PLvvoQatxaHOMHRiP7hFayNXTJNdxIEiYp[Bonita Camp tutorial]. Of course the xref:ROOT:index.adoc[official documentation] is also a great place to learn more about Bonita. If you prefer to learn from examples, you can find several on the https://community.bonitasoft.com/project?title=&field_type_tid=3869[community website]. And finally, remember that you can always get help and https://community.bonitasoft.com/questions-and-answers/[ask questions of the Bonita Community].
+To learn more about Bonita components and concepts, we recommend the https://www.youtube.com/playlist?list=PLvvoQatxaHOMHRiP7hFayNXTJNdxIEiYp[Bonita Camp tutorial].
+Of course the xref:ROOT:index.adoc[official documentation] is also a great place to learn more about Bonita.
+If you prefer to learn from examples, you can find several on the https://community.bonitasoft.com/c/project/5[community website]. +
+And finally, remember that you can always get help and https://community.bonitasoft.com/c/q-a/6/[ask questions of the Bonita Community].

modules/getting-started/pages/getting-started-index.adoc

@@ -11,7 +11,7 @@ You will then be able to adapt and extend this example to fit your own needs.
 [NOTE]
 ====
 
-* If you have any problems while working through this tutorial, you can https://community.bonitasoft.com/questions-and-answers[ask for help on the Bonita Community web site] and/or open an issue on the Bonita https://bonita.atlassian.net/projects/BBPMC/issues[Community issue tracker].
+* If you have any problems while working through this tutorial, you can https://community.bonitasoft.com/c/q-a/6[ask for help on the Bonita Community web site] and/or open an issue on the Bonita https://bonita.atlassian.net/projects/BBPMC/issues[Community issue tracker].
 * This example has also been implemented and packaged to be downloaded from Bonita Studio's Welcome page (see below). +
 This can be useful to compare your creations with the already implemented example, or just to learn by watching how it has been implemented. +
 ====
@@ -21,13 +21,13 @@ To download the example from Bonita Studio:
 . Open Bonita Studio (see the prerequisite below)
 . On the Welcome page, in the _Resources_ tile at the bottom right, click on *Import the Getting Started example*
 . In the _Import .bos archive_ modal window that opens, you can see that the example will be imported in a new Bonita project by default
-. Click on the *Details* button, and learn about the main elements it contains by opening all sections of the _Archive_ column 
+. Click on the *Details* button, and learn about the main elements it contains by opening all sections of the _Archive_ column
 . Now click on the *Extensions* button, and learn about the extensions already created and packaged with the project
 (Don't worry: you will learn more about those "elements" and "extensions" while going through the tutorial)
 . Click on the "Import" button to finalize the importation operation. You get a list of the dependencies imported
 . Click on the "Deploy" button to be able to view the user interfaces in the embedded Bonita Runtime
 . Let all elements of the list checked and click on "Deploy" again
-. Click on the "Close" button to stay in Bonita Studio and start following the tutorial. 
+. Click on the "Close" button to stay in Bonita Studio and start following the tutorial.
 . You can find the whole content of the Getting Started project in the "Explorer" tab on the left. Just click on the arrow to expand it
 
 [.card-section]

modules/identity/pages/enforce-password-policy.adoc

@@ -56,7 +56,7 @@ Here are the steps to create and add a custom password validator:
           <scope>provided</scope>
       </dependency>
  </dependencies>
- 
+
 <!-- Add required additional repositories -->
 <repositories>
    <repository>
@@ -130,6 +130,6 @@ If the password complies with the criteria in the new password policy, no except
 
 [NOTE]
 ====
-The default error message shown on the default admin user list page is `Password must be at least 10 characters long containing at least 3 digits, 2 upper case characters, and 2 special characters.`. 
+The default error message shown on the default admin user list page is `Password must be at least 10 characters long containing at least 3 digits, 2 upper case characters, and 2 special characters.`.
 If you configured a custom password policy, you might need to create a custom page to change the error message.
 ====

modules/identity/pages/guest-user.adoc

@@ -17,7 +17,7 @@ This feature is deactivated by default. When you activate it, make sure you give
 For better security it is recommended when using this feature, to have a reverse proxy or a load balancer configured to prevent too many requests to the REST API to be performed, consuming all the platform resources (Distributed denial of service attacks, etc...).
 ====
 
-This feature is different from the auto-login feature that was available in the 6.x versions of Bonita BPM as it doesn't give directly access to a process form publicly. It is intended for living applications access.
+This feature is different from the auto-login feature that was available in the 6.x versions of Bonita as it doesn't give directly access to a process form publicly. It is intended for living applications access.
 
 [#prerequisite]
 == Guest profile and dedicated user account
@@ -56,7 +56,7 @@ Make sure to set the username and password of the guest user account created in
 
 . Use the xref:runtime:bonita-platform-setup.adoc[platform setup tool] again to save your changes into the database (Eg. setup.sh/.bat push). +
 Restart Bonita server.
-. If your configuration is correct you should be able to access your public application directly with the URL `http://<host>:<port>/bonita/apps/<app token>` without being logged in first. +
+. If your configuration is correct you should be able to access your public application directly with the URL `+http://<host>:<port>/bonita/apps/<app token>+` without being logged in first. +
 You are done.
 
 [NOTE,caption=UI Builder]

modules/identity/pages/ldap-synchronizer.adoc

@@ -225,7 +225,7 @@ This file defines the connection settings and specifies the account used for use
 |
 
 | serverUrl
-| Url to access the Bonita Server (http://myHost:8080)
+| Url to access the Bonita Server (`+http://myHost:8080+`)
 | no default value
 
 | applicationName
@@ -760,7 +760,7 @@ Oct 06, 2022 3:51:55 PM com.bonitasoft.ldapsynchronizer.repository.BonitaUserRep
 INFO: Using tenant id specified in configuration: 1
 Oct 06, 2022 3:51:56 PM com.bonitasoft.ldapsynchronizer.LDAPSynchronizer run
 SEVERE: Synchronization failed
-java.lang.Exception: Failed to connect to Bonita server: HTTP: url[http://localhost:8080] application[bonita] login[BonitaTechUser] password[PRESENT] 
+java.lang.Exception: Failed to connect to Bonita server: HTTP: url[http://localhost:8080] application[bonita] login[BonitaTechUser] password[PRESENT]
     at com.bonitasoft.ldapsynchronizer.repository.BonitaUserRepository.initialize(BonitaUserRepository.java:151)
     at com.bonitasoft.ldapsynchronizer.LDAPSynchronizer.run(LDAPSynchronizer.java:65)
     at com.bonitasoft.ldapsynchronizer.LDAPSynchronizer.main(LDAPSynchronizer.java:238)

modules/identity/pages/single-sign-on-with-cas.adoc

@@ -189,7 +189,7 @@ By default, logging out from Bonita Engine logs the user out of CAS. You can cha
 
 == Tenant administrator login
 
-The xref:ROOT:tenant_admin_credentials.adoc[Tenant administrator] (also kwown as the _tenant technical user_) will always be able to log in without a CAS account. To log with the tenant administrator, use the standard Bonita Runtime login page accessible on `http://<bundle host>:<port>/bonita/login.jsp`.
+The xref:ROOT:tenant_admin_credentials.adoc[Tenant administrator] (also known as the _tenant technical user_) will always be able to log in without a CAS account. To log with the tenant administrator, use the standard Bonita Runtime login page accessible on `+http://<host>:<port>/bonita/login.jsp+`.
 
 == Manage passwords
 
@@ -223,7 +223,7 @@ It allows to retrieve authentication tickets to authenticate in the Bonita Runti
 
 For detailed information about the procedure to install Restful access on your CAS SSO server, see the following links:
 
-* http://apereo.github.io/cas/4.2.x/index.html[CAS SSO RESTful API]
+* https://apereo.github.io/cas/7.0.x/index.html[CAS SSO RESTful API]
 * xref:ROOT:rest-api-overview.adoc[Bonita REST API]
 
 [NOTE]