Build Studio: Difference between revisions
Xamunadmin (talk | contribs) |
Xamunadmin (talk | contribs) |
||
Line 18: | Line 18: | ||
|- | |- | ||
| Ellipsis || • By clicking the ellipsis button in each design user has the option to view the Design/Page | | Ellipsis || • By clicking the ellipsis button in each design user has the option to view the Design/Page | ||
|} | |||
====Create Module (For WEB only)==== | |||
{| class="wikitable mw-collapsible" | |||
! Feature | |||
! Description | |||
|- | |||
| Create Module|| • Group name is required field. <br> • Main component dropdown list should vary based on the selected. Design/Page. This field is a required field. <br> • User has the option to select the Version (Blueprint versions). <br> • At least 2 Designs/Page should be selected when creating a group. | |||
|- | |||
| Choose Version || • Select a version where this module will be added as part of a version releases | |||
|- | |||
| Main Component || • Selection of a page where you will assign as main component | |||
|- | |||
| Include in Deployment || • A checkbox where an option to include this module whenever user Deploy in Sandbox | |||
|- | |||
| Save button || • Save the created module and it will be added on the List of modules. | |||
|- | |||
| Cancel button || • Cancel button will terminate create module action. | |||
|} | |} | ||
Revision as of 14:03, 1 March 2024
Build Studio has the backend and frontend setup for the project. The developers can easily build the application using the low-code interface. It also has the feature of deploying the application in an ultra-fast way and testing it.
Check and Confirm Pages
This is the page where the user can check and confirm the pages in Design components. You can view this page after creating a project and application. In this section, the user can group pages by module which is applicable only for Web Applications.
Feature | Description |
---|---|
Design Components | • Paginated list of designs |
Create Module button | • Create Module button should be disabled when all designs/pages are added in a group. • The user will be able to create module |
Add New Design | • A dialog will appear containing the Tenant ID, API Key, Session Keya and App ID with Instructions. • Will import new Figma Design |
Modules | • User can Edit/update created modules. • User can Delete created modules • Paginated list of created modules |
Ellipsis | • By clicking the ellipsis button in each design user has the option to view the Design/Page |
Create Module (For WEB only)
Feature | Description |
---|---|
Create Module | • Group name is required field. • Main component dropdown list should vary based on the selected. Design/Page. This field is a required field. • User has the option to select the Version (Blueprint versions). • At least 2 Designs/Page should be selected when creating a group. |
Choose Version | • Select a version where this module will be added as part of a version releases |
Main Component | • Selection of a page where you will assign as main component |
Include in Deployment | • A checkbox where an option to include this module whenever user Deploy in Sandbox |
Save button | • Save the created module and it will be added on the List of modules. |
Cancel button | • Cancel button will terminate create module action. |
Backend
Data Modelling
At Data Model Touchup, the predicted entity for each page can be set up by extracting the components of the page and setup the parameters.
Entiry and Property Maintenance
It contains the list of pages and its properties where the user has the option to add, edit and delete.
Entity Designer
This is the page where the developer can confirm and edit the entity of each page.
Once published, developers will be able to view the swagger. Typically, publishing takes about 30 minutes, but a pre-built version of the backup is available.
Create Entity and Property
This is the page where the developer can create the entity and property of the pages.
Route Editor (For Mobile only)
The Route Editor is for Mobile application only. This is where the initial code is displayed, and the developer can maintain the code.
Flutter Config(For Mobile only)
The Flutter Configuration is for Mobile applications only. It contains the list of the configuration.
DIO Configuration
This is the page where the developer can view and edit the Dio Configuration.
Local Storage Configuration
This is the page where the developer can view and edit the configuration for Storage Keys.
Services
This is the page where the developer can add and maintain the services.
Repositories
This is the page where the developer can view the different repository files.
Local Database Configuration
This is the page where the developer can add and maintain the database configuration.
Pubspec Editor
This is the page where the developer can add the packages. The JSON can also be viewed from this page.
Screen State
This is the page where the developer can add and maintain the different Screen State.
View Model
This is the page where the developer can create and maintain the View Model.
JSON to Dart
The JSON to Dart Model is for Mobile applications only. This is where the developer can create and maintain the different models.
Build API Swagger
Once swagger is viewable, developers will be able to test and view the back end set up and entity flow.
Frontend
UI Touch Up
This is the page where the front-end design and page routing set-up can be generated.
Angular Config(For Web Only)
To help the developers manage the angular package dependencies and environment variables.
Package Manager
Packages are the dependencies of the application to make it work.
Environment Variable
Environment variables are needed to store the application secrets and configuration data.
Page Routes
Page routing contains the flow from one view to another. This is also where the logic for the business rules can be applied.
Application Logic
Once Application logic for the business rules were set and integration is created, “Build” button will be available. Once done building the Frontend, App Test Site will be available for testing.
Version Release
way to differentiate current and past application configurations is through the Version Release.
Create Version
This is the page where the developer can create the different release versions.
Version Modules
This page list down the modules added in each version. The modules are created from Design Component page.