Prerequisites

To run the application, the following prerequisites must be met:

• Docker Desktop version 4.29.0 or higher
• DNS redirection of "authority" to 127.0.0.1
• Node.js version 12.22.9 or higher
• npm version 8.8.1 or higher
• Git in the latest version
• (Optional) Postman (to use the templates included in the project)
• (Optional) 5minds Studio version 1.16.1 or higher (to observe process execution)

The DNS redirection can be easily achieved by adding an entry to the host file of the operating system used. Even though the entire application runs in Docker, these prerequisites must be met because a Docker image is not hosted in a container registry and will be built upon first start.

Installation and Starting the Application

• git clone https://github.com/Ainges/BA
• Navigate to ./processSuite
• Install the Node.js packages:
  • npm install in ./processSuite/apps/processSuite/frontend
• Start the application by running: docker compose up --build in ./processSuite

Initializing Profile Pictures for Created Users

To display profile pictures for the sample users, MinIO needs to be configured first:

1. Access MinIO at http://localhost:9001 with the following credentials:
   • Username: admin123456
   • Password: admin123456
2. Navigate to Buckets > Create Bucket
3. Create a bucket named profilepictures.
4. Select the bucket and set the Access Policy to Public.
5. In the Object Browser menu, select profilepictures.
6. Click on the upload button (top right) > Upload file.
7. Choose and upload all images from ./integration/config/minio.

However, this is only necessary once. By using volumes, the configuration survives a deletion of the container.

Usage

The 5minds Portal is available at: http://localhost:8082. The backend initializes some users at the start. To easily go through the process, you can log in with the following credentials:

• Username: admin
• Password: admin

In the top left corner, there is a bell icon. Clicking on the bell will bring up the task list to interact with the application. Tasks can be assigned in the Process Engine in two ways:

• Direct assignment to the task via UserID
• Through the Swimlane

The admin user can access all tasks, even if they are assigned to a specific user, as is the case in the second phase of the onboarding process. Here, tasks are directly assigned to the user ID of the new employee. For this reason, a warning is displayed in the UI when the task is activated by the admin user, but it does not cause any issues.

The 5minds Authority is accessible at http://authority:11560. (Hence the DNS redirection)

Starting the Process

An instance of the onboarding process can be started via a REST request to the backend. It is recommended to import the Postman Collection "OnboardingTop PDA" found in ./postmanCollection. Alternatively, you can send an HTTP POST request to http://localhost:8080/onboarding/top/employeeHasSignedContract with the following body:

{
  "first_working_day": "2024-08-01",
  "hours_per_week": 40,
  "first_name": "Max",
  "last_name": "Mustermann",
  "private_email": "[email protected]",
  "position": "HR",
  "birth_date": "2000-08-01",
  "employment_status": "Vollzeit",
  "postal_address": "Musterstraße 12, 12345 Musterstadt"
}

Monitoring the Process Execution

1. Start 5minds Studio.
2. Connect Studio to the engine:
   • In the "Connections" tab, click the plus sign and enter the engine URL (http://localhost:8080).
3. The engine you just entered should now be listed under "Connected Engines" alongside the Studio internal engine.
4. Select the newly created instance and expand it if necessary.
5. All process instances are listed under "Process Instances."
6. By clicking the folder icon in the row of the respective instance, you can trace the process flow.

Monitoring E-Mail

The emails that are created during the process can be accessed via http://localhost:3300. This is necessary at the latest during the relocation process, as the process flow comes to a standstill here until a selection has been made.

Final Note

• The time events all have a short duration entered to test the application. How to achieve a real configuration is noted in each documentation field.
• To ensure that the current process models are executed, you can open the path ./processSuite/processes in the 5minds Studio and redeploy all process models to the engine via Run > Deploy Solution.
• Despite the note in the docker compose file that the integration service should wait for ActiveMQ Artemis and the engine, it can occasionally start too quickly and fail to reach the engine or ActiveMQ Artemis. This results in the initial users not being created. To fix this, simply restart the container while the other services are already running.