Object Types

Object types are the core building blocks used to design Lowgile applications.

In the Design editor, each object type represents a specific category of application functionality, such as data storage, user interfaces, process automation, security, or application configuration.

Understanding the purpose of each object type helps application designers choose the correct building block when modelling business processes and application behavior.

Object type categories

Lowgile object types can be grouped into several broad categories.

1. Data modeling

These object types define how application data is stored and managed.

Entities store transactional business data created and updated by users.
Static Entities store predefined reference data such as currencies, cost centers, countries, or product categories.
Server Data Stores persist data on the server.
Client Data Stores store data locally within the browser or client session.

2. User interface

These object types define how users interact with an application.

Screens provide application user interfaces.
Screens contain components that display information, collect input, and perform actions.

3. Process automation

These object types define how workflows and business processes operate.

Processes define BPMN workflows, tasks, routes, and process transitions.

Note

To learn how proces flows are structured, see Understanding BPMN Process Flows.

4. Configuration

These object types provide reusable application configuration.

Configuration Items store shared settings, credentials, connection details, and reusable configuration values.
User-Defined Configurations store application-specific configuration data.

5. Security and access control

These object types control access to application functionality.

Roles group permissions assigned to users.
Access control configuration determines which users can access specific application functionality.

Choosing the correct object type

When designing an application, choose object types based on the responsibility they fulfil.

Need to store user-created or changing business data? Use an Entity.
Need a predefined list of reference values? Use a Static Entity.
Need to create a user interface? Use a Screen.
Need to automate a workflow or business process? Use a Process.
Need reusable settings or connection details? Use a Configuration Item.
Need to manage user access? Use Roles and access control configuration.

Selecting the correct object type helps keep applications organized, maintainable, and easier to extend over time.

For detailed reference information about individual object types, see: