diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 2de28158d6..36449e19b6 100644 --- a/modules/ROOT/pages/index.adoc +++ b/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] diff --git a/modules/ROOT/pages/portal-removal.adoc b/modules/ROOT/pages/portal-removal.adoc index ddcb3c1bc1..4d9459c30c 100644 --- a/modules/ROOT/pages/portal-removal.adoc +++ b/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 diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index 2bf0f5b8b0..85ccfdf6b1 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -74,14 +74,14 @@ With the previous versions, creating a new environment required to set up the wh === Process and Case info REST API resources - *Subscription editions* -It is now possible to retrieve the tasks execution data of all open cases of a process by using the xref:api:actors-process-connectors-api.adoc#_processinfo_subscription_editions_only[`bpm/processInfo` REST API resource]. It returns counters for each flow node in the process, showing the number of flow node instances that are in executing, ready, or failed state. +It is now possible to retrieve the tasks execution data of all open cases of a process by using the xref:api:rest-api-overview.adoc[`bpm/processInfo` REST API resource]. It returns counters for each flow node in the process, showing the number of flow node instances that are in executing, ready, or failed state. -The REST API resource xref:api:cases-process-instance-api.adoc#_caseinfo_subscription_editions_only[Case info `bpm/caseInfo`] which is used for case visualization is now available in subscription editions only. +The REST API resource xref:api:rest-api-overview.adoc[Case info `bpm/caseInfo`] which is used for case visualization is now available in subscription editions only. For Community users who update to 2022.2, if you have this business need, you can create a REST API extension that leverages Bonita Engine java API to get the same functionality as in Bonita 2022.2 - Subscription version. === Human task REST API resource -It is now possible to retrieve the tasks - pending or already assigned - for which a user is a potential candidate by combining the filters `user_id` and `show_assigned_to_others` of xref:api:activities-tasks-flow-nodes-api.adoc#_search_for_a_humantask[`bpm/humanTask` REST API resource]. +It is now possible to retrieve the tasks - pending or already assigned - for which a user is a potential candidate by combining the filters `user_id` and `show_assigned_to_others` of xref:api:rest-api-overview.adoc[`bpm/humanTask` REST API resource]. == Technical updates @@ -140,7 +140,7 @@ The detailed list is available in the "What’s new in Bonita 2022.1" page, in t ==== Fixes in Bonita Studio including Bonita UI Designer -* STUDIO-4515 - NPE generated during project migration +* STUDIO-4515 - NPE generated during project migration === Fixes in Bonita 2022.2-u9 (2024-04-18) @@ -188,7 +188,7 @@ _We would like to thank both Tomas Castro Rojas and Mohammad A’mir for reporti * STUDIO-4483 - BonitaMarketplace: NPE generated in the log file when the HTTP response's entity-body is empty * STUDIO-4490 - Exception at runtime: the Call activity is wrong in the process-design.xml generated * UID-723 - Update to 7.15: Web browser's disk and memory caches break the product and custom pages -* CVE-50 - Removing from the packaged maven repository an old vulnerable log4j library which wasn't executed +* CVE-50 - Removing from the packaged maven repository an old vulnerable log4j library which wasn't executed ==== Fixes in Bonita Runtime including Bonita Applications @@ -306,7 +306,7 @@ Please note that, due to an https://github.com/hazelcast/hazelcast/issues/24688[ * RUNTIME-1477 - [admin-case-details] improve display of Started by information * RUNTIME-1478 - [admin-task-details] improve display of Executed by information * RUNTIME-1485 - Fix [SSO] Allow the usage of any claim of the ID token for the OIDC adapter to fetch the username value from -* RUNTIME-1486 - Fix [Rest API Extension][Java] Archetype generating bad InputStream management code +* RUNTIME-1486 - Fix [Rest API Extension][Java] Archetype generating bad InputStream management code * RUNTIME-1489 - [Security] Version update of several dependencies for 2022.2-u1 (7.15.1) * RUNTIME-1527 - Fix Platform API resources access should not need an API session along with the platform session * RUNTIME-1545 - Fix [SSO] OIDC auto detect bearer only option breaking json requests diff --git a/modules/api/pages/using-list-and-search-methods.adoc b/modules/api/pages/using-list-and-search-methods.adoc index db6c7edbe5..d5187e0972 100644 --- a/modules/api/pages/using-list-and-search-methods.adoc +++ b/modules/api/pages/using-list-and-search-methods.adoc @@ -51,7 +51,7 @@ sob.or(); sob.differentFrom(HumanTaskInstanceSearchDescriptor.ASSIGNEE_ID, myUser.getId()); ---- - +[#case_sensitivity] == Case sensitivity diff --git a/modules/applications/pages/custom-applications-index.adoc b/modules/applications/pages/custom-applications-index.adoc index 5173f7600c..5a7a278dce 100644 --- a/modules/applications/pages/custom-applications-index.adoc +++ b/modules/applications/pages/custom-applications-index.adoc @@ -10,13 +10,13 @@ It is created and operated within Bonita Platform: created with Bonita Studio an Its purpose is to display and structure the right information and provide the right controls at the right time to the profiles, so they can efficiently perform their tasks. + _Graphically_, an application is made of a navigation menu and a set of pages. In some of the pages, some controls, like -"Validate" or "Reject" buttons- are directly linked to processes and execute tasks in the background. Others -like "New request" or "Add additional information"- open forms that, once submitted start a new process instance, or execute a task. + -Bonita allows you to create xref:ROOT:bonita-purpose.adoc#_what_can_i_do_with_bonita[different types of applications]. + +Bonita allows you to create xref:ROOT:bonita-purpose.adoc[different types of applications]. + _Structurally_, an application is made of various xref:ROOT:project-structure.adoc[elements]. Some are directly linked to the application (name, token, navigation), others are referenced (layout, pages, profiles, theme). They are all assembled in the application descriptor. + 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* to create 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] diff --git a/modules/applications/pages/languages.adoc b/modules/applications/pages/languages.adoc index 0de5ef6a6a..b40b5938c9 100644 --- a/modules/applications/pages/languages.adoc +++ b/modules/applications/pages/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/` diff --git a/modules/applications/pages/multi-language-pages.adoc b/modules/applications/pages/multi-language-pages.adoc index eed23fd9d6..f43dc34b8a 100644 --- a/modules/applications/pages/multi-language-pages.adoc +++ b/modules/applications/pages/multi-language-pages.adoc @@ -41,7 +41,7 @@ To use a localization asset, replace the default `localization.json` file with a ... ---- -The code that specifies a language in `localization.json` must be the same as the code in the `.po` files used to xref:ROOT:languages.adoc#_add_a_new_language[add a new language]. +The code that specifies a language in `localization.json` must be the same as the code in the `.po` files used to xref:ROOT:languages.adoc#add-new-language[add a new language]. By default, translation keys are in en-US english texts. If you want to have custom texts, you can create a new translation section for en-US and handle it as a new translation. This option allows to freely change texts by avoiding duplicates on other language sections. @@ -79,7 +79,7 @@ Now translate the text outside of Bonita, in any suitable translation editor, or === Add a new language -Before you can view a page in a language, that language must be supported for Bonita web applications. French is one of the default languages supported, so you just need to add support for Russian. To do this, xref:ROOT:languages.adoc#_add_a_new_language[add Russian from the Community translations to your Bonita Runtime]. Then restart your Bonita Studio, start the Bonita Runtime, and change the language to Russian to check that it is available. +Before you can view a page in a language, that language must be supported for Bonita web applications. French is one of the default languages supported, so you just need to add support for Russian. To do this, xref:ROOT:languages.adoc#add-new-language[add Russian from the Community translations to your Bonita Runtime]. Then restart your Bonita Studio, start the Bonita Runtime, and change the language to Russian to check that it is available. === Add a localization asset to the page diff --git a/modules/bonita-overview/pages/project-structure.adoc b/modules/bonita-overview/pages/project-structure.adoc index b3990fb1cf..975152c2cb 100644 --- a/modules/bonita-overview/pages/project-structure.adoc +++ b/modules/bonita-overview/pages/project-structure.adoc @@ -12,7 +12,7 @@ image:bonita-project-elements.png[] [NOTE] ==== -Using all the concepts in a projet allows to take the full advantage of the Bonita platform. +Using all the concepts in a project allows to take the full advantage of the Bonita platform. However, it is not required to use all the concepts to create a valid Bonita Automation project. ==== @@ -35,7 +35,7 @@ However, it is not required to use all the concepts to create a valid Bonita Aut |xref:process:actor-filtering.adoc[Actor filter] |Filters users that can access a human task in a process -|A couple are provided in the Marketplace and you can create custom actor filters +|A couple is provided in the Marketplace and you can create custom actor filters |Studio or xref:ROOT:actor-filter-archetype.adoc[Dedicated SDK] (custom actor filters) |- @@ -57,7 +57,7 @@ However, it is not required to use all the concepts to create a valid Bonita Aut |Structure of the business data used by your processes |Create |Studio -|External data base w/ provided connector +|External database w/ provided connector |=== @@ -111,7 +111,7 @@ Bonita Automation project can be extended by creating custom components. These a Some extensions are used to add elements to those provided while others are used to enforce the Bonita platform possibilities. -Extensions can be developed outside of the Studio with your favorite IDE. +Extensions can be developed outside the Studio with your favorite IDE. [cols="1,1,1"] |=== @@ -144,5 +144,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. ==== diff --git a/modules/getting-started/pages/create-application.adoc b/modules/getting-started/pages/create-application.adoc index 9cc236eb90..41904b3d10 100644 --- a/modules/getting-started/pages/create-application.adoc +++ b/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]. diff --git a/modules/getting-started/pages/getting-started-index.adoc b/modules/getting-started/pages/getting-started-index.adoc index 327184c65b..20f1e74b9d 100644 --- a/modules/getting-started/pages/getting-started-index.adoc +++ b/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] diff --git a/modules/identity/pages/enforce-password-policy.adoc b/modules/identity/pages/enforce-password-policy.adoc index 725ea3e205..5661016edb 100644 --- a/modules/identity/pages/enforce-password-policy.adoc +++ b/modules/identity/pages/enforce-password-policy.adoc @@ -65,9 +65,9 @@ have to follow this given procedure (example given for the x.y.z version): * retrieve the console-common-x.y.z.jar from a Bonita distribution or live instance (in the bonita.war or in the exploded war) -* retrieve poms from the github repository - ** bonita-console: https://github.com/bonitasoft/bonita-web/blob/x.y.z/pom.xml - ** console-common: https://github.com/bonitasoft/bonita-web/blob/x.y.z/common/pom.xml +* retrieve poms from the GitHub repository + ** bonita-console: `+https://github.com/bonitasoft/bonita-web/blob/x.y.z/pom.xml+` + ** console-common: `+https://github.com/bonitasoft/bonita-web/blob/x.y.z/common/pom.xml+` * manually put the jars and pom in your local repository or deploy them into your repository manager ** bonita-console pom.xml file in /org/bonitasoft/console/bonita-console/x.y.z @@ -127,6 +127,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. ==== diff --git a/modules/identity/pages/guest-user.adoc b/modules/identity/pages/guest-user.adoc index e356e2812c..f08423e179 100644 --- a/modules/identity/pages/guest-user.adoc +++ b/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://:/bonita/apps/` without being logged in first. + +. If your configuration is correct you should be able to access your public application directly with the URL `+http://:/bonita/apps/+` without being logged in first. + You are done. [NOTE.bonitacloud,caption=Bonita Cloud] diff --git a/modules/identity/pages/ldap-synchronizer.adoc b/modules/identity/pages/ldap-synchronizer.adoc index 5a8a51f26c..676851df16 100644 --- a/modules/identity/pages/ldap-synchronizer.adoc +++ b/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 @@ -759,7 +759,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) diff --git a/modules/identity/pages/single-sign-on-with-cas.adoc b/modules/identity/pages/single-sign-on-with-cas.adoc index ce90064721..bc132b0c6d 100644 --- a/modules/identity/pages/single-sign-on-with-cas.adoc +++ b/modules/identity/pages/single-sign-on-with-cas.adoc @@ -180,7 +180,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://:/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://:/bonita/login.jsp+`. == Manage passwords @@ -214,7 +214,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] diff --git a/modules/identity/pages/single-sign-on-with-oidc.adoc b/modules/identity/pages/single-sign-on-with-oidc.adoc index 31b99bf833..89fbd1eba4 100644 --- a/modules/identity/pages/single-sign-on-with-oidc.adoc +++ b/modules/identity/pages/single-sign-on-with-oidc.adoc @@ -237,11 +237,11 @@ NOTE: Activating this option means any user authorized by the IdP to access Boni [NOTE] ==== -More configuration options can be found in https://www.keycloak.org/docs/18.0/securing_apps/#_java_adapter_config[Keycloak official documentation] +More configuration options can be found in https://www.keycloak.org/docs/21.1.2/securing_apps/#_java_adapter_config[Keycloak official documentation] ==== -Once your Identity Provider is correctly configured (see the section _Configure the Identity Provider_), try to access any Bonita Application page, an app page or a form URL (or just `http://:/bonita[?tenant=]`) and make sure that you are redirected to your Identity Provider to log in (unless you are already logged in). + -Note that if you try to access `http://:/bonita/login.jsp`, then you won't be redirected to the OIDC provider's authentication end point since this page needs to be accessible for the tenant administrator (or another user if you set the property `oidc.auth.standard.allowed` to `true`) to be able to log in without an account on the Identity Provider. +Once your Identity Provider is correctly configured (see the section _Configure the Identity Provider_), try to access any Bonita Application page, an app page or a form URL (or just `+http://:/bonita[?tenant=]+`) and make sure that you are redirected to your Identity Provider to log in (unless you are already logged in). + +Note that if you try to access `+http://:/bonita/login.jsp+`, then you won't be redirected to the OIDC provider's authentication end point since this page needs to be accessible for the tenant administrator (or another user if you set the property `oidc.auth.standard.allowed` to `true`) to be able to log in without an account on the Identity Provider. [WARNING] ==== @@ -273,7 +273,7 @@ In addition, you can add some log to diagnose received headers in ` prefix="localhost_access_log" suffix=".txt" pattern="Proto %{X-Forwarded-Proto}i Host %{X-Forwarded-Host}i For %{X-Forwarded-For}i By %{X-Forwarded-By}i %h %l %u %t "%r" %s %b"/> ---- -More information can be found in Tomcat offical documentation https://tomcat.apache.org/tomcat-9.0-doc/config/valve.html#Remote_IP_Valve[Remote_IP_Valve] and https://tomcat.apache.org/tomcat-9.0-doc/config/valve.html#Access_Log_Valve[Access_Log_Valve] +More information can be found in Tomcat official documentation https://tomcat.apache.org/tomcat-9.0-doc/config/valve.html#Remote_IP_Valve[Remote_IP_Valve] and https://tomcat.apache.org/tomcat-9.0-doc/config/valve.html#Access_Log_Valve[Access_Log_Valve] ==== == Configure the Identity Provider diff --git a/modules/identity/pages/single-sign-on-with-saml.adoc b/modules/identity/pages/single-sign-on-with-saml.adoc index 8e9698903f..3e64a6dd6c 100644 --- a/modules/identity/pages/single-sign-on-with-saml.adoc +++ b/modules/identity/pages/single-sign-on-with-saml.adoc @@ -194,9 +194,9 @@ with the certificate provided by the IdP. The policy can either be FROM_NAME_ID or FROM_ATTRIBUTE (in that case you need to specify the name of the attribute to use --only one attribute can be specified--). There can only be one mapping (meaning that the same policy is used for all the user accounts). ** You may also need to change the requestBinding and/or responseBinding from POST to REDIRECT depending on your IdP configuration. ** The url binding to your IdP also needs to be defined by replacing the following string: - *** http://idp.saml.binding.url.to.change + *** `+http://idp.saml.binding.url.to.change+` ** If you want to use the SAML logout feature, the URL of your Bonita server needs to be defined by replacing the following string (otherwise, you can remove this attribute): - *** http://bonita.server.url.to.change + *** `+http://bonita.server.url.to.change+` [NOTE] @@ -225,7 +225,7 @@ If your IdP responses are not signed, you can remove the Keys node from the IDP [NOTE] ==== -More configuration options can be found in https://www.keycloak.org/docs/latest/securing_apps/index.html#_saml-general-config[Keycloak official documentation] +More configuration options can be found in https://www.keycloak.org/docs/21.1.2/securing_apps/index.html#_saml-general-config[Keycloak official documentation] ==== [source,xml] @@ -272,8 +272,8 @@ More configuration options can be found in https://www.keycloak.org/docs/latest/ ---- -Once your Identity Provider is corectly configured (see the section _Configure the Identity Provider_), try to access any Bonita Application page, an app page or a form URL (or just `http://:/bonita[?tenant=]`) and make sure that you are redirected to your Identity Provider to log in (unless you are already logged in). + -Note that if you try to access `http://:/bonita/login.jsp`, then you won't be redirected as this page still needs to be accessible in order for the tenant administrator (or another user if you set the property `saml.auth.standard.allowed` to true) to be able to log in without an account on the Identity Provider. +Once your Identity Provider is corectly configured (see the section _Configure the Identity Provider_), try to access any Bonita Application page, an app page or a form URL (or just `+http://:/bonita[?tenant=]+`) and make sure that you are redirected to your Identity Provider to log in (unless you are already logged in). + +Note that if you try to access `+http://:/bonita/login.jsp+`, then you won't be redirected as this page still needs to be accessible in order for the tenant administrator (or another user if you set the property `saml.auth.standard.allowed` to true) to be able to log in without an account on the Identity Provider. [WARNING] ==== diff --git a/modules/identity/pages/user-authentication-overview.adoc b/modules/identity/pages/user-authentication-overview.adoc index 0e139be807..3f9f00e789 100644 --- a/modules/identity/pages/user-authentication-overview.adoc +++ b/modules/identity/pages/user-authentication-overview.adoc @@ -64,23 +64,23 @@ implementation of this method does nothing (the subsequent engine login is enoug will then call engine API https://javadoc.bonitasoft.com/api/{javadocVersion}/org/bonitasoft/engine/api/LoginAPI.html#login(java.lang.String,%20java.lang.String)[LoginAPI.login()] . At this point, operations are processed on Bonita Engine side. Engine (see https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-process-engine/src/main/java/org/bonitasoft/engine/api/impl/LoginAPIImpl.java[LoginAPIImpl] class) verifies that the username and password are not empty. A verification is also done to validate that the tenant is enabled (use provided tenant id or default one if not provided). Then https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-process-engine/src/main/java/org/bonitasoft/engine/api/impl/LoginAPIImpl.java[LoginAPIImpl] -will call https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/bonita-login-api/src/main/java/org/bonitasoft/engine/core/login/LoginService.java[LoginService] -(one implementation available: https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/bonita-login-api-impl/src/main/java/org/bonitasoft/engine/core/login/SecuredLoginServiceImpl.java[SecuredLoginService]). -. SecuredLoginService calls https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/bonita-authentication-api/src/main/java/org/bonitasoft/engine/authentication/GenericAuthenticationService.java[GenericAuthenticationService]. -The default implementation is: https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/bonita-authentication-api-impl/src/main/java/org/bonitasoft/engine/authentication/impl/AuthenticationServiceImpl.java[AuthenticationServiceImpl]. -. The https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/bonita-authentication-api-impl/src/main/java/org/bonitasoft/engine/authentication/impl/AuthenticationServiceImpl.java[AuthenticationServiceImpl] +will call https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/src/main/java/org/bonitasoft/engine/core/login/LoginService.java[LoginService] +(one implementation available: https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/src/main/java/org/bonitasoft/engine/core/login/SecuredLoginServiceImpl.java[SecuredLoginService]). +. SecuredLoginService calls https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/src/main/java/org/bonitasoft/engine/authentication/GenericAuthenticationService.java[GenericAuthenticationService]. +The default implementation is: https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/src/main/java/org/bonitasoft/engine/authentication/impl/AuthenticationServiceImpl.java[AuthenticationServiceImpl]. +. The https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/src/main/java/org/bonitasoft/engine/authentication/impl/AuthenticationServiceImpl.java[AuthenticationServiceImpl] verifies that your username and password are valid. -. After call of the https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/bonita-authentication-api/src/main/java/org/bonitasoft/engine/authentication/GenericAuthenticationService.java[GenericAuthenticationService], -https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/bonita-login-api-impl/src/main/java/org/bonitasoft/engine/core/login/SecuredLoginServiceImpl.java[SecuredLoginServiceImpl] -performs an extra check to verify that the provided username exists in the Bonita database (https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/bonita-login-api-impl/src/main/java/org/bonitasoft/engine/core/login/SecuredLoginServiceImpl.java[SecuredLoginServiceImpl] -does not trust https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/bonita-authentication-api-impl/src/main/java/org/bonitasoft/engine/authentication/impl/AuthenticationServiceImpl.java[AuthenticationServiceImpl]). +. After call of the https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/src/main/java/org/bonitasoft/engine/authentication/GenericAuthenticationService.java[GenericAuthenticationService], +https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/src/main/java/org/bonitasoft/engine/core/login/SecuredLoginServiceImpl.java[SecuredLoginServiceImpl] +performs an extra check to verify that the provided username exists in the Bonita database (https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/src/main/java/org/bonitasoft/engine/core/login/SecuredLoginServiceImpl.java[SecuredLoginServiceImpl] +does not trust https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-authentication/src/main/java/org/bonitasoft/engine/authentication/impl/AuthenticationServiceImpl.java[AuthenticationServiceImpl]). *Note:* A specific behavior applies for the tenant technical user. -. https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/bonita-login-api-impl/src/main/java/org/bonitasoft/engine/core/login/SecuredLoginServiceImpl.java[SecuredLoginServiceImpl] -returns an object that represents the session. This is a server side only object (https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-session/bonita-session-api/src/main/java/org/bonitasoft/engine/session/model/SSession.java[SSession]) +. https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-login/src/main/java/org/bonitasoft/engine/core/login/SecuredLoginServiceImpl.java[SecuredLoginServiceImpl] +returns an object that represents the session. This is a server side only object (https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-session/src/main/java/org/bonitasoft/engine/session/model/SSession.java[SSession]) . Call get back to https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-core/bonita-process-engine/src/main/java/org/bonitasoft/engine/api/impl/LoginAPIImpl.java[LoginAPIImpl] -that converts https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-session/bonita-session-api/src/main/java/org/bonitasoft/engine/session/model/SSession.java[SSession] -to https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-api/bonita-common-api/src/main/java/org/bonitasoft/engine/session/APISession.java[APISession]. -. https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-api/bonita-common-api/src/main/java/org/bonitasoft/engine/session/APISession.java[APISession] +that converts https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-session/src/main/java/org/bonitasoft/engine/session/model/SSession.java[SSession] +to https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-common/src/main/java/org/bonitasoft/engine/session/APISession.java[APISession]. +. https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-common/src/main/java/org/bonitasoft/engine/session/APISession.java[APISession] is provided back up to the https://github.com/bonitasoft/bonita-web/blob/{bonitaTechnicalVersion}/server/src/main/java/org/bonitasoft/console/common/server/login/LoginManager.java[LoginManager] that will add session information as HTTP session attribute. . Call get back to https://github.com/bonitasoft/bonita-web/blob/{bonitaTechnicalVersion}/server/src/main/java/org/bonitasoft/console/common/server/login/servlet/LoginServlet.java[LoginServlet] @@ -106,7 +106,7 @@ and corresponds to one user. *The Bonita Engine session* -See https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-api/bonita-common-api/src/main/java/org/bonitasoft/engine/session/APISession.java[APISession] +See https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-common/src/main/java/org/bonitasoft/engine/session/APISession.java[APISession] class. This session is created by Bonita Engine when the user submits a login page. *Session expiration* @@ -116,7 +116,7 @@ an exception will be raised. Bonita Applications will catch this exception, invalidate the HTTP session and redirect the user to the login page. NOTE: The Bonita Engine default session duration is one hour (default value -defined in https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-session/bonita-session-impl/src/main/java/org/bonitasoft/engine/session/impl/SessionServiceImpl.java[SessionServiceImpl]). +defined in https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/services/bonita-session/src/main/java/org/bonitasoft/engine/session/impl/SessionServiceImpl.java[SessionServiceImpl]). You can configure a different session duration by editing the `bonita.tenant.session.duration` property in `bonita-tenant-community-custom.properties`. Specify the duration in milliseconds. If the HTTP session has expired, Bonita Applications will redirect the user to the @@ -136,7 +136,7 @@ Engine session and HTTP session will be invalidated. == How do Bonita Applications know if a user is authenticated? -The Bonita Applications check if a valid Bonita Engine session (https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-api/bonita-common-api/src/main/java/org/bonitasoft/engine/session/APISession.java[APISession] +The Bonita Applications check if a valid Bonita Engine session (https://github.com/bonitasoft/bonita-engine/blob/{bonitaTechnicalVersion}/bpm/bonita-common/src/main/java/org/bonitasoft/engine/session/APISession.java[APISession] object) is found in the `apiSession` attribute inside the HttpRequest. If the engine session is still valid, the user will have access to the required resource. diff --git a/modules/integration/pages/event-handlers.adoc b/modules/integration/pages/event-handlers.adoc index cfa0e1436f..676e5886a2 100644 --- a/modules/integration/pages/event-handlers.adoc +++ b/modules/integration/pages/event-handlers.adoc @@ -106,30 +106,6 @@ pom.xml : - - - - restlet - - true - - - false - - https://maven.restlet.talend.com/ - - - terracotta - - true - - - false - - https://repo.terracotta.org/maven2/ - - - ---- diff --git a/modules/pages-and-forms/pages/create-or-modify-a-page.adoc b/modules/pages-and-forms/pages/create-or-modify-a-page.adoc index 73ac6bb18c..35fb714595 100644 --- a/modules/pages-and-forms/pages/create-or-modify-a-page.adoc +++ b/modules/pages-and-forms/pages/create-or-modify-a-page.adoc @@ -7,7 +7,7 @@ == User Interfaces development overview Your automation project can use xref:ROOT:pages.adoc[pages] to display information and provide interaction controls to the end-users or administrators. + -It most of the times uses xref:forms.adoc[forms] to display and collect new or edited information. + +It most of the time uses xref:forms.adoc[forms] to display and collect new or edited information. + Forms and pages are made of containers and widgets. + Some containers and widgets can be grouped in xref:ROOT:fragments.adoc[fragments], in order to be reused in several pages or forms. + @@ -21,7 +21,7 @@ Developers can xref:applications:customize-living-application-theme.adoc[create Bonita UI Designer comes with a set of xref:ROOT:widgets.adoc[provided containers and widgets]. + xref:custom-widgets.adoc[Custom widgets] can also be created to make the palette richer. + -Those are developped by professional developers, from scratch or from an https://community.bonitasoft.com/project[existing project] of the Community. + +Those are developed by professional developers, from scratch or from an https://community.bonitasoft.com/c/project/5[existing project] of the Community. + The following chapters give more information on how to develop all the others elements in the UI Designer. @@ -44,13 +44,13 @@ For more technical information about the forms, visit xref:ROOT:forms-developmen == Create a page -xref:ROOT:pages.adoc[Pages] are created independently from the processes. They are used to display business information that group several processes and several instances of the processes in an efficient view, a list of requests, for example. + +xref:ROOT:pages.adoc[Pages] are created independently of the processes. They are used to display business information that group several processes and several instances of the processes in an efficient view, a list of requests, for example. + The controls they embed (buttons, links) can call BPM APIs that will trigger the display of the process instantiation form, or the execution of a task. === From scratch . From Bonita Studio coolbar, click on the *_UI Designer_* icon to open the UI Designer. + . Click on the *_Create_* button -. In the pop up, choose the element to create +. In the pop-up, choose the element to create . Give it a name . Click on the *_Create_* button . In the page editor, drag and drop the widgets, fragments, or BDM objects to create the right user interface @@ -61,7 +61,7 @@ You can easily duplicate an exiting page just by saving it under a different nam . From Bonita Studio coolbar, click on the *_UI Designer_* icon to open the UI Designer. + . Open the page you want to duplicate . Click on the *_Save_* button and select *_Save as_* -. In the pop up, choose the element to create (new page or form) +. In the pop-up, choose the element to create (new page or form) . Give it a name . Click on the *_Save_* button @@ -72,14 +72,14 @@ Only Bonita pages created with the UI Designer can be customized in the UI Desig To customize a page provided by Bonita: . From Bonita Studio coolbar, click on the *_Applications_* icon, and open the *_Administrator Application_* -. Go to the *_Resources_* menu, find the page, and and check its description to make sure it is a page done with Bonita UI Designer +. Go to the *_Resources_* menu, find the page, and check its description to make sure it is a page done with Bonita UI Designer . Export the page . From Bonita Studio coolbar, click on the *_UI Designer_* icon to open Bonita UI Designer . Import the page in the UI Designer Note that by doing so, if the page embed fragments and custom widgets, they are also imported and added to the UI Designer palette. -You can find the list of pages ready for customization in a xref:ROOT:pages.adoc#_List_of_Bonita_Applications_customizable_pages[dedicated documentation page]. +You can find the list of pages ready for customization in a xref:ROOT:pages.adoc#list_bonita_application_customizable_pages[dedicated documentation page]. For more technical information about the pages, visit xref:ROOT:pages-development.adoc[the dedicated documentation page]. @@ -101,7 +101,7 @@ For more technical information about the pages, visit xref:ROOT:pages-developmen . In Bonita Studio, go to the _Project Explorer_ . Open the project, and the _Pages/Forms/Layouts_ section -. Double click on _Bonita layout_. This automatically opens the UI Designer with the layout ready to edit. +. Double-click on _Bonita layout_. This automatically opens the UI Designer with the layout ready to edit. . Edit it and save it with another name === From scratch @@ -135,7 +135,7 @@ You can display your page, layout, form or fragment with one of your theme appli From the preview window, you can also expand the preview outside of current preview mechanism, with the *Expand Preview in new window* button. This allows you to set new URL parameters, play with dynamic browser sizing, and to reuse same url in another browser to see how your form or page behaves in your user default browser. + -You can use the a device types bar on the preview screen to choose the target device type. + +You can use the device types bar on the preview screen to choose the target device type. + The preview displays the element as it would be displayed on the selected type of device. + [#export] @@ -147,7 +147,7 @@ You can export any element to import it into another UI Designer. + To export an element, click the *_Export_* button image:images-6_0/pb-export.png[Export button] on the Page editor or the UI Designer home page. A zip file is downloaded to your computer. It contains a Bonita custom page, which is also suitable for import into another UI Designer. + -After export you can modify your page or layout code by directly editing the code located in _resources_ folder. Be aware that such a modification to the code will work when the page or layout is deployed in the Bonita Runtime, but it may be broken if you import the page into another UI Designer. +After export, you can modify your page or layout code by directly editing the code located in _resources_ folder. Be aware that such a modification to the code will work when the page or layout is deployed in the Bonita Runtime, but it may be broken if you import the page into another UI Designer. To import elements in another Studio, you can export pages and forms in the process `.bos` file. In the list of elements to insert in the .bos file, forms are checked by default, but not pages. When you import this `.bos` file into another Bonita Studio, forms and pages that you have checked are available in the UI Designer of that Studio. @@ -165,7 +165,7 @@ An element that has not been designed with the UI Designer cannot be imported in == Pages and forms in .bos/.bar file When you generate the `.bar` file of a process, the mapped forms created with the UI Designer are embedded in the file. + -Application pages are not embedded as they are independant from the process. + +Application pages are not embedded as they are independent of the process. + When the .bar file is deployed, forms are deployed too. + Applications and its elements must be deployed onto the target environment. This can be done manually from the Super Administrator or Administrator applications, in the *_Applications_* and *_Resources_* menu options. It can also be done automatically through the automation of the project builds and deployment. diff --git a/modules/pages-and-forms/pages/pages.adoc b/modules/pages-and-forms/pages/pages.adoc index 93531f3b9a..211cc6a9f3 100644 --- a/modules/pages-and-forms/pages/pages.adoc +++ b/modules/pages-and-forms/pages/pages.adoc @@ -10,6 +10,7 @@ Bonita Runtime comes with some provided pages to use in applications. They are w Starting with Bonita 2021.1, you can also download Bonita User application and Bonita Administrator applications (from Bonita Studio Welcome page), and get more provided pages, developped with Bonita UI Designer. + Such UI Designer pages can be customized in the UI Designer, to better fit the needs of the end-users. +[#list_bonita_application_customizable_pages] === List of Bonita Applications customizable pages ==== Bonita User Application @@ -21,7 +22,7 @@ In this application, you can customize: ==== Bonita Administrator Applications -In thess applications, when relevant, you can customize: +In these applications, when relevant, you can customize: * Bonita Admin Process List `adminProcessListBonitaV_` * Bonita Admin Case Details `adminCaseDetailsBonitaV_` @@ -52,7 +53,7 @@ A few examples of custom pages: * Provide an administrator with a multi-attribute search facility. * Integrate a page from an external application. -For all information about developping a custom page, visit xref:ROOT:pages-development.adoc[the dedicated documentation page]. +For all information about developing a custom page, visit xref:ROOT:pages-development.adoc[the dedicated documentation page]. == Use in applications diff --git a/modules/pages-and-forms/pages/widgets-inputs.adoc b/modules/pages-and-forms/pages/widgets-inputs.adoc index 3a38c7f3d3..daceadcf50 100644 --- a/modules/pages-and-forms/pages/widgets-inputs.adoc +++ b/modules/pages-and-forms/pages/widgets-inputs.adoc @@ -22,6 +22,7 @@ There are four types of input: * number: a decimal or integer number * password: like text but each character is replaced by an asterisk. +[#currency-input-widget] === Currency input widget image::widgets/currency-input.png[currency-input] diff --git a/modules/process/pages/cmis.adoc b/modules/process/pages/cmis.adoc index 80dcff8086..95916101a1 100644 --- a/modules/process/pages/cmis.adoc +++ b/modules/process/pages/cmis.adoc @@ -52,9 +52,9 @@ If this configuration is not set, new versions of documents will overwrite previ * Binding type: webservices (or atompub) * The URL (server address) for the atompub binding if it is used * If using webservices, there are four new URLs: - ** RepositoryService, for example _https://localhost:12345/alfresco/cmis/RepositoryService?wsdl_ + ** RepositoryService, for example _++https://localhost:12345/alfresco/cmis/RepositoryService?wsdl++_ ** RepositoryService endpoint - ** ObjectService, for example _https://localhost:12345/alfresco/cmis/ObjectService?wsdl_ + ** ObjectService, for example _++https://localhost:12345/alfresco/cmis/ObjectService?wsdl++_ ** ObjectService endpoint * Click *_Next_*. @@ -90,7 +90,7 @@ This example presents the creation of a folder on a local installation of Alfres * Username and password * Repository name: -default- * Binding type: atompub -* URL: http://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.1/atom/ +* URL: _++http://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.1/atom/++_ * Click *_Next_*. . In the Folder window, enter the location and name of the folder you wish to create: diff --git a/modules/process/pages/connector-archetype-tutorial.adoc b/modules/process/pages/connector-archetype-tutorial.adoc index 92e5585639..20a8ec2624 100644 --- a/modules/process/pages/connector-archetype-tutorial.adoc +++ b/modules/process/pages/connector-archetype-tutorial.adoc @@ -585,6 +585,7 @@ You can build the connector using the following command line at the root of the ./mvnw clean package ---- +[#publish_connector_to_gh_packages] == 6 - Publish the connector on GitHub packages [NOTE] diff --git a/modules/process/pages/connector-migration.adoc b/modules/process/pages/connector-migration.adoc index 55a493c318..8b89091d03 100644 --- a/modules/process/pages/connector-migration.adoc +++ b/modules/process/pages/connector-migration.adoc @@ -15,7 +15,7 @@ All the content of this page can be applied to migrate actor filters created wit First of all, a new connector project has to be created using the provided maven archetype. + xref:connector-archetype#_generate_the_project_using_the_maven_archetype[This piece of documentation] explains how to create a connector project using the maven archetype. -Some parameters have to be passed to the maven archetype to create the project (groupid, artifactId, version, package, language...). Make sure to use *Java* as the language, so the existing implementation code will be reusable. It is also recommended to keep the package of the current connector implementation, else you might need to edit some part of your implementation source code. +Some parameters have to be passed to the maven archetype to create the project (groupId, artifactId, version, package, language...). Make sure to use *Java* as the language, so the existing implementation code will be reusable. It is also recommended to keep the package of the current connector implementation, else you might need to edit some part of your implementation source code. [TIP] ==== @@ -296,4 +296,4 @@ The migration from the old project is completed. + The project can be built using the command `./mvnw clean package` at the root of the project. + The jar built in the folder _target_ can be imported as an extension in the Studio, to test that the migration has been done correctly. -Once you are done, it is recommended to publish your connector on a maven repository, so it will be possible to use this connector as a Bonita extension using its maven coordinates. An example is available xref:connector-archetype-tutorial#_6_publish_the_connector_on_github_packages[here]. +Once you are done, it is recommended to publish your connector on a maven repository, so it will be possible to use this connector as a Bonita extension using its maven coordinates. An example is available xref:connector-archetype-tutorial.adoc#publish_connector_to_gh_packages[here]. diff --git a/modules/runtime/images/tomcat-behind-reverse-proxy.png b/modules/runtime/images/tomcat-behind-reverse-proxy.png new file mode 100644 index 0000000000..c771484ffc Binary files /dev/null and b/modules/runtime/images/tomcat-behind-reverse-proxy.png differ diff --git a/modules/runtime/pages/bonita-platform-setup.adoc b/modules/runtime/pages/bonita-platform-setup.adoc index 5fe938de65..509c81b561 100644 --- a/modules/runtime/pages/bonita-platform-setup.adoc +++ b/modules/runtime/pages/bonita-platform-setup.adoc @@ -185,7 +185,7 @@ It is made of both data entered in file `database.properties` as well as other d This file *should not* be modified manually in most cases, unless for specific use-cases like adding parameters in the connection URL or using a specific database driver. This file contains the Database configuration information that are not inside file `database.properties` (database driver class name, connection URL, etc). -Those information are used internally by the Bonita Setup tool to configure properly the bundle (See <>) and the database initialization procedure (See <>). + +This information are used internally by the Bonita Setup tool to configure properly the bundle (See <>) and the database initialization procedure (See <>). + Bonita Setup tool uses the values provided in file `database.properties` as replacement strings to the properties defined in file `internal.properties`. Those new processed values are then used by the tool. _Usage_: + @@ -211,6 +211,7 @@ Or also if you need to use a specific *database Driver* java class name: *But in most cases, you don't need to modify this file.* +[#troubleshooting] [.troubleshooting-title] == Troubleshooting diff --git a/modules/runtime/pages/cases.adoc b/modules/runtime/pages/cases.adoc index 64d3c96337..8d8fbda226 100644 --- a/modules/runtime/pages/cases.adoc +++ b/modules/runtime/pages/cases.adoc @@ -45,7 +45,7 @@ Zoom in the diagram with either _Ctrl+mouse wheel_ or the zoom buttons. If you a Once zoomed in, you can drag the diagram. + Resize your browser window and click on the *_Reset_* button to fit the diagram to your window. -Remember that a failure at a step does not necessarily mean that the case has failed entirely, but it might indicate that some action is needed, perhaps to xref:ROOT:admin-application-task-list.adoc#_replay_a_failed_task[replay a connector]. +Remember that a failure at a step does not necessarily mean that the case has failed entirely, but it might indicate that some action is needed, perhaps to xref:ROOT:admin-application-task-list.adoc#_replay_a_failed_flow_node[replay a connector]. You can customize the diagram page, or embed the BPMN diagram in your own page: see xref:pages-and-forms:customize-display-process-monitoring.adoc[How to customize the display of process execution monitoring]. diff --git a/modules/runtime/pages/custom-deployment.adoc b/modules/runtime/pages/custom-deployment.adoc index 3e7b13861b..a6bd07ef9e 100644 --- a/modules/runtime/pages/custom-deployment.adoc +++ b/modules/runtime/pages/custom-deployment.adoc @@ -90,7 +90,7 @@ We assume here that the database has already been xref:ROOT:database-configurati Once created and configured you need to initialize it using the setup tool provided in the bundle. This will create database schema and initial values. -. In `TOMCAT_DIRECTORY/setup` folder, edit the file `database.properties` with properties matching your RDBMS. Beware of xref:runtime:bonita-platform-setup.adoc#backslash_support[backslash characters]. +. In `TOMCAT_DIRECTORY/setup` folder, edit the file `database.properties` with properties matching your RDBMS. Beware of xref:runtime:bonita-platform-setup.adoc#troubleshooting[backslash characters]. . In `TOMCAT_DIRECTORY/setup` folder, run `setup.(sh|bat) init` == Next steps diff --git a/modules/runtime/pages/database-configuration.adoc b/modules/runtime/pages/database-configuration.adoc index 122123e091..09512b1885 100644 --- a/modules/runtime/pages/database-configuration.adoc +++ b/modules/runtime/pages/database-configuration.adoc @@ -231,8 +231,8 @@ To support XA transactions, SQL Server requires a specific configuration. You can refer to https://msdn.microsoft.com/en-us/library/aa342335(v=sql.110).aspx[MSDN] for more information. Here is the list of steps to perform (as an example, the database name BONITA is used): -. Download the zip package of https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=11774[Microsoft SQL Server JDBC Driver 6.0] and unzip it. -. Copy the `sqljdbc_xa.dll` from `%JDBC_DRIVER_INSTALL_ROOT%\sqljdbc_6.0\enu\xa\x64\` (x64 for 64 bit version of Windows, x86 for 32 bit version of Windows) to `%SQLSERVER_INSTALL_ROOT%\MSSQL13.\MSSQL\Binn\.` +. Download the zip package of https://learn.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server[Microsoft SQL Server JDBC Driver] and unzip it. +. Copy the `sqljdbc_xa.dll` from `%JDBC_DRIVER_INSTALL_ROOT%\sqljdbc\enu\xa\x64\` (x64 for 64 bit version of Windows, x86 for 32 bit version of Windows) to `%SQLSERVER_INSTALL_ROOT%\MSSQL13.\MSSQL\Binn\.` . Copy/paste the content of `install.sql` file (located in `%JDBC_DRIVER_INSTALL_ROOT%\sqljdbc\6.0\enu\xa`) to SQL Server Management Studio's Query Editor. . Execute the query in the Query Editor. . To confirm successful execution of the script, open the "Object Explorer" and go to: *Master* > *Programmability* > *Extended Stored Procedures*. + diff --git a/modules/runtime/pages/first-steps-after-setup.adoc b/modules/runtime/pages/first-steps-after-setup.adoc index 89c816ba66..5b2d5d8732 100644 --- a/modules/runtime/pages/first-steps-after-setup.adoc +++ b/modules/runtime/pages/first-steps-after-setup.adoc @@ -37,7 +37,7 @@ A key security concern when using passwords for authentication is password stren ==== Choose a strong password for your database -The database is at the heart of your application. It is where all entreprise data (sensitive or non-sensitive) is stored. As a result, the database username and password are of great value to the business and they need to be protected. It is highly recommended to choose strong, random and long passwords, since they make it difficult or even improbable for one to guess the password through either manual or automated means. +The database is at the heart of your application. It is where all enterprise data (sensitive or non-sensitive) is stored. As a result, the database username and password are of great value to the business and they need to be protected. It is highly recommended to choose strong, random and long passwords, since they make it difficult or even improbable for one to guess the password through either manual or automated means. ==== Choose a strong password for your connectors @@ -101,7 +101,7 @@ Create a user with the "administrator" profile: NOTE: do not create a user or an administrator with the same login and password as the technical users (platform or tenant) . Log into the Bonita Runtime as the technical user. + -*Note:* If your system is using single sign-on with CAS, you need to log in with the following URL: `http://`_`hostname:port`_`/bonita/login.jsp?redirectUrl=/bonita/apps/appDirectoryBonita/`. +*Note:* If your system is using single sign-on with CAS, you need to log in with the following URL: `+http://hostname:port/bonita/login.jsp?redirectUrl=/bonita/apps/appDirectoryBonita/+`. . Open the Bonita Super Admin Application . Create a user with the standard profile. . Go to *Organization* > *Profiles*. Click on triple dots button for "Administrator" profile. diff --git a/modules/runtime/pages/healthcheck-mechanism.adoc b/modules/runtime/pages/healthcheck-mechanism.adoc index beb967a578..7b61943404 100644 --- a/modules/runtime/pages/healthcheck-mechanism.adoc +++ b/modules/runtime/pages/healthcheck-mechanism.adoc @@ -3,7 +3,7 @@ [#api-health-endpoints] == API health endpoints -The Bonita docker image provides one API endpoint, /healthz to indicate the current state of the platform (accessed by the URL https:///bonita/healthz). +The Bonita docker image provides one API endpoint, `/healthz` to indicate the current state of the platform (accessed by the URL `+https:///bonita/healthz+`). A call to the URL will typically return the following information in JSON format: [source,json] @@ -19,11 +19,11 @@ A call to the URL will typically return the following information in JSON format "executionTimeMillis":"7"} ---- -The most common "unhealthy" state will be that the /healthz URL is not accessible. +The most common "unhealthy" state will be that the `/healthz` URL is not accessible. == Security -The /healthz endpoint is protected by a username/password authentication. The default values are username `monitoring` and password `mon1tor1ng_adm1n`. +The `/healthz` endpoint is protected by a username/password authentication. The default values are username `monitoring` and password `mon1tor1ng_adm1n`. It is very much recommended to change those values. It can be done by overriding the following environment properties: [source,text] @@ -47,5 +47,5 @@ docker run -p 8080:8080 -v ~/lic:/opt/bonita_lic/ --env-file ~/bonita.env --name ---- == Internal Workings -The /healthz endpoint is an internal class that retrieves various information through the PlatformAPI.java. -If one of the requested information cannot be retrieved (ie. if the API call raises an exception), the endpoint will return a status "error" with a stacktrace. +The `/healthz` endpoint is an internal class that retrieves various information through the PlatformAPI.java. +If one of the requested information cannot be retrieved (i.e. if the API call raises an exception), the endpoint will return a status "error" with a stacktrace. diff --git a/modules/runtime/pages/how-a-bdm-is-deployed.adoc b/modules/runtime/pages/how-a-bdm-is-deployed.adoc index 7a1d2ed1b9..006635fdfc 100644 --- a/modules/runtime/pages/how-a-bdm-is-deployed.adoc +++ b/modules/runtime/pages/how-a-bdm-is-deployed.adoc @@ -112,7 +112,7 @@ Also, DAO interfaces and implementations are generated, to give access to the qu } ---- -DAO implementation code uses https://javadoc.bonitasoft.com/api/${javadocVersion}/org/bonitasoft/engine/api/CommandAPI.html[Engine Commands] +DAO implementation code uses https://javadoc.bonitasoft.com/api/{javadocVersion}/org/bonitasoft/engine/api/CommandAPI.html[Engine Commands] to call from client-side queries that run server-side. Once generated, those Java classes are *compiled and packaged*: diff --git a/modules/runtime/pages/install-a-bonita-bpm-cluster.adoc b/modules/runtime/pages/install-a-bonita-bpm-cluster.adoc index 4660eb64ec..b810d9fc1e 100644 --- a/modules/runtime/pages/install-a-bonita-bpm-cluster.adoc +++ b/modules/runtime/pages/install-a-bonita-bpm-cluster.adoc @@ -44,7 +44,7 @@ When done you will have a database with all tables created and with a table `CON . xref:ROOT:database-configuration.adoc#database_creation[Create the database]. . In case you use xref:data:define-and-deploy-the-bdm.adoc[Business data], xref:database-configuration.adoc#database_creation[create a database for the Business Data]. . Download a Bonita xref:tomcat-bundle.adoc[Tomcat bundle] and unzip it in your chosen folder. -. Edit file *`setup/database.properties`* and modify the properties to suit your databases (Bonita internal database & Business Data database). Beware of xref:runtime:bonita-platform-setup.adoc#backslash_support[backslash characters]. +. Edit file *`setup/database.properties`* and modify the properties to suit your databases (Bonita internal database & Business Data database). Beware of xref:runtime:bonita-platform-setup.adoc#troubleshooting[backslash characters]. In the following steps, you will update the configuration files that are in the `setup/platform_conf/initial` folder of the platform setup tool. @@ -223,13 +223,13 @@ To dismantle a cluster: . When all nodes have been stopped, update the load balancer to remove the cluster. The individual nodes can now be used as standalone Bonita server, provided the following change in the configuration is done: -Update file `bonita-platform-sp-custom.properties` located in the `platform_engine` folder of the configuration, use the xref:runtime:bonita-platform-setup.adoc#configuration_files[platform setup tool] to update it and set back the *`bonita.cluster`* property to *`false`*. +Update file `bonita-platform-sp-custom.properties` located in the `platform_engine` folder of the configuration, use the xref:runtime:bonita-platform-setup.adoc[platform setup tool] to update it and set back the *`bonita.cluster`* property to *`false`*. -See xref:runtime:bonita-platform-setup.adoc#updating_configuration[How to update a Bonita Tomcat Bundle configuration] for more details on updating the configuration. +See xref:runtime:bonita-platform-setup.adoc#run_bundle_configure[How to update a Bonita Tomcat Bundle configuration] for more details on updating the configuration. === Managing the cluster with Hazelcast -As said before, Bonita cluster uses Hazelcast as the distributed cluster dispatcher layer. Therefore you can use the Hazelcast tools to manage the cluster topology. +As said before, Bonita cluster uses Hazelcast as the distributed cluster dispatcher layer. Therefore, you can use the Hazelcast tools to manage the cluster topology. See the http://www.hazelcast.com/docs.jsp[Hazelcast documentation] for details. Note that a Bonita cluster uses multicast for discovery by default. You can disable this in Hazelcast. @@ -237,7 +237,7 @@ If you are using multicast, you must ensure that your production environment is This is to ensure the nodes do not discover each other on the network, if they are not supposed to run inside the same cluster. It is possible to have more than one cluster on the same network. In this case, you must configure the cluster names to be sure that it is clear which node belongs to which cluster. -You can configure the cluster name through Hazelcast or by updating `bonita-platform-sp-custom.properties` located in the `platform_engine` folder of the configuration, use the xref:runtime:bonita-platform-setup.adoc#configuration_files[platform setup tool] to update it. +You can configure the cluster name through Hazelcast or by updating `bonita-platform-sp-custom.properties` located in the `platform_engine` folder of the configuration, use the xref:runtime:bonita-platform-setup.adoc[platform setup tool] to update it. == image:troubleshooting.png[troubleshooting-icon] Troubleshooting diff --git a/modules/runtime/pages/log-in-and-log-out.adoc b/modules/runtime/pages/log-in-and-log-out.adoc index 60d60a21a9..d246a3c6db 100644 --- a/modules/runtime/pages/log-in-and-log-out.adoc +++ b/modules/runtime/pages/log-in-and-log-out.adoc @@ -18,11 +18,11 @@ Or an administrator needs to perform monitoring or maintenance on the Bonita Pla For any of this, they need to log in. To do so: . Enter the login page URL. (The default port number is 8080.) + - * For Bonita User Application: `http://`_`hostname:port`_`/bonita/apps/userApp`. + + * For Bonita User Application: `+http://hostname:port/bonita/apps/userApp+`. + * For Bonita Administrator Application: - ** For the Enterprise edition: `http://`_`hostname:port`_`/bonita/apps/adminAppSP` - ** For the Community edition: `http://`_`hostname:port`_`/bonita/apps/adminApp` - *** For a custom application: `http://`_`hostname:port`_`/bonita/apps/yourAppName`. + ** For the Enterprise edition: `+http://hostname:port/bonita/apps/adminAppSP+` + ** For the Community edition: `+http://hostname:port/bonita/apps/adminApp+` + *** For a custom application: `+http://hostname:port/bonita/apps/yourAppName+`. . In the fields, enter the _username_, and the _password_ . Click on the *Login* button. diff --git a/modules/runtime/pages/reverse-proxy-configuration.adoc b/modules/runtime/pages/reverse-proxy-configuration.adoc index 0760e3e79e..6ab1b5c07f 100644 --- a/modules/runtime/pages/reverse-proxy-configuration.adoc +++ b/modules/runtime/pages/reverse-proxy-configuration.adoc @@ -13,7 +13,7 @@ Bonitasoft does not support anymore having Bonita Runtime running on a dedicated If you have to expose Bonita Runtime or a Bonita-developed application publicly, but legitimately want to protect any other resources behind your firewall, you should set up a software architecture similar to this one: -image::https://people.apache.org/~mturk/docs/article/fig2.gif[Tomcat behind a firewall with reverse proxy] +image::tomcat-behind-reverse-proxy.png[Tomcat behind a firewall with reverse proxy] where the Web Server serves as a reverse proxy, and where the Tomcat server hosts Bonita. diff --git a/modules/runtime/pages/tomcat-bundle.adoc b/modules/runtime/pages/tomcat-bundle.adoc index 7bc37d464a..fbb7c44f55 100644 --- a/modules/runtime/pages/tomcat-bundle.adoc +++ b/modules/runtime/pages/tomcat-bundle.adoc @@ -4,7 +4,7 @@ You will find here the mandatory and optional steps needed to install and configure the Tomcat bundle to run the Bonita platform. -The Tomcat bundle is a .zip archive that contains the Apache Tomcat Java EE application server prepackaged along with Bonita and xref:runtime:bonita-platform-setup.adoc#platform_setup_tool[Bonita platform setup tool]. +The Tomcat bundle is a .zip archive that contains the Apache Tomcat Java EE application server prepackaged along with Bonita and xref:runtime:bonita-platform-setup.adoc#bonita_setup_tool[Bonita platform setup tool]. The Tomcat bundle is a regular .zip archive based on Tomcat zip distribution. [#tomcat-bundle-installation] @@ -147,7 +147,7 @@ For production, you are recommended to use one of the supported databases, with ==== . Make sure xref:ROOT:database-configuration.adoc#database_creation[your databases are created] and xref:database-configuration.adoc#specific_database_configuration[customized to work with Bonita]. -. Edit file `/setup/database.properties` and modify the properties to suit your databases (Bonita internal database & Business Data database). Beware of xref:runtime:bonita-platform-setup.adoc#backslash_support[backslash characters]. +. Edit file `/setup/database.properties` and modify the properties to suit your databases (Bonita internal database & Business Data database). Beware of xref:runtime:bonita-platform-setup.adoc#troubleshooting[backslash characters]. . Run `\setup\start-bonita.bat` (Windows system) or `/setup/start-bonita.sh` (Unix system) to run Bonita Tomcat bundle (see <>) [NOTE] diff --git a/modules/runtime/pages/use-gzip-compression.adoc b/modules/runtime/pages/use-gzip-compression.adoc index 9d80193ee3..34e8aaa877 100644 --- a/modules/runtime/pages/use-gzip-compression.adoc +++ b/modules/runtime/pages/use-gzip-compression.adoc @@ -62,7 +62,7 @@ Official Tomcat documentation for https://tomcat.apache.org/tomcat-9.0-doc/confi == Check changes After you modify the file, restart your application server and test with the following `curl` command: -`curl -I -H 'Accept-Encoding: gzip' http://`_`ip_address:port`_`/bonita/login.jsp` +`curl -I -H 'Accept-Encoding: gzip' +http://ip_address:port/bonita/login.jsp+` Check that the header returned contains the line `Content-Encoding: gzip`. The output should be similar to this: diff --git a/modules/runtime/pages/user-application-index.adoc b/modules/runtime/pages/user-application-index.adoc index 9fb3e185d3..21b83cfd8f 100644 --- a/modules/runtime/pages/user-application-index.adoc +++ b/modules/runtime/pages/user-application-index.adoc @@ -1,6 +1,6 @@ = Bonita User Application :page-aliases: ROOT:user-application-index.adoc -:description: This page gives an easy access to Bonita User Application content, and to some related topics elsewhere in the documentation. +:description: This page gives easy access to Bonita User Application content, and to some related topics elsewhere in the documentation. {description} @@ -19,12 +19,12 @@ xref:ROOT:user-process-list.adoc[[.card-title]#Process list# [.card-body.card-co [.card.card-index] -- -xref:ROOT:user-application-case-list.adoc[[.card-title]#Case list# [.card-body.card-content-overflow]#pass:q[Follow up open instances, check the closed ones]#] +xref:ROOT:user-application-case-list.adoc[[.card-title]#Case list# [.card-body.card-content-overflow]#pass:q[Follow-up open instances, check the closed ones]#] -- [.card.card-index] -- -xref:ROOT:user-task-list.adoc#installAccessControl[[.card-title]#Task list# [.card-body.card-content-overflow]#pass:q[Open forms, fill out the data, submit, and get efficient]#] +xref:ROOT:user-task-list.adoc[[.card-title]#Task list# [.card-body.card-content-overflow]#pass:q[Open forms, fill out the data, submit, and get efficient]#] -- [.card-section] diff --git a/modules/setup-dev-environment/pages/shared-project.adoc b/modules/setup-dev-environment/pages/shared-project.adoc index e26350c1b6..14b78d9a35 100644 --- a/modules/setup-dev-environment/pages/shared-project.adoc +++ b/modules/setup-dev-environment/pages/shared-project.adoc @@ -10,7 +10,7 @@ === Prerequisites * A remote Git repository (https://github.com/[GitHub], https://bitbucket.org[Bitbucket]...) -* Basic Git workflow knowledge (https://git-scm.com/book/en/v2/Getting-Started-Git-Basics[Reference article]) +* Basic Git workflow knowledge (https://git-scm.com/book/en/v2/Git-Basics-Getting-a-Git-Repository[Reference article]) === Git integration in Studio @@ -74,7 +74,7 @@ Bonita Studio integrates the default merge tool of EGit. Here are some hints on === Advanced Git commands -Git workflow offers a lot of other features that are not directly integrated in Bonita Studio. You can still use them using the command line interface (https://git-scm.com/download/[available here]). To retrieve the location of your project on your filesystem do a right click on the project name in the project explorer and select *Show in system explorer* (default location of your project would be: ++++++/workspace/++++++).++++++++++++ +Git workflow offers a lot of other features that are not directly integrated in Bonita Studio. You can still use them using the command line interface (https://git-scm.com/downloads[available here]). To retrieve the location of your project on your filesystem do a right click on the project name in the project explorer and select *Show in system explorer* (default location of your project would be: ++++++/workspace/++++++).++++++++++++ === Authentication The following authentication methods are supported: diff --git a/modules/setup-dev-environment/pages/workspaces-and-repositories.adoc b/modules/setup-dev-environment/pages/workspaces-and-repositories.adoc index ca3c369e79..407c3ba00b 100644 --- a/modules/setup-dev-environment/pages/workspaces-and-repositories.adoc +++ b/modules/setup-dev-environment/pages/workspaces-and-repositories.adoc @@ -94,7 +94,7 @@ If the list does not contain the name of the project you want to use, check that ==== Prerequisites * A remote Git repository (https://github.com/[GitHub], https://bitbucket.org[Bitbucket]...) -* Basic Git workflow knowledge (https://git-scm.com/book/en/v2/Getting-Started-Git-Basics[Reference article]) +* Basic Git workflow knowledge (https://git-scm.com/book/en/v2/Git-Basics-Getting-a-Git-Repository[Reference article]) ==== Git integration in Studio @@ -164,7 +164,7 @@ Bonita Studio integrates the default merge tool of EGit. Here are some hints on ==== Advanced Git commands -Git workflow offers a lot of other features that are not directly integrated in Bonita Studio. You can still use them using the command line interface (https://git-scm.com/download/[available here]). To retrieve the location of your project on your filesystem do a right click on the project name in the project explorer and select *Show in system explorer* (default location of your project would be: /workspace/). +Git workflow offers a lot of other features that are not directly integrated in Bonita Studio. You can still use them using the command line interface (https://git-scm.com/downloads[available here]). To retrieve the location of your project on your filesystem do a right click on the project name in the project explorer and select *Show in system explorer* (default location of your project would be: /workspace/). [#git-troubleshooting] @@ -177,7 +177,7 @@ Git workflow offers a lot of other features that are not directly integrated in I see this type of message in the Studio log, but when I open the URL in my browser, it works fine [.symptom-description] -`!MESSAGE An exception occurred during push on URI http://your_remote_git_repository/repository/my_bonita_repo.git: http://your_remote_git_repository/repository/my_bonita_repo.git: 503 Service Unavailable` +`!MESSAGE An exception occurred during push on URI +http://your_remote_git_repository/repository/my_bonita_repo.git+: +http://your_remote_git_repository/repository/my_bonita_repo.git+: 503 Service Unavailable` [.cause]*Potential cause* You probably connect to the internet through a Proxy diff --git a/modules/software-extensibility/pages/custom-library-development.adoc b/modules/software-extensibility/pages/custom-library-development.adoc index d00224a454..b10141d8c6 100644 --- a/modules/software-extensibility/pages/custom-library-development.adoc +++ b/modules/software-extensibility/pages/custom-library-development.adoc @@ -745,7 +745,7 @@ The released `jar` file will be attached to a GitHub release and you may use thi * https://maven.apache.org/repository/guide-central-repository-upload.html[Maven Central] ** How to automate it with https://docs.github.com/en/actions/guides/publishing-java-packages-with-maven[GitHub actions] * https://github.com/features/packages[GitHub packages] -** Example for xref:ROOT:connector-archetype-tutorial.adoc#_6_publish_the_connector_on_github_packages[connector extension] +** Example for xref:ROOT:connector-archetype-tutorial.adoc#publish_connector_to_gh_packages[connector extension] * Private Nexus or Artifactory...etc ====