Low-Code Designer > Apps > What is an App? / Main app process

Main app process

QuickBPM apps can be aligned with two kinds of processes. The former is related to the app and is called an associated process. The latter is called the main app process; it is associated with the app as well but has some specifics that will be described below.

The main app process is always created at the same time as the app. This allows you to conveniently configure the app context, forms, and statuses right from the process designer while you build a flowchart.

The main process starts when a user creates a new app item. For example, when a user adds a new order, the "Order handling" process starts immediately. You may have multiple processes associated with the Order app, for instance, "Reclamations", "Returns" but when you create a new order in the app, it is the main app process that will start.

How to create the main app process

There are two ways to create the main process:

1. In the main menu of a workspace, click the Add button and select the Create option.

0.png

In the pop-up, write down the name of the process and click the Next button. The process designer page will immediately open. Here you can draw and set up the app process; the app itself will be created automatically. Read more about how to build a process in the article Business process modeling.

2. In the main menu of the workspace, click the Add button, then select More > Create.

1.png

You will see a pop-up that allows you to quickly create an app. Enter the app name and select other settings. At the bottom of the form, tick the Create associated business process checkbox. Then tick the checkbox Run after creating a new app item.

2.png

Specifics of the main app process

In the designer, on the Context tab, as well as on the forms of the start event and tasks, a switch will appear, allowing you to work with both process variables and app properties.

Switch to the process context if you want to work with variables that are directly related to the business process but not relevant to the app. As an example, think about such variables as the initiator, comment on a task, executor of a swimlane or other workspace app.

Select the app context, if you want to add or remove properties that are relevant exclusively to the app. The property that you create in the designer will be added to the creation, viewing, and editing forms of an app item.

4.png

To add new properties to the app context, go to the Context tab, make sure that the switch is set to work with app variables and click the +Add button.

Similarly, you can create new app properties in the settings of the start event or task. To do this, select an event or a task and go to the Form tab. You will see the same switch that allows you to choose either the process context or that of the app.

начало внимание

If you remove a property in the designer, it will be also removed from the app creation, viewing and editing forms.

конец внимание

It is important to remember that the start event in the main process is not only used to initiate the process. When you add a new property to the start event form, it is automatically added to the item creation, editing, and viewing forms. Each property is a field that an employee will have to fill out when creating a new app item.

3.png

If you create a new property on the task form, it will appear on the viewing and editing forms of the app item.

To sum up, the main app process allows you to access the app context directly from the process designer. You can create new properties, edit them as well as set up item forms without leaving the designer page.

The table below shows where the new property will appear depending on how initially it was created: on the Context tab, on the start event form or on a task form.

Where the property is initially created:

Where the new property will appear:

App context

Creation form

Viewing form

Editing form

Context tab

+

Start event

+

+

+

+

Task

+

+

+

Otherwise, the main process is configured and works just like any process associated with the app. For example, you can configure statuses directly from the designer without switching to app settings.

We recommend that you use the main process to describe how a new app item should be handled. Please note that if you created an app and its main process, you won't be able to unbind them or replace this process with another one.