Max Platform Concepts
In Max Platform, the following basic elements serve as building blocks to support the creation of applications with varying levels of complexity:
• Objects
• Fields
• Data Types
• Relationships
These building blocks make it possible to build a system that supports basic CRUD operations. Users can create data, view data in lists, view and edit single data entities, generate charts and reports, and so on.
Objects
Objects are the primary Max Platform entity. Each Object corresponds to a single data entity on the platform. These entities are core building blocks for Max Platform, and each application has its own set of default Objects. Users can also create custom Objects to meet their unique business needs.
Fields and Data Types
Fields define the attributes of Records that belong to related Objects. For example, in Service Board, the Task object has Fields such as Name, Assignee, and Start Time that represent the attributes of the related Object. Each Field is represented by a record of the Field object, and can have a variety of data types, such as String, Number, Timestamp, and so on. In Max Platform, these types are called Datatypes.
 |
The data modeled in Objects are stored in related Records. Each record has a full identifier in the format namespace_identifier_record_identifier. For example, in Service Board, the Identifier field value of the Object record named Job is job and its Namespace field value is ServiceMax - svmx. The Namespace record named ServiceMax - svmx has an Identifier field value of svmx, so the full identifier of the Object record named Job is svmx_job.
|
Relationships
Relationships define relations between Source Objects and Target Objects. Referential Relationships represent 1:N relations, and are configured as Fields of Source Objects that have the Relationship data type. Multiple Relationships represent N:N relations, and are configured in intermediate tables without related Fields.
Customization Options
You can customize Max Platform applications in the following ways:
• You can use REST APIs to retrieve or update data.
• To validate entities before creation, update, or deletion, you can create Data Validators.
• To create or update entities or call external resources before or after entities are created, updated, or deleted, you can create Event Handlers.
◦ Before Event Handlers have a Trigger field value of Before, which means they execute before CRUD operation transactions are committed, or before non-CRUD operations are executed.
◦ After Event Handlers have a Trigger field value of After, which means they execute after CRUD operation transactions are committed, or after non-CRUD operations are executed.
|
|
After Event Handlers start new transactions or executions, because they start after the triggering transaction or execution is committed.
|
Operations and Sources
To create Data Validators and Event Handlers, you must first define Operations and Sources. Operations contain general information, such as the programming language, class name, method, and route for the configured processing behavior. Sources contain the source code that executes customization behavior. Max Platform Groovy APIs are used to define customized Source code, and at this time, no other language is supported.