We want to begin our chapter, Creating a Process App, with a basic explanation of how Big Process Design

and Big Process Execution are related to each other or, let's say, work together. Big Process Design is the
module within the Big Platform that you use to flowchart your processes. If you are not familiar with Big
Process Design yet, we highly recommend our First Steps training you can also find in this training hub.

In Big Process Design, you can flowchart a business process without any regards to executing the process.
However, the diagram in Big Process Design is the basis for the case-based execution of your documented
process as a process app. Any workflow specification or enrichment of the process with user forms, decisions
or third-party integration will be done directly in the model diagram in Big Process Design.

So let's get back to Big Process Design. Actually, there are no more than four steps necessary to get your
process model ready and transformed into a process app. Step 1 is simply the process modeling. So, if you
would like to execute an already existing process, you have yet completed your first step. Great! In the second
step, we open the diagram attributes via the small i, our details. Please scroll down a little. For the third step,

please look for the attribute group Automation. Here you will find a checkbox for executable process. Now
please activate this checkbox. The fourth and last step is the check-in of our process. After a few seconds, both
a play button in Big Process Design and a process app in Big Process Execution will appear. This is all the
magic needed to create a process app. What I would like to add at this point is that it is not necessary to release
a process before testing the process app.

That means you do not need to complete the release workflow in Big Process Design in order to test your
process app. The dry run of a case can be done even before the release, thanks to different stages in Big
Process Execution. By clicking on the play button that appears after checking in your process, a new browser
tab will be opened with the development or studio environment of Big Process Execution.

Now you can start testing immediately. In order to give you a bit more background, let's jump directly to the
next lesson, where we will discuss the differences between the three stages in Big Execution. Similar to our
main tool, Big Process Design, Big Process Execution also provides different stages. We always encourage all
our customers, and now of course you as well, to use the staging system in order to optimize and holistically
test your process apps before officially publishing both the diagram and the process app at the same time.

The staging system consists of three stages, very similar to Big Process Design. Again, if you're not yet
familiar with Big Process Design, we highly encourage you to do so. Their respective free training is linked
below. Okay, let's take a closer look. The development stage,

Studio. When a diagram was marked as an executable process in Big Process Design, a corresponding process
app will appear immediately in the studio. So the content of the Big Execution Studio stage is 100% equivalent
to the diagram version from Public Workspace in Big Process Design. Using the play button in the Design's
Public Workspace will redirect you to the website, tenant name, process execution, studio. The test stage.

Once the publication or release workflow for a diagram in Big Process Design was started, a version of this
diagram will be available in the preview stage. Same in Big Process Execution. Here we will find a
corresponding process app in the test stage of Big Process Execution. So the preview stage of Big Design is
equal to the test stage of Big Execution. As a reviewer in Big Process Design, you may also use the play button
to test the process app.

Your redirection will now lead you to the following link. Tenant name, process execution, test. Our last and
final stage for execution is the productive stage, app. Only fully approved process apps will be operationally
used in the app stage of Big Process Execution. The process apps we will find here are now 100% based on their
published equivalents of the respective diagrams available in the publication stage of Big Process Design.

Thus, process apps in the productive stage of Big Execution are equal to diagrams in the publication stage of
Big Design. If you use the design's reader role to execute your processes via the play button, you will always be
forwarded to a website with tenant name, process execution, app.

In our last lesson of this course, we will focus on the actual automation using the process extended BPM tool
evaluation we already know. With one-click automation, we have created an easy entry point into process
automation as users can easily turn their process models into executable workflows with just, as the name
already suggests, one mouse click. Let's apply the steps we have already learned to automate the process.
 Please open the diagram attributes, scroll down to the automation group, mark the process as executable, and
check it in again. Publish the process directly since we have already tested it extensively beforehand. Wait a
second until a process app has been created in the backend and then use the play button in the publication of Big
Process Design. Clicking on the play button will automatically take us to the start form of our new case in the
app environment of Big Execution.

Voila! That's our one-click automation for the extended BPM tool evaluation. The start form allows us to
define which employees are involved in the process. This is the easiest level of automation where the system is
basically the pilot directing which employee should do which task.

Considering the minimal effort you have to put into it, this is already great. However, you can easily do more.
The next step will be to use additional automation features for this process. You can, for example, make use of
variables, extended forms, or email templates. So let's take a sneak peek into how that would look like and fast
forward through the automation process. Automation potential can be found in the email communication
between the employee and the supervisor,

which will then be sent automatically. Or an automated gateway. The extended forms allow us to, for example,
gather information early in the process. This information is processed and stored in so-called variables and can
later be used, as in this example, for a fully automated gateway.

Variables add a whole new layer to the intelligent execution of a process. Information does not have to be
worked with immediately. It can be saved, combined with other data through sophisticated operations, as you
know it from spreadsheet calculations, and then, later on, used in the process to send an email or, as in this
case, just decide about the way the case should go. There are many more automation functions like scheduled
events via a timer or script tasks which we can only briefly introduce here in this training.

Scheduled events can be used for processes that are recurring monthly, quarterly, or annually. Script tasks
give you the opportunity to go from no-code to low-code automation in selected areas of your process app. It
supports common programming languages like JavaScript and gives you endless possibilities to work
dynamically with the process or case variables.

And there are many more extended automation possibilities. How exactly we use these will be explained in
detail in another training.