Jmix Bookstore

Jmix Bookstore is a comprehensive example application built with Jmix - a full-stack framework for business applications. It showcases the operations of a retail business that specializes in shipping books across the US.

The online demo of the Jmix Bookstore is available at https://demo.jmix.io/bookstore.

Table of Content

• About the Example
  • Technical Details
  • Implementation Effort
  • Add-ons
  • Running Locally
  • Building Locally
  • Performance Testing
• Application Overview
  • Sales
    • Placing Customer Orders
  • Order Fulfillment
    • Confirming Customer Orders
    • Perform Fill-up requests
  • Procurement
    • Place Supplier Orders
    • Managing Product Catalog
  • IT
    • Managing System Access
    • Master Data Management
• Implementation Details
  • Domain Model
  • Security
  • Internationalization
  • Multitenancy
  • BPM
  • Email
  • Reports
  • Notifications
  • Background Tasks: Quartz

About the Example

The Jmix Bookstore example application is a comprehensive example of what advanced capabilities Jmix provides for application developers. Compared to the Jmix Petclinic example application, the Bookstore is way bigger, covers more advanced use-cases and shows the capabilities of various add-ons (free as well as premium) and their integration into a Jmix application.

Technical Details

Jmix Bookstore runs using:

• Jmix 2
• Spring Boot 3
• Java 21

Application Size

To give an understanding of the size of the application, here are some rough statistics:

• 20 entities
• 8 enums
• 36 UI views
• 6 user roles
• 10 business processes

Production Code

• 150 Java classes
• 14.000 lines of code (Java + XML)

Test Code (rough statistics)

• 100 test cases
• 130 Java classes (test + test support)
• 6.000 lines of code

Implementation Effort

One important decision factors for implementing custom software is time to market / developer efficiency. Jmix aims to provide a fast way of delivering high quality backoffice style applications.

The Implementation of the version 1.0 of the Bookstore example was done in a 1.5 person-months by a single senior Java developer containing the following areas:

• conceptual meetings (5%)
• requirements gathering (5%)
• domain modelling (10%)
• data model implementation (10%)
• custom business logic implementation (15%)
• test automation (20%)
• UI development (20%)
• UI styling / theming (10%)
• documentation (5%)

Besides this little overall effort, the resulting application of the Jmix Bookstore has the following important characteristics:

1. high resulting quality (test automation, modularisation)
2. long term maintainable (due to test automation, modularisation, widely used base technologies like Spring Boot, JPA and Vaadin)
3. good (out-of-the-box) user experience
4. broad functionality coverage
5. extensible for users without development effort (like custom filter selection, user-created reports, user-created BPM processes)

Add-ons

The application also features various add-ons available on the Jmix Marketplace:

• Multitenancy
• Email
• Reports
• Data Tools
• Quartz
• BPM (commercial)
• Notifications (commercial)
• Maps (commercial)
• Pessimistic Locking
• Grid Export Actions
• German Translation

Running Locally

You can run the containerized application locally as follows:

• Make sure you have Docker installed
• Download docker-compose.yml file to a local folder
• Open a terminal in that directory and run

  docker-compose up
  

• For using LocaitionIQ to calculate routes and locations, set
  BOOKSTORE_LOCATIONIQ_API_KEY
  environment variable to your API key in your terminal or globally in the operating system before starting the containers.

Building Locally

The application uses several commercial add-ons, so you need an active Jmix Enterprise subscription to build the application locally. You can also do it with the trial subscription by following the steps below.

First, get the

sample application. You may download it from your account page at https://store.jmix.io/.

Next, copy the

directory from the

jmix-commercial-addons-demo

sample project to the root of the

jmix-bookstore

project.

After that, modify the

file of the

jmix-bookstore

project: add the repository with the

trial-repository

directory.

repositories {
    mavenCentral()
    maven {
        url 'https://global.repo.jmix.io/repository/public'
    }
    if (file('trial_repository').exists()) {
        maven {
            url "file://${project.projectDir}/trial_repository"
        }
    } else {
        maven {
            url = 'https://global.repo.jmix.io/repository/premium'
            credentials {
                username = rootProject['premiumRepoUser']
                password = rootProject['premiumRepoPass']
            }
        }
    }
}

Note that the Bookstore project must be based on exactly the same Jmix version as the commercial add-ons sample project.

Performance Testing

See PERFORMANCE_TESTING for the description of performance tests executed for this application. The document includes the required configuration, information about infrastructure, tooling and test scenario. The test results demonstrate the behavior of the application with 1000 concurrent users.

Application Overview

Jmix Bookstore is a retail bookstore, that ships books to customers. The single distribution channel is phone. Customers call in and can order books directly from the phone, without any need to use a computer. They simply speak to a person that takes their orders and makes sure the correct book lands at their doorsteps.

The company consists of the following departments:

• Sales
• Order Fulfillment
• Procurement
• IT

The following users are available in the application:

Position	Username	Password
Administrator	admin	admin
Sales Representative	lois	lois
Sales Representative	jessica	jessica
Order Fulfillment Manager	adrian	adrian
Order Fulfillment Specialist	hikari	hikari
Order Fulfillment Specialist	melissa	melissa
Procurement Manager	nicole	nicole
Procurement Specialist	sophia	sophia
Procurement Specialist	william	william

We will highlight the main business cases of the corresponding departments that are supported by the application.

Sales

The sales team is the main interaction point with the customers. The company splits the customers into different territories. Each sales team member is responsible for one or more territories:

• Lois Marsh
  is responsible for all territories in the "US-South" and "US-East" regions.
• Jessica Musgrave
  is responsible for all territories in the "US-North" and "US-West" regions.

Placing Customer Orders

When a customer calls and wants to order some books, the sales specialists search for the customers by first name / lastname and optionally create a customer record for new customers.

After that, they collect the books that the customer would like to order, set the quantity and let the customer know about the price of a particular book and the overall order.

Placed orders will be picked up by the order fulfillment employees to confirm the customer order. When an order is confirmed by their colleagues, the sales employee gets a notification about it (see: Implementation Details > Notifications).

Order Fulfillment

The order fulfillment department consists of three employees:

and

Hikari Miyama

as order fulfillment specialists as well as

Adrian Adams

being an order fulfillment manager.

They together are responsible for making sure the orders, created by the sales folks are correct and can be fulfilled. Sometimes they see that particular books are low in stock. So they indicate to the procurement department that a book is getting out-of-stock, so that the colleagues can order new books from the suppliers.

Confirming Customer Orders

Once the order is placed by the sales department, it needs to be confirmed by the fulfillment employees. During the confirmation, the distribution center that should fulfill the order is selected. The system gives recommendations, but ultimately it is up to the order fulfillment specialist to decide which is the distribution center that fulfills the order. The main decision factor is the proximity between the fulfillment center and the shipping address, but other factors like amount of stock is also considered.

Perform Fill-up Requests

After a customer placed an order, the order fulfillment specialist checks about the remaining amount of stock for a book. In case it goes below a threshold, they will request a fill-up for this book in the inventory. During that process, the procurement employees are notified (see: Implementation Details > Notifications), so that they can start the work on performing supplier orders.

Procurement

The employees of the procurement department are:

and

Sophia Burnett

.

Nicole Berry

is their manager.

The responsibility of the procurement team is to perform supplier orders to fill up the stock of books. Besides that they are also in charge of managing the book catalog.

Place Supplier Orders

When a fill-up requests comes from the order fulfillment employees, William and Sophia are supposed to trigger a supplier order. They normally do that on mondays. Over the week the system collects the fill-up requests and groups them by suppliers, so that an aggregated supplier order can be placed.

The procurement specialist reviews the aggregated requests and can potentially make adjustments regarding the total amount of books or adding / removing particular books from the supplier order.

Once the review is finished, an approval is required if the cooperation status of the supplier is not "Important".

This business process is implemented using the BPM add-on (see: Implementation Details > BPM).

Finally, after optionally approving the supplier order, a supplier order is placed. The system sends out an automated email containing all relevant information to the configured supplier email address. (see: Implementation Details > Email).

Managing Product Catalog

The second responsibility of the procurement team is to manage the product catalog of books. For this the application provides views to add books to the product catalog as well as removing them from the listing.

IT

The IT department of the company consists of a single person:

. He is taking care of managing the master data of the system as well as providing system access for employees.

Managing System Access

In order to ensure that every employee has access to the system functionalities they need in order to fulfill their duties, Mike empowers employees to have access to the system. For this he manages employee records and users. He also assigns them to the corresponding positions & roles in the company and optionally their associated territories. With that, the employees are able to access the parts of the system and the associated data.

As (data) security is a very important to the company, the data the employees see is strictly restricted to their area of work. E.g. sales employees can only see customers and orders of their associated territories. Additionally, they are only allowed to create orders and customers, but not products or territories. This role management and assignment is performed by Mike as his work as the IT administrator.

Master Data Management

Particular data that changes very infrequently and acts as master data for other parts of the system is also managed by the IT department. This includes the Regions, Territories as well as the Fulfillment Centers the company operates.

Implementation Details

This section describes different functionalities that are part of the Jmix Bookstore application and also how they implemented using different capabilities of Jmix.

Domain Model

The domain model of the Jmix Bookstore is based on a regular order management system's data model. Additionally, it contains the part for the supplier order process and the general HR domain model.

The domain model for the customer orders part looks like this:

classDiagram
    Customer o-- Order
    Order *-- OrderLine
    OrderLine --> Product
    Product --> ProductCategory    
    Product --> Supplier

A

is associated with many orders. An

Order

consists of multiple

OrderLine

objects. One

OrderLine

represents a product association with corresponding information about the price. The

Product

entity is grouped into

ProductCategory

entities and references a

Supplier

that is used to request supplier orders.

The domain model that supports the supplier orders contains the following entities:

classDiagram
    Product --> Supplier
    
    SupplierOrderRequest --> Product
    SupplierOrder o-- SupplierOrderLine
    SupplierOrderLine --> Product
    SupplierOrder --> Supplier

The

entity is the source entity, that acts as the basis for

SupplierOrderRequest

instances. Those are created during the Perform Fill-up Requests process. The system converts those requests into

SupplierOrder

entities which hold a

SupplierOrderLine

for each

SupplierOrderRequest

that referenced a

Product

which belongs to the same

Supplier

. This

Supplier

is also used for the

SupplierOrder

.

During the Place Supplier Orders process, those

entities are created. The

Employee

that reviewed this

SupplierOrder

(through the BPM process variables) brings up the next subpart of the domain model.

The part of the employee information with the corresponding territory associations looks like this:

classDiagram
    Region o-- Territory
    Employee o--o Territory
    Employee --> User
    Employee --> Position
    User o--> Region
    User o--o Role

An

represents the logical representation of an employee in the company. The

Employee

has a

Position

that (s)he holds within the organisation. Optionally the

Employee

can reference multiple

Territory

instances, that (s)he is responsible for. Those

Territory

entities are grouped into a

Region

.

The system representation of an employee is the

, which main purpose is providing system access. The

User

references multiple

Role

entities (not physically in the database, just conceptually via the

RoleAssignmentEntity

from Jmix).

Additionally, the

references multiple

Region

entities as "associated regions". Those regions are automatically determined by the fact that the

Employee

has multiple

Territories

assigned, which themselves belong to a

Region

. This reference is present to allow the row-level roles to restrict access to Customers / Orders of the same region that the current user is in (see: Security > row-level roles).

Security

The Bookstore example uses different permissions for the different user groups to ensure users can only see the data and use the functionality they need for their daily work.

The Jmix Subsystem is used to achieve this goal. In the io.jmix.bookstore.security package, different design-time roles are defined.

The employees generally obtain one of the following functional / resource roles:

• EmployeeRole
  - base role for all employees to get basic system access
  • read permission for master data like employees, position, tenants
  • UI permissions for common UI views like 'My Task List', 'Address Map Lookup UI', etc.
• FullAccessRole
  - Role for administrative users without any restrictions
• OrderFulfillmentRole
  - functional role for
  Order Fulfillment
  position
  • read & write access to customer & order data; supplier order requests
  • read access to product and supplier order data
  • access to corresponding UI views
• ProcurementSpecialistRole
  - functional role for
  Procurement Specialist
  position
  • read & write access to product catalog data
  • read & write access to supplier order data
  • read access to supplier order request data
  • write access to supplier order request status attribute
  • access to corresponding UI views
• ProcurementManagerRole
  - functional role for
  Procurement Manager
  position
  • read & write access to product catalog data
  • read & write access to supplier order data
  • read access to supplier order request data
  • access to corresponding UI views
• SalesRepresentativeRole
  - functional role for
  Sales Representative
  position
  • read & write access to customer & order data; supplier order requests
  • read access to product catalog data
  • access to corresponding UI views

Additionally, there are two data constraining roles / row-level roles present in the system:

• ShowOnlyActiveSuppliersRole
  - data constraining role for
  Procurement Specialist
  position
  • limits suppliers to only ones that are not in status 'On Hold'
  • limits products to only ones that have suppliers with status not in 'On Hold'
• ShowOnlyActiveSuppliersRole
  - data constraining role for
  Order Fulfillment
  and
  Sales Representative
  position
  • limits customers to only ones that are in the associated regions of the current employee
  • limits orders to only ones where the customers region is in the associated regions of the current employee

The Jmix Security subsystem (see Jmix Documentation: Security) takes those design time roles into consideration automatically when users are assigned to those roles.

This assignment happens as part of the test data creation in the case of the Bookstore example, or during runtime in case an administrator manually manages system access (see IT > Managing System Access).

For automatic provisioning of the role assignments see the following classes:

• ItAdministratorEmployeeDataProvider
• ProcurementManagerDataProvider
• OrderFulfillmentSpecialistDataProvider
• ProcurementManagerDataProvider
• ProcurementSpecialistDataProvider
• SalesRepresentativeDataProvider

Internationalization

Jmix supports the application to be available in different languages. The Jmix Bookstore is translated into different languages (English and German at the moment). The user can select the desired language on the login screen.

Static Translations

In the UI, the texts to display are referenced through the

prefix, together with a translation key like:

io.jmix.bookstore.view.territory/territoryListView.title

. For each language, there is a translation file that contains the mappings between those keys and the translated text. See messages_de.properties for the german translation.

Translation of Data

Sometimes it is also required to not only change the static part of the application (like UI labels, error messages, enum values), but also to allow users to dynamically enter translations for data that is used as references.

This form of translation is not supported out of the box by Jmix. Instead, it requires the application developer to implement a solution for the concrete use-case.

In the Bookstore example, we have implemented one example of such behaviour. There is an entity called

which allows the administrator to configure the different Positions that are available for employees. The name of that Position (like

Sales Representative

) should be translated to the different languages. This way when the administrator creates the employee, it is possible to see the translated term for the entry in the dropdown box of the position selection.

It is implemented in the following way. The

entity holds a 1:N composition to an entity called

PositionTranslation

that is used to store the translations. The

PositionTranslation

entity has the following attributes:

• name (the translated value)
• locale (the language the value represents)
• position (the position it belongs to)

There are standard views for managing the translations generated as part of the Position detail view. To display the correct translation on the dropdown, the instance name of the

entity contains a lookup for the translation of the current user:

class Position {
    // ...

    @OnDelete(DeletePolicy.CASCADE)
    @Composition
    @OneToMany(mappedBy = "position")
    private List<PositionTranslation> translations;

    @InstanceName
    @DependsOnProperties({"name", "translations"})
    public String getInstanceName(CurrentAuthentication currentAuthentication) {
        Locale currentLocale = currentAuthentication.getLocale();
        return translations.stream().filter(positionTranslation -> positionTranslation.getLocale().equals(currentLocale))
                .map(PositionTranslation::getName)
                .findFirst()
                .orElse(getName());
    }
}

The

dependency passed into the method enables retrieving the current user locale.

See the following classes that represent the described behaviour:

• Position - The entity that should have translation for the name
• PositionTranslation - The entity that holds the translations of a Position
• LocaleConverter - Converter to store
  java.util.Locale
  instances directly in the DB
• LocaleDatatype - Jmix Datatype definition of
  java.util.Locale
• PositionEdit - Position Edit Screen that converts the
  Locale
  instance to a proper name via
  MessageTools
  (e.g.:
  de
  will translate to
  German
  )

Multitenancy

In the Bookstore example, the Multitenancy add-on is used to provide the different users ephemeral test environments of the bookstore. This is mainly used for the hosted version at https://demo.jmix.io/bookstore to prevent cluttered test data from various users when trying out the bookstore online demo. In this application, the Multitenancy add-on is used as follows:

All business entities (Customer, Order, Product, etc.) have the

attribute annotated with

@TenantId

through the

StandardTenantEntity

superclass.

For the test environment use-case of the Multitenancy usage, it is needed to store additional data in the tenant entity. This is achieved by using Jmix extension mechanism. The entity TestEnvironmentTenant extends the

entity that comes from the add-on. It uses

@ReplaceEntity(Tenant.class)

to indicate to Jmix that this entity should be used throughout the application instead of the original

Tenant

entity class.

See also: Jmix Documentation: Modularity and Extension / Extending Functionality / Extending Data Model.

When the user opens the app for the first time, a random tenant identifier is generated like

and put into the Tenant field in the Login screen:

When logging in and the tenant is not already initialised in the database, the following operations are performed:

1. Tenant is created
2. Tenant
   admin
   user is created
3. All example business users are created
4. System data (BPM process definition, System Reports) are imported for the tenant
5. Master data (Employee Positions, Regions, Territories, etc.) are created
6. Random test data for all business entities are generated

See the following classes that represent the described behaviour:

• TestEnvironmentTenants - Interface providing the main API of the test environment tenant logic
• TestEnvironmentTenantsBean - Bean implementing
  TestEnvironmentTenants
  interface
• TenantCreation - Bean for creating the tenant instance
• TestDataCreation - Bean for generating / importing test data
• TenantTestdataIntegrationTest - Integration test that shows how the tenant / test data generation works (only business logic, not UI)

BPM

The BPM add-on is used by the Bookstore application to implement business processes using the BPMN-2.0 standard. It embeds the flowable BPMN engine into the application and provides the UI for task management.

The BPMN engine is used in the Place Supplier Orders business process. The process definition can be seen in the running application as well as in the source code (either via XML or through the BPMN Designer of Jmix Studio (see also: Jmix Documentation: Using Studio / Studio Features / BPMN Designer).

See also: perform-supplier-order.bpmn20.xml

The process contains the following tasks:

1. Review Supplier Order Draft
   - human task to look at the created draft (based on the fill-up requests) and decide to continue with the order or decline the order altogether
2. Draft valid?
   1. if invalid, the order is marked as invalid and the requester is notified about the invalidity of their request
   2. if valid, the order is marked as valid
3. Approval required decision
   (DMN Task) - DMN table that identifies under which circumstances a valid order needs to go to approval (based on the supplier cooperation status)
4. Approval required?
   1. if required, human task to approve supplier order (with optional feedback loop to the
      Procurement Specialist
      ) is performed by the
      Procurement Manager
   2. if not required, the order is placed
5. Place Supplier Order
   - Service Task to automatically place the order. It marks the order as placed and creates a DOCX document via Jmix Reports Integration containing the order with its line items as a letter. The rendered DOCX document is stored on the supplier order entity and returned to the process instance to use it in the next step.
6. Send Order Form to Supplier
   - Email task that sends out the generated order form via email to the corresponding supplier using Jmix Email integration.

The process is programmatically triggered as part of the scheduled task 'Supplier Order Draft Creation', where for each new draft a process instance is started and assigned to users with the

role.

See the following classes that are related to the BPM usage:

• perform-supplier-order.bpmn20.xml - The BPMN-2.0 process definition for the
  perform supplier order
  process
• PerformSupplierOrderService - Interface representing the logic that is called during the BPMN service tasks
• PerformSupplierOrderServiceBean - Bean that implements
  PerformSupplierOrderService
  and provides logic to notify requesters about invalid requests as well as placing the supplier order on the supplier system
• SupplierOrderDraftCreation - Bean that creates the process instances based on the supplier order drafts it creates
• SupplierOrderReviewForm - Custom UI view that implements the human task of the process to review the requested supplier order
• SupplierOrderApproval - Custom UI view that implements the human task of the process to approve a supplier order

Email

As the last step of the Place Supplier Orders business process, the BPMN-2.0 business process integrates the Email add-on. The supplier order form is sent to the supplier via email.

Besides adding the add-on to the project, it is required to configure the connection settings to the SMTP server in the

file:

# ...

##############################################################
# Jmix Email Add-on
##############################################################
jmix.email.email-sending-cron=*/30 * * * * ?

jmix.email.from-address=<<MAIL_SERVER_HOST>>

# Spring Mail configuration
spring.mail.properties.mail.smtp.starttls.enable=true
spring.mail.properties.mail.smtp.auth=true
spring.mail.protocol=
spring.mail.port=
spring.mail.host=<<MAIL_SERVER_HOST>>
spring.mail.username=<<MAIL_SERVER_USERNAME>>
spring.mail.password=<<MAIL_SERVER_PASSWORD>>

The add-on comes with an administrative UI to see what the status is of outgoing emails. It contains the ability to read the emails, download the attachments and trigger re-send in case something went wrong during transmission.

Reports

The Reports add-on is used in the Bookstore example as part of the Place Supplier Orders BPMN-2.0 process. When the order is placed, the supplier order form (as DOCX document) is created. To achieve this, the

report is configured via the administrative UI:

The Report contains a report template as a DOCX document that contains placeholders where the actual data is inserted.

To contain the correct data (supplier order, order lines), the corresponding data from the BPMN-2.0 process is passed in when the report execution is triggered. This happens within the

Service task implemented in PerformSupplierOrderServiceBean through the

ReportRunner

API from the reports add-on (see also: Jmix Documentation: Add-ons / Reports / Running Reports / Reports API):

class PerformSupplierOrderBean {
    
    // ...
    private FileRef createSupplierOrderForm(User reviewedBy, SupplierOrder reloadedSupplierOrder) {
        ReportOutputDocument document = reportRunner.byReportCode("supplier-order-form")
                .addParam("entity", reloadedSupplierOrder)
                .addParam("reviewedBy", reviewedBy)
                .run();

        ByteArrayInputStream documentBytes = new ByteArrayInputStream(document.getContent());
        return fileStorage.saveStream("supplier-order-form.docx", documentBytes);
    }
}

Notifications

The Bookstore example utilises the notifications add-on to notify business users about events that happened within the system. In the users inbox, those notifications can be reviewed and marked as read.

The Bookstore notifies about the following business events:

Business Process	Business Event	Sender	Receiver
Confirming Customer Orders	Order confirmed	Order Fulfillment Specialist	Sales
Perform Fill-up requests	Supplier Order Request created	Order Fulfillment Specialist	Procurement Specialist
Place Supplier Orders	Supplier Order Draft created	System	Procurement

The notifications are send out by the system as part of state transitions of entities. Generally it uses the

API from the notifications add-on to deliver the in-app notifications to the users. See NotificationCenter.

In the bookstore example an additional abstraction is implemented. The Notification Center is the main class responsible for sending out the in-app notifications. It listens to all Spring events of the InAppNotificationSource type. This means that within the application the Spring application events mechanism is used to produce custom events at various points in the application.

Here is an example of the event interaction from the Order Fulfillment > Confirming Customer Orders process for sending out an in-app notification:

sequenceDiagram
actor Order Fulfillment Specialist
actor Sales Emplyoee
    Order Fulfillment Specialist->>[Jmix] DataManager:Save Order (confirm)
    [Jmix] DataManager-->>[Bookstore] OrderEventListener:EntityChangedEvent<Order>
    [Bookstore] OrderEventListener-->>[Bookstore] NotificationCenter:Order Confirmed (Event)
    [Bookstore] NotificationCenter->>[Jmix] NotificationManager: createNotification()
    [Jmix] NotificationManager-->>Sales Emplyoee: Order Confirmed

The data (sender, receiver, title and text) for the corresponding events of the

type are provided by implementing a bean of the

NotificationDetailDataProvider<OrderConfirmedEvent>

type. For the Order Confirmation example from above the following bean implements this responsibility: OrderConfirmedNotificationDetailDataProvider.

finds the corresponding data provider bean that matches a particular event type to retrieve the notification data.

Background Tasks: Quartz

In the Bookstore example the Quartz add-on is used to run periodic tasks by the system. Mainly the following two scheduled tasks are implemented:

• Create supplier order drafts (as part of the Place Supplier Orders process) every 5 minutes
• Clean up old test data tenants that are no longer in use (every day)

Example:

:

For the scheduled task of the supplier order draft creation a Quartz Job is registered as a spring bean together with a trigger configuration (see: SupplierOrderDraftCreationConfig):

@Configuration
public class SupplierOrderDraftCreationConfig {

    @Bean
    JobDetail supplierOrderDraft() {
        return JobBuilder.newJob()
                .ofType(SupplierOrderDraftCreationJob.class)
                .storeDurably()
                .withIdentity("supplierOrderDraftCreation")
                .build();
    }

    @Bean
    Trigger supplierOrderDraftTrigger(JobDetail supplierOrderDraft) {
        return TriggerBuilder.newTrigger()
                .forJob(supplierOrderDraft)
                .withIdentity("supplierOrderDraftTrigger")
                .startNow()
                .withSchedule(
                        cronSchedule("0 0/5 * * * ?")
                )
                .build();
    }
}

This mechanism registers

automatically in the system when the application starts up. In the quartz add-on it is also possible to configure those scheduled tasks via the UI. But in this example it is registered through the source code to show an alternative approach.

Here is the implementation of the job class that is executed as part of this scheduled task:

:

public class SupplierOrderDraftCreationJob implements Job {

    //...
    
    private final SupplierOrderDraftCreation supplierOrderDraftCreation;

    public SupplierOrderDraftCreationJob(SupplierOrderDraftCreation supplierOrderDraftCreation) {
        this.supplierOrderDraftCreation = supplierOrderDraftCreation;
    }


    @Override
    @Authenticated
    public void execute(JobExecutionContext context) {
        log.info("Starting Supplier Order Draft Creation Job for all Tenants");
        int amountOfCreatedSupplierOrders = supplierOrderDraftCreation.createDraftSupplierOrders();
        log.info("Finished Supplier Order Draft Creation Job: {} Supplier Orders created", amountOfCreatedSupplierOrders);
    }
}

(see: SupplierOrderDraftCreationJob).

The class needs to implement the

interface, but does not need to be marked as a Spring

@Component

.

The execution context is authenticated with system authentication via the

annotation on the execute method. See also: Jmix Documentation: Security / Authentication / System Authentication.

The actual business logic of creating supplier order instances is implemented in the

bean to separate execution context from business logic.