= Bonita User Application
:description: This pages describes the Bonita User Application: its values, how to access it, its differences with the _User_ profile of Bonita Portal, and the details of its features. +

This pages describes the Bonita User Application: its values, how to access it, its differences with the _User_ profile of Bonita Portal, and the details of its features. +
The Bonita User Application allows anyone with the _User_ profile to view tasks and do them, get information and add comments on cases, get a list of processes to start.

== Value

Bonita Portal is deprecated and will be removed in a future Bonita release. +
We believe that Bonita Applications give our users much more freedom for customization:

* Their menus can be customized compared to provided Portal profiles, by adding or removing pages, while still keeping the mapping with the _User_ profile
* Portal pages that have been re-created with the UI Designer have more features and/or features improvements
* These pages can also be modified in the UI Designer to fit precise users' needs.

We also want to remove the last parts of the platform that were still built with Google Web Toolkit framework; as useful as it has been when building Bonita Portal, we now find some limitations.

== Access during Implementation

To get the application when you are implementing your Bonita project, go to the "Resources" tile of the *Studio Welcome page*, and click on "Import Bonita User Application".

image::images/UI2021.1/studio-get-application.png[Get application from Studio]

You can also get it from our https://github.com/bonitasoft/bonita-user-application/[User Application GitHub repository]. +
There are two ways to get the .bos file. You can either get it from the _Releases_ on the right or by cloning the repository of your choice and building it using maven. +
Building the repository will create a .bos file in the `target` folder. You can import this one into the development environment.
 +
Using this method is also useful if you want to get an older version of an application or if you need a weekly version with a potential bugfix.

After Studio validation, the application is imported or cloned; you can view its content in the project explorer, deploy it, and open it.

== Access in pre-Production and in Production

To deploy the applications into a bundle or the Cloud, you can use xref:{bcdDocVersion}@bcd::livingapp_manage_configuration.adoc[Bonita Continuous Delivery]'s xref:{bcdDocVersion}@bcd::bcd_cli.adoc[CLI] (Subscription editions using BCD).
Alternatively, you can deploy an application by importing all its components in the following order:

* Organization then profiles
* API extensions then pages, layout, themes
* Business Data Model then processes
* Application descriptor

== Similarities and differences with _User_ profile of Bonita Portal

On top of the application values, here are the similarities and differences between application and Portal for the provided pages:

* All pages previously created using Google Web Toolkit framework have been recreated with Bonita UI Designer. They can be customized in the UI Designer. They come with the Admin Application you download from Bonita Studio.
* All pages previously created in other technologies have been wrapped as custom pages. They cannot be customized in the UI Designer. Since they cannot be imported in a .bos archive, they do not come with the Admin Application you download. Instead, they come as provided resources. You can find them in the "Resources" tab of the application.

Now, in details:

* _Processes_: same as in Bonita Portal.
* _Cases_:
 ** Case list: recreated with the UI Designer. It allows a much better display of search keys.
 ** Case details: recreated with the UI Designer.
* _Tasks_: same as in Bonita Portal.

== Create your own User application from ours

. Have all your custom pages ready, either imported in Bonita UI Designer or Bonita Studio.
. Open our UI Designer pages to customize them.
. In Bonita Studio, go to the "Project explorer" on the left and double click on the "bonita-user-application.xml" application descriptor.
. In the editor, rename the pages, change the order in the menu, remove the pages you do not need, add yours in the menu, or as orphan pages accessed through navigation from another page.
+
[WARNING]
====
Make sure our "details" pages are always used as orphan pages, as they need some parameters (usually just an ID) to be passed in the URL by a list or another page to show any content.
====
+
. To add other Bonita provided pages, open the portal from the coolbar, switch to the Administrator profile, and look in the "Resources" page, filtered by pages.

[NOTE]
====

Once a page has been customized, or when the User application has been customized, it is no longer supported. +
But you can reach one of our Professional Services team member to help you develop or maintain it.
====

== Login and sign out

To know more, go to the xref:log-in-and-log-out.adoc[dedicated page].

== Language selection

To know more, go to the xref:languages.adoc[dedicated page].

== Navigation between applications

To know more, go to the xref:navigation.adoc[dedicated page].
