Unverified Commit 6be7738d authored by Adrien's avatar Adrien Committed by GitHub
Browse files

Update all page links by adding the root module, so with the aliases all links work (#1788)

parent 6abc5eca
......@@ -4,18 +4,18 @@
{description} +
A REST API extension allows to extend REST Resources using Bonita, to get or send information in a page or a form.
To learn more on how to create REST API Extensions, refer to the xref:rest-api-extensions.adoc[tooling for creating and testing REST API Extensions] page (Enterprise, Performance, Efficiency, and Teamwork editions).
To learn more on how to create REST API Extensions, refer to the xref:ROOT:rest-api-extensions.adoc[tooling for creating and testing REST API Extensions] page (Enterprise, Performance, Efficiency, and Teamwork editions).
== Deploy a REST API Extension
REST API Extensions are xref:resource-management.adoc[managed] as resources.
REST API Extensions are xref:ROOT:resource-management.adoc[managed] as resources.
REST API Extensions use the same authorization mechanism as the standard Bonita REST APIs. When you import the extension, the information in `page.properties` is used to create the appropriate resource permission mappings in Bonita (see xref:rest-api-authorization.adoc[REST API authorization] for information about REST API security configuration).
REST API Extensions use the same authorization mechanism as the standard Bonita REST APIs. When you import the extension, the information in `page.properties` is used to create the appropriate resource permission mappings in Bonita (see xref:ROOT:rest-api-authorization.adoc[REST API authorization] for information about REST API security configuration).
[NOTE]
====
It is also possible to deploy a REST API Extensions using xref:portal-api.adoc#page[REST portal API / "page" resource].
It is also possible to deploy a REST API Extensions using xref:ROOT:portal-api.adoc#page[REST portal API / "page" resource].
====
[NOTE]
......@@ -33,7 +33,7 @@ If you are running Bonita in a cluster, after you import a REST API Extensions,
[WARNING]
====
As the deployment of the REST API Extensions automatically creates the appropriate resource permission mapping, be careful not to xref:bonita-platform-setup.adoc#update_platform_conf[push a configuration] that does not contain the latest permissions updates. This would overwrite the deployed configuration. To avoid doing so, pull the latest configuration, edit the needed elements and push it back to the Bonita runtime in a pretty short amount of time.
As the deployment of the REST API Extensions automatically creates the appropriate resource permission mapping, be careful not to xref:ROOT:bonita-platform-setup.adoc#update_platform_conf[push a configuration] that does not contain the latest permissions updates. This would overwrite the deployed configuration. To avoid doing so, pull the latest configuration, edit the needed elements and push it back to the Bonita runtime in a pretty short amount of time.
====
[#usage]
......@@ -47,7 +47,7 @@ A page that uses REST API Extensions must add the required resources in the page
If the page declares its resources correctly, then every user being able to access this page (because it is part of a custom profile or Living Application they have access to)
will also be automatically granted the necessary permissions to call the REST API Extensions. This works the same way as with the other resources of the REST API. +
However, if you need to grant access to this REST API Extensions to some users regardless of the pages they have access to, then you need to add xref:rest-api-authorization.adoc#custom-permissions-mapping[custom permissions] for these users. +
However, if you need to grant access to this REST API Extensions to some users regardless of the pages they have access to, then you need to add xref:ROOT:rest-api-authorization.adoc#custom-permissions-mapping[custom permissions] for these users. +
In order to do so, edit `custom-permissions-mapping.properties` to give the permissions (value of the property `apiExtension.permissions`) declared in the page.properties of the REST API Extensions to the required profiles or users.
[NOTE]
......@@ -60,14 +60,14 @@ REST API permissions are stored in the user's session and new permissions will o
In Bonita Studio, the debug mode is disabled by default. In debug mode, you can see changes on your REST API Extensions without importing a new zip archive, but it means the classloader of the extension is recreated at each request. +
If you want to enable the debug mode, you can activate it in the Studio server preferences.
xref:live-update.adoc[Live update] allows the Administrator to update one element of the application in a situation of emergency.
xref:ROOT:live-update.adoc[Live update] allows the Administrator to update one element of the application in a situation of emergency.
=== Edit the REST API extension
* Retrieve platform configuration using the xref:bonita-platform-setup.adoc#update_platform_conf[setup tool].
* Retrieve platform configuration using the xref:ROOT:bonita-platform-setup.adoc#update_platform_conf[setup tool].
* Edit `platform_conf/current/tenants/<TENANT_ID>/tenant_portal/custom-permissions-mapping.properties`.
* Add a permission for the REST API: `profile|User=[examplePermission]`.
* Push the changed platform configuration into database using the _setup tool_.
* Restart Tomcat bundle
You can xref:resource-management.adoc#modify[edit the content of a REST API extension] by installing a new version.
You can xref:ROOT:resource-management.adoc#modify[edit the content of a REST API extension] by installing a new version.
The url mappings in the `page.properties` in the new version should have the `examplePermission`.
\ No newline at end of file
......@@ -115,7 +115,7 @@ Example: +
[IMPORTANT]
====
A task is not automatically assigned to the user who accesses the task form. There must first be a xref:bpm-api.adoc[REST API call to assign the task to the user].
A task is not automatically assigned to the user who accesses the task form. There must first be a xref:ROOT:bpm-api.adoc[REST API call to assign the task to the user].
Otherwise, the user will not be able to execute the task.
====
......
......@@ -8,7 +8,7 @@
=== Prerequisites
Check the xref:hardware-and-software-requirements.adoc[hardware and software requirements].
Check the xref:ROOT:hardware-and-software-requirements.adoc[hardware and software requirements].
==== MacOs specific prerequisites
......
......@@ -25,9 +25,9 @@ or
. Specify the location where the .bar file will be created. The filename is determined by the process name and cannot be changed at this stage.
. Click *Finish*. The business archive is created.
When you build a process from the project explorer, the configuration used is the configuration saved as default. You can edit it from the xref:configuring-a-process.adoc[configure menu]
When you build a process from the project explorer, the configuration used is the configuration saved as default. You can edit it from the xref:ROOT:configuring-a-process.adoc[configure menu]
You can now xref:admin-application-process-list.adoc[install the process in Bonita Administrator Application].
You can now xref:ROOT:admin-application-process-list.adoc[install the process in Bonita Administrator Application].
== Initialize the organization in Bonita Administrator Application
......@@ -36,5 +36,5 @@ you must create the organization that you need for all the processes that will b
and import it into Bonita Administrator Application.
To export the organization, go to the *Organization* menu and choose *Export...*. You
can then xref:import-export-an-organization.adoc[import the organization into Bonita Administrator Application]. After the organization is imported,
you can xref:admin-application-groups-list.adoc[manage the groups], xref:admin-application-roles-list.adoc[roles], and xref:admin-application-users-list.adoc[users] in the organization.
can then xref:ROOT:import-export-an-organization.adoc[import the organization into Bonita Administrator Application]. After the organization is imported,
you can xref:ROOT:admin-application-groups-list.adoc[manage the groups], xref:admin-application-roles-list.adoc[roles], and xref:admin-application-users-list.adoc[users] in the organization.
......@@ -5,6 +5,6 @@ A set of best of breed tools to develop custom connectors independently of the B
[WARNING]
====
The Connector's development toolkit has been replaced by the xref:connector-archetype.adoc[Bonita connector
The Connector's development toolkit has been replaced by the xref:ROOT:connector-archetype.adoc[Bonita connector
archetype].
====
......@@ -3,8 +3,8 @@
{description}
Since the xref:portal-removal.adoc[removal of Portal in 2021.2], the Look & Feel was re-packaged in the bundle itself. You can find it in the `server/webapps/bonita/portal-theme` folder. For a reference about the contained files go to xref:https://documentation.bonitasoft.com/bonita/2021.1/creating-a-new-look-feel[the previous version of Bonita]. +
Since the xref:ROOT:portal-removal.adoc[removal of Portal in 2021.2], the Look & Feel was re-packaged in the bundle itself. You can find it in the `server/webapps/bonita/portal-theme` folder. For a reference about the contained files go to xref:https://documentation.bonitasoft.com/bonita/2021.1/creating-a-new-look-feel[the previous version of Bonita]. +
The two places that still use the old Look & Feel are old pages not made using the UI Designer and the Bonita Login page. +
Those old pages take into account the theme of your application. If you want to modify their style, we strongly suggest xref:themes.adoc[you change the theme]. +
Those old pages take into account the theme of your application. If you want to modify their style, we strongly suggest xref:ROOT:themes.adoc[you change the theme]. +
For the Login page, you will still need to change the old Look & Feel in the above-mentioned folder. A solution is in the works to take into account the theme of the application.
\ No newline at end of file
......@@ -5,21 +5,21 @@ How to effectively use the different kinds of data available within Bonita Platf
In a BPM-based application, use:
* xref:define-and-deploy-the-bdm.adoc[Business variables] for information that:
* xref:ROOT:define-and-deploy-the-bdm.adoc[Business variables] for information that:
** is mostly used by Bonita
** has meaning after a process instance is archived
** is used at several places in the process
** is read by a process to orientate its flow
** is shared across several process instances
** is displayed in an application page
* Task-level xref:specify-data-in-a-process-definition.adoc[process variables] for:
* Task-level xref:ROOT:specify-data-in-a-process-definition.adoc[process variables] for:
** intermediate computation results (for example a connector result to be used as input of the next connector)
** information that is private to the process, not used elsewhere in the application
* Pool-level xref:specify-data-in-a-process-definition.adoc[process variables] for information that:
* Pool-level xref:ROOT:specify-data-in-a-process-definition.adoc[process variables] for information that:
** can be read by the process to orientate its flow
** can be used at several places in the process
** is private to the process, not used elsewhere in the application
* External databases, with xref:connectivity-overview.adoc[connectors], for information that:
* External databases, with xref:ROOT:connectivity-overview.adoc[connectors], for information that:
** is used by multiple applications besides Bonita
Key benefits of using business data:
......@@ -30,9 +30,9 @@ Key benefits of using business data:
* Improved performance compared with process variables or external databases
* Easier application maintenance
An application page accesses business data using the xref:bdm-api.adoc[bdm REST API]. A page also contains page xref:variables.adoc[variables], which have no meaning outside the page.
An application page accesses business data using the xref:ROOT:bdm-api.adoc[bdm REST API]. A page also contains page xref:variables.adoc[variables], which have no meaning outside the page.
The data that is passed from a form to a process is defined using a xref:contracts-and-contexts.adoc[contract]. Define a contract for process instantiation and for each human task.
The data that is passed from a form to a process is defined using a xref:ROOT:contracts-and-contexts.adoc[contract]. Define a contract for process instantiation and for each human task.
These contracts are part of the process definition.
A form has access to business data and documents using the xref:contracts-and-contexts.adoc[context] and the xref:rest-api-overview.adoc[REST API].
A form also contains form xref:variables.adoc[variables], which have no meaning outside the form.
A form has access to business data and documents using the xref:ROOT:contracts-and-contexts.adoc[context] and the xref:rest-api-overview.adoc[REST API].
A form also contains form xref:ROOT:variables.adoc[variables], which have no meaning outside the form.
......@@ -14,17 +14,17 @@ Click on the menu *Help* \-> *About* \-> *Installation Details*
[discrete]
==== Others
xref:ui-designer-dependencies.adoc[List of UI Designer dependencies]
xref:ROOT:ui-designer-dependencies.adoc[List of UI Designer dependencies]
xref:bonita-data-repositories-dependencies.adoc[List of Data-Repository dependencies]
xref:ROOT:bonita-data-repositories-dependencies.adoc[List of Data-Repository dependencies]
== Runtime
xref:bonita-engine-dependencies.adoc[List of Engine dependencies]
xref:ROOT:bonita-engine-dependencies.adoc[List of Engine dependencies]
xref:portal-js-dependencies.adoc[List of Portal-js dependencies]
xref:ROOT:portal-js-dependencies.adoc[List of Portal-js dependencies]
xref:react-page-dependencies.adoc[List of React pages dependencies]
xref:ROOT:react-page-dependencies.adoc[List of React pages dependencies]
xref:bonita-web-dependencies.adoc[List of Bonita web dependencies]
\ No newline at end of file
xref:ROOT:bonita-web-dependencies.adoc[List of Bonita web dependencies]
\ No newline at end of file
......@@ -7,15 +7,15 @@ blabla
[.card.card-index]
--
xref:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
xref:ROOT:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
--
[.card.card-index]
--
xref:xxg.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
xref:ROOT:xxg.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
--
[.card.card-index]
--
xref:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
xref:ROOT:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
--
......@@ -7,15 +7,15 @@ blabla
[.card.card-index]
--
xref:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
xref:ROOT:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
--
[.card.card-index]
--
xref:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
xref:ROOT:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
--
[.card.card-index]
--
xref:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
xref:ROOT:xx.adoc[[.card-title]#xx# [.card-body.card-content-overflow]#pass:q[TODO]#]
--
......@@ -7,25 +7,25 @@ Learn how Bonita Platform can be extended to suit your needs.
== Possible Extensions
[.card.card-index]
--
xref:connector-archetype.adoc[[.card-title]#Connectors# [.card-body.card-content-overflow]#pass:q[Discover how to create your custom connectors]#]
xref:ROOT:connector-archetype.adoc[[.card-title]#Connectors# [.card-body.card-content-overflow]#pass:q[Discover how to create your custom connectors]#]
--
[.card.card-index]
--
xref:actor-filter-archetype.adoc[[.card-title]#Actor Filters# [.card-body.card-content-overflow]#pass:q[Discover how to create your custom actor filters]#]
xref:ROOT:actor-filter-archetype.adoc[[.card-title]#Actor Filters# [.card-body.card-content-overflow]#pass:q[Discover how to create your custom actor filters]#]
--
[.card.card-index]
--
xref:customize-living-application-theme.adoc[[.card-title]#Themes# [.card-body.card-content-overflow]#pass:q[Discover how to create your custom living application themes]#]
xref:ROOT:customize-living-application-theme.adoc[[.card-title]#Themes# [.card-body.card-content-overflow]#pass:q[Discover how to create your custom living application themes]#]
--
[.card.card-index]
--
xref:rest-api-extension-archetype.adoc[[.card-title]#REST API Extensions# [.card-body.card-content-overflow]#pass:q[Discover how to create your REST API Extensions]#]
xref:ROOT:rest-api-extension-archetype.adoc[[.card-title]#REST API Extensions# [.card-body.card-content-overflow]#pass:q[Discover how to create your REST API Extensions]#]
--
[.card.card-index]
--
xref:custom-widgets.adoc[[.card-title]#Custom Widgets# [.card-body.card-content-overflow]#pass:q[Discover how to create your custom widgets]#]
xref:ROOT:custom-widgets.adoc[[.card-title]#Custom Widgets# [.card-body.card-content-overflow]#pass:q[Discover how to create your custom widgets]#]
--
......@@ -7,15 +7,15 @@ blabla
[.card.card-index]
--
xref:actors.adoc[[.card-title]#How to 1# [.card-body.card-content-overflow]#pass:q[TODO]#]
xref:ROOT:actors.adoc[[.card-title]#How to 1# [.card-body.card-content-overflow]#pass:q[TODO]#]
--
[.card.card-index]
--
xref:actor-filtering.adoc[[.card-title]#How to 2# [.card-body.card-content-overflow]#pass:q[TODO]#]
xref:ROOT:actor-filtering.adoc[[.card-title]#How to 2# [.card-body.card-content-overflow]#pass:q[TODO]#]
--
[.card.card-index]
--
xref:organization-overview.adoc[[.card-title]#How to 3# [.card-body.card-content-overflow]#pass:q[TODO]#]
xref:ROOT:organization-overview.adoc[[.card-title]#How to 3# [.card-body.card-content-overflow]#pass:q[TODO]#]
--
......@@ -8,22 +8,22 @@ Learn how to get the most out of the Bonita Platform and all of its components.
[.card.card-index]
--
xref:what-is-bonita-index.adoc[[.card-title]#What is Bonita?# [.card-body.card-content-overflow]#pass:q[A useful overview (our purpose, artifacts to create, platform architecture)!]#]
xref:ROOT:what-is-bonita-index.adoc[[.card-title]#What is Bonita?# [.card-body.card-content-overflow]#pass:q[A useful overview (our purpose, artifacts to create, platform architecture)!]#]
--
[.card.card-index]
--
xref:release-notes.adoc[[.card-title]#What's new in {bonitaVersion}# [.card-body.card-content-overflow]#pass:q[At a glance: new values, improvements, changes, and bug fixes]#]
xref:ROOT:release-notes.adoc[[.card-title]#What's new in {bonitaVersion}# [.card-body.card-content-overflow]#pass:q[At a glance: new values, improvements, changes, and bug fixes]#]
--
[.card.card-index]
--
xref:project-best-practices-index.adoc[[.card-title]#Project best practices# [.card-body.card-content-overflow]#pass:q[Helpful experience we share for the good of your project]#]
xref:ROOT:project-best-practices-index.adoc[[.card-title]#Project best practices# [.card-body.card-content-overflow]#pass:q[Helpful experience we share for the good of your project]#]
--
[.card.card-index]
--
xref:api-index.adoc[[.card-title]#Bonita API# [.card-body.card-content-overflow]#pass:q[REST API, Java API, your own API]#]
xref:ROOT:api-index.adoc[[.card-title]#Bonita API# [.card-body.card-content-overflow]#pass:q[REST API, Java API, your own API]#]
--
[.card-section]
......@@ -31,17 +31,17 @@ xref:api-index.adoc[[.card-title]#Bonita API# [.card-body.card-content-overflow]
[.card.card-index]
--
xref:studio-installation.adoc[[.card-title]#Studio installation# [.card-body.card-content-overflow]#pass:q[How to download and install Bonita Studio]#]
xref:ROOT:studio-installation.adoc[[.card-title]#Studio installation# [.card-body.card-content-overflow]#pass:q[How to download and install Bonita Studio]#]
--
[.card.card-index]
--
xref:getting-started-index.adoc[[.card-title]#Getting Started Tutorial# [.card-body.card-content-overflow]#pass:q[A 9-step journey to create a simple Automation Project]#]
xref:ROOT:getting-started-index.adoc[[.card-title]#Getting Started Tutorial# [.card-body.card-content-overflow]#pass:q[A 9-step journey to create a simple Automation Project]#]
--
[.card.card-index]
--
xref:runtime-installation-index.adoc[[.card-title]#Runtime installation# [.card-body.card-content-overflow]#pass:q[Install and configure a Bonita Runtime to bring your project to life]#]
xref:ROOT:runtime-installation-index.adoc[[.card-title]#Runtime installation# [.card-body.card-content-overflow]#pass:q[Install and configure a Bonita Runtime to bring your project to life]#]
--
[.card-section]
......
......@@ -34,7 +34,7 @@ Such data can either be automatically stored in a database dedicated to business
A connector is a link between a process and an external information system such as a database or information service. A number of standard connectors are provided, and you can create additional connectors if required. +
Separating the connector configuration and implementation from the process means it is easier to update or replace the connector without having to modify the process. You can use the same connector in more than one process. +
See the xref:connectivity-overview.adoc[Connectivity overview] for details.
See the xref:ROOT:connectivity-overview.adoc[Connectivity overview] for details.
== Organization
......@@ -43,16 +43,16 @@ Typically, the organization corresponds to the hierarchy of teams within your bu
If your clients and suppliers have access to your processes, those users must also be included in the organization. +
You can also feed the Bonita Runtime by synchronizing with an external LDAP directory. +
During process modelling, you need to create a draft organization in Bonita Studio with the main entities (groups, roles) to map it to process actors. +
See the xref:organization-overview.adoc[Organization overview] for details.
See the xref:ROOT:organization-overview.adoc[Organization overview] for details.
== Actors
An actor is a placeholder specified in the process definition for the users. Using an actor instead of specifying real people directly makes the process definition more flexible: when the list of users changes, you change only the process configuration, which can be done while the process is running. You can also use the same process definition with completely different sets of users, for example, if a service business sells a process to several clients. +
Making the connection between the actor definition and the set of users is called actor mapping. +
See xref:organization-management-in-bonita-bpm-studio.adoc[Configure a test organization] and xref:actors.adoc[actors] for details.
See xref:ROOT:organization-management-in-bonita-bpm-studio.adoc[Configure a test organization] and xref:actors.adoc[actors] for details.
== Environments and parameters
An environment (available in the Bonita Enterprise, Performance, Efficiency, and Teamwork editions) is the context in which a process will run. +
There are three standard environments: Local, Qualification, and Production. You can define additional environments that are useful when designing and deploying a process for your business. +
A parameter is a piece of information in a process that has a value specific to the environment. See xref:environments.adoc[Environments] and xref:parameters.adoc[Parameters] for more details.
A parameter is a piece of information in a process that has a value specific to the environment. See xref:ROOT:environments.adoc[Environments] and xref:parameters.adoc[Parameters] for more details.
......@@ -10,7 +10,7 @@ Each application can have its own layout.
There is an example of layout in Bonita Applications, the "Bonita Layout".
Layouts are xref:resource-management.adoc[added, exported, edited, and deleted] as resources in Bonita Applications.
Layouts are xref:ROOT:resource-management.adoc[added, exported, edited, and deleted] as resources in Bonita Applications.
== Use in applications
......@@ -21,12 +21,12 @@ In a Non-Production or Production environment, a layout is imported as a .zip ar
== Live update
xref:live-update.adoc[Live update] allows the Administrator to update one element of the application in a situation of emergency.
xref:ROOT:live-update.adoc[Live update] allows the Administrator to update one element of the application in a situation of emergency.
=== Edit the layout
You can xref:resource-management.adoc]#modify[edit the content of a layout] by installing a new version.
You can xref:ROOT:resource-management.adoc]#modify[edit the content of a layout] by installing a new version.
=== Modify the pages in an application
You can xref:applications.adoc]#define-navigation[link another layout to an application] in the application descriptor.
You can xref:ROOT:applications.adoc]#define-navigation[link another layout to an application] in the application descriptor.
......@@ -5,12 +5,12 @@ Learn how to migrate a Bonita Platform from an older version to a newer version.
== Migrating your platform to the new version
You can automatically xref:migrate-from-an-earlier-version-of-bonita.adoc[migrate the platform from an earlier version of Bonita]. You cannot migrate your platform from a version earlier than 6.0.2.
You can automatically xref:ROOT:migrate-from-an-earlier-version-of-bonita.adoc[migrate the platform from an earlier version of Bonita]. You cannot migrate your platform from a version earlier than 6.0.2.
After migration, a process continues to run unchanged. You can modify the process definition later to take advantage of the new features in this version of Bonita.
== Migrating your Bonita Studio
To migrate to a newer version of Bonita Studio, install the new version using the xref:bonita-bpm-studio-installation.adoc[Studio installer wizard] for your operating system.
To migrate to a newer version of Bonita Studio, install the new version using the xref:ROOT:bonita-bpm-studio-installation.adoc[Studio installer wizard] for your operating system.
If you want to keep the artifacts in your workspace, select the option to migrate your workspace.
WARNING: if you do not migrate your workspace, or if you use the OS-independent archive to install the new Bonita Studio,
......@@ -25,4 +25,4 @@ Note: you cannot import a process definition `.bos` file into a version of Bonit
that was used to create it.
A process definition created using a version 6.x of Bonita, or using 6.x forms or case overview pages, needs to have its task and instantiation forms modified in a previous version of
Bonita (7.0.0 to 7.7.4) before migrating to this version. Bonita Studio 7.8 and above can't import these forms, which may result in data loss or process malfunctions. For more details see xref:migrate-from-an-earlier-version-of-bonita.adoc[platform migration].
Bonita (7.0.0 to 7.7.4) before migrating to this version. Bonita Studio 7.8 and above can't import these forms, which may result in data loss or process malfunctions. For more details see xref:ROOT:migrate-from-an-earlier-version-of-bonita.adoc[platform migration].
......@@ -8,7 +8,7 @@ For example, you cannot have two variables called `beanCounter` in a diagram, ev
You could, however, have a variable called `beanCounter` and an actor called `beanCounter`.
NOTE: Variables are not shared between Studio and UI Designer. Furthermore, in the UI Designer, variables are not shared between pages.
For information about to use variables in the UI Designer, go to xref:variables.adoc[Variables].
For information about to use variables in the UI Designer, go to xref:ROOT:variables.adoc[Variables].
Even in a relatively simple process, the number of names quickly becomes large. Adopting a naming strategy improves the readability and maintainability of your processes, and makes it easier to reuse elements. We propose the following best practises.
......
......@@ -16,11 +16,11 @@ In practice, this includes:
The Administrator has the rights to:
* xref:import-export-an-organization.adoc[install an organization exported from Bonita Studio]
* xref:import-export-an-organization.adoc[export an organization from the Bonita Install / Export Organization page]
* create, update, and delete groups, from the xref:admin-application-groups-list.adoc[Administrator application]
* create, update, and delete roles, from the xref:admin-application-roles-list.adoc[Administrator application]
* xref:ROOT:import-export-an-organization.adoc[install an organization exported from Bonita Studio]
* xref:ROOT:import-export-an-organization.adoc[export an organization from the Bonita Install / Export Organization page]
* create, update, and delete groups, from the xref:ROOT:admin-application-groups-list.adoc[Administrator application]
* create, update, and delete roles, from the xref:ROOT:admin-application-roles-list.adoc[Administrator application]
* create, update, and manage users and manage memberships, from the link:admin-application-users-list.adoc[Administrator application]
When you first launch the Bonita Administrator Application in a Production environment, there is *no default organization*.
You must xref:first-steps-after-setup.adoc[create a user and map it to the Administrator profile]. This user can than create and manage the organization.
You must xref:ROOT:first-steps-after-setup.adoc[create a user and map it to the Administrator profile]. This user can than create and manage the organization.
......@@ -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:release-notes.adoc#_new_bonita_applications[converted into Living Applications], using Bonita Layout and Bonita Theme
- xref: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: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
- 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
......
......@@ -13,9 +13,9 @@ You can test some process components individually:
* Expressions: use the *_Evaluate_* feature of the Expression editor.
You can run the process locally, launching it from Bonita Studio without first deploying it to Bonita Applications.
You must xref:configure-a-test-organization.adoc[create a test organization]
and xref:configuring-a-process.adoc[configure a process] before you can
xref:run-a-process-from-bonita-bpm-studio-for-testing.adoc[run a process from Bonita Studio].
You must xref:ROOT:configure-a-test-organization.adoc[create a test organization]
and xref:ROOT:configuring-a-process.adoc[configure a process] before you can
xref:ROOT:run-a-process-from-bonita-bpm-studio-for-testing.adoc[run a process from Bonita Studio].
In addition to functional testing during development, we recommend that you monitor the system load. This will help evaluate the performance, so you can make your process efficient.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment