Application definition

Developing an application using the Crossmarx platform is mainly defining the functionality you need. You define the "What", not the "How". The major part of the application can be defined without coding ("No-code"). Only specific tailor made functionality might need some coding ("Low-code").

All Crossmarx applications are defined using these four elements:

To develop an application, for every element you select what you need, configure, reload, and you are done. All functionality that is commonly used in business applications is already available, and can be easily activated.

Element 1: Blueprint

The 'Blueprint' consists of both the data model and the business rules. This is the foundation for the other elements. Building a good foundation will make it easier adding other functions to the application.

The data model is defined using:

• classes
• fields
• relations
• lookup lists
• filters

read more

The business rules of your application are defined using:

• calculations
• field triggers
• class triggers
• validations
• actions
• user groups
• permissions

read more

Element 2: User interface

This element contains building blocks to define the functional aspect of the user interface of your application. The blocks in this element:

• menus
• layouts
• forms
• dashboards
• custom urls

read more

Element 3: Resources

This element contains building blocks to define the design aspect of the user interface of your application. The blocks in this element:

• css
• surrounding page
• velocity scripts
• resource files

read more

Element 4: Configuration

This element contains building blocks to define other operations in your application. The blocks in this element:

• queries & reports
• imports
• exports
• deduplication settings
• jobs

read more

Summary

The blueprint consists of building blocks from five groups.