Skip to main content
Matrix42 Self-Service Help Center

Define Fleet Management Data Model and Customization Recording

Goal

The article demonstrates how by means of the SolutonBuilder Schema Editor to build initial application Data Model for managing Cars. And how the SolutionBuilder Customization Recording feature helps to track all the changes in SolutionBuilder to generate at the end the Schema Scripts, which could be afterward used for installing the Fleet Management application on Production environment.

 In scope of the Lesson only the initial Application Data Model is created which aimed to demonstrated the common principles of Schema Editor usage. In further lessons the Data Model be extended in scope of each described feature 

Step 1: Design the Data Model

To start any Application or just a small feature you need clear understand how the Data Model behind the expected changes ar look like.  The following diagram (UML Class Diagram) provides one of the possible way how the Data Model can be designed upfront.

FLM DataModel.png

Step 2: Activate Customization Recording

When you design the UUX application in SolutionBuilder, for 99% it affects only changes in Production Database. And when the Application is fully implemented on Development Environment, and need to be migrated to Production Environment, only bunch of Database changes need to applied.  To simplify the generation of the Schema scripts relevant for the implemented actions, the SolutionBuilder provides a feature "Customization Recording", which on activation, automatically track all the relevant changes in the System, and at the end generates the Schema Scripts, ready to be installed on any other UUX environment.

  1. To activate the recording, open Solution Bulider Administration area Home Page
  2. Click the button "Start Recording".
    FLM_StartRecroding.png
  3. Assure the Recording is started and the button Download Recording is appeared.
    FLM_StopRecording.png

Step 3: Implement Designed Data Model

  1. Open SolutionBulider Data Definitions area, under the Administration/Schema Editor, and create a new Data Definitions with type "Pickup" for Car Type, Car Model, Car Brand, Car Gear. 
  2. Fill created Pickups with Data.
  3. For the Car Model, extends the standart schema of the Pickup class, with additional attribute Brand, to refer the Car Model related Car Manufacturer.
  4. Create Data Definition for the Car class. Use Data Definition "Simple CI base". That is relatively new option for Data Definition, which allows to create lightweigt Configuration Items
  5. Define "Car" relations and attributes like on UML
  6. Create Configuration Item "Car Type", mark it as a "Simple CI", and select previously created "Car" Data Definition, as Main Type Class

Step 4: Prepare Installation Package

Once the Schema changes is done, the first part of the project is finished. And we persist the implemented changes in Schema Scrips. For that come back to Administration hope page, and click button "Download Recorded Changes". The System returns the archive with the relevant schema scrips. 
To execute the schema scripts easily on another environment, the downloaded package is extended with .BAT file which command to install scripts

update -schema "..\Config\FleetManagment\FleetManagment.xml" "..\Config\FleetManagment"

After the adjustment the package has the following structure:

L FleetManagment.bat
L FleetManagment
       L FleetManagment.xml
       L 02-90-0444 CreateFLMCarClassBase.class
       L .....
       L 02-90-0454 AddFragmentsCarType.dat   

Step 5: Apply changes on Production Environment

  1. Deploy FleetManagment package to Production Enviroment. Extract archive to {ApplicationFolder}/Config folder
  2. Run FleetManagement.bat
  3. Make sure affected changes are present
  • Was this article helpful?