This tutorial introduces you to the essentials of Jmix by walking you through building a simple full-stack web application. It covers the entire development process, from data modelling to creating UI and managing access rights.
To get the most out of this tutorial, you should be familiar with Java and relational databases.
You will build an application that helps to automate the onboarding process. The company is organized into departments. Each department has an HR manager, who oversees the onboarding, registers new employees and sets up their onboarding steps. A new hire gets the list of required steps and marks them done.
The complete application source code is available in the jmix-framework/jmix-onboarding GitHub repository. We recommend following instructions of this tutorial to create the application step by step, but if you want to just investigate the completed example, clone the repository and open it in Jmix Studio as described in the Opening Existing Project section.
Below we will take a closer look at the data model, user roles and get familiar with the user interface that we are going to build.
Creating an application with Jmix often starts from designing the data model. Let’s look at the model of the sample onboarding application.
The central entity in the application is
User. It contains the user login name and other attributes, as well as their joining date and the onboarding process status. The user belongs to a department, which is designated by the link to the
Deparment entity defines a company department. It has a name and an HR manager - a user who registers new employees belonging to the department.
Step entity defines an onboarding step like "Safety briefing", "Fill in profile", etc. A step has a name and a duration - a period of time in days after joining the organization when the employee should complete the step. The
sortValue attribute sets the order of the step in a list of steps.
UserStep entity is an onboarding step of a particular user. It links the
Step entities and adds
completedDate attributes. The due date is calculated as a user’s joining date plus the step duration. The completed date is set to the current date when the user marks the step done.
The sample application supports the following user roles:
Administrators have full control of the application. They see all users, set up onboarding steps, departments and assign HR managers.
HR Managers register new employees withing their departments and start the onboarding process by generating steps for a particular user. They can also track the onboarding process of their department employees.
Employees can see their own onboarding steps and mark the completed steps.