No-Code Platform

Introduction 

 
No-code platform has a visual IDE for business users to build applications. Applications will have entities, services, and data sources. It will have capabilities to create multi-channel apps and integrate them with services. Customizations can be provided easily as upgrades to the application deployed on AWS. The applications can be customized with different themes and User interface will have search, filter, export, and import capabilities. This platform will work with NoSQL databases like MongoDB.
 
The platform will have admin functionality to make changes. The changes are related to custom fields. Users can append the fields of text, attachment, number, currency, date, and money type. These fields can be added to entities. Validation rules can be applied to custom fields. Validation options can be provided to the user for choosing the right one for a custom field. The user can create actions on entities by adding custom code in a file. A trigger can be added to a custom field based on event and business operation.
 
The application architecture has a presentation layer, service layer, services client (mobile), persistence layer, data access layer, and database layers. These layers are implemented using the language stack and platform-specific patterns and practices. The metadata attributes are configured in the input for different layers. The application is configurable and extensible with modules, services, events, delegates, templates, services, and classes.
 
The code in the framework uses the metadata for handling different layers in the language-specific technology stack. The help documentation is also configured and it is used for application creation, rendering, and displaying. The user interface can be complex and will need layouts, complex control, validations, tab order, and additional configuration for different UI controls.
 
No Code Platform
 
A user interface will be provided to configure the layouts of the pages and desktop views. The pages and views can have custom fields and custom validations for the fields.
 
The fields can be of different types such as text, boolean, number, currency, date, and money. The user interface can have the capability for attachments. Fields can be configured for attachments. The fields can have different controls such as drop-down, pick select, multi-select, and auto-complete. The application can have controls which can be cascading and expanded selection actions. The user views can be configured which can consist of multiple records and widgets. The relationship between views and other records can be one to many, many to many and one to one. The fields can have controls that can be complex like type-ahead controls. Flyover tips can be configured for the view fields. The complex business logic will be passed on through custom modules and classes. The framework has capabilities to handle releases, upgrades, versions, and maintenance related features.
 
The neural sketch approach is based on the latest technology stack and can be upgraded to any new technology stack by changing the application framework code stack in different architecture layers. The database layer persists the data. It also handles the current state. The future scheduled state modifications can be handled by the database layer. Persistence layer has features to store and retrieve the data from various data sources across the system. The retrieval of the data is done by using different adapters.
 
The business logic and the rules layer handles the complex changes across the business entities and the entity groups. The service layer handles the updates and managing the group of entities. The user interface layer has features related to customization, configurability, extensibility of the attributes, and entities.
 
Different organizations use a metadata-driven approach for creating the application framework based products. (e.g., Oracle). Metadata is used to create the applications by using dynamic patterns and generation of the presentation layer and other layers modeled in the input configuration files. The modeling is based on the generic attribute-based entity patterns and data access object pattern. The application framework of the No-Code Platform helps in releases, upgrades, customizations, maintenance, and other challenges in the software engineering lifecycle. The user interface is provided for handling the customizations. These customizations do not require any code changes. The custom modules can be coded which can be loaded by the application framework of the no-code platform.
 
The user interface for the applications will be typically simple and easy to use. The application will handle different languages, format, and organization/layout based on the user's location and setup. The application will have support for globalization, which includes internationalization and localization. The application will have rapid and flexible searching and reporting. Collaboration and Data Sharing will be part of the application features. The application will support data sharing with different non-product users, inside and outside of the system. The application architecture of the No Code Platform Framework will have the ability to extend by using commercial packages and software. Security and licensing requirements will be handled by the application architecture. The architecture handles auditing of modifications such as inserts, edits, and deletions. The application will have configurable, multi-tiered, entity-context sensitive, security access to data and actions for different user roles and groups.
 
The platform application configuration will provide the capability to customize certain aspects of the application architecture like screens, data fields, workflows, etc. The application will have a development-related configuration related to managing metadata and programmatic updates. The application framework will have admin-level features for managing metadata through screens. It will have search features which are like Google search engine. The development configuration will have features for handling metadata and programmatic changes. Document management features will be part of the application framework. The document management module will be integrable with external document management software. The business rules will be handled in the framework and tied up with events and time. The workflow framework features will be part of the No-Code Platform application. Admin users will be able to schedule periodic tasks. Calendar events will be supported by the scheduler and the application. The notification component will be able to push notifications using email and other messaging frameworks.
 
Reporting will be part of the application framework. Internationalization requirements will be supported for more than one language, currency, and locale. Event and batch driven synchronization features will be used by the application framework for external system integration. A configurable user interface will be provided for these integrations.
 
The web user interface will be based on a rich and responsive application framework and have customization capabilities. Domain objects can be created using the user interface provided. The relationships and reference data can be provided. The sample configuration is provided which has the form, form fields, views, entities used in the system.
 
The application framework of the No Code Platform will support the creation and customization of domain objects. Domain objects can be exported and imported from the user interface. Support the import and export of custom domain objects (including database modifications) and custom screens. Custom actions can be configured and services can be mapped to the custom actions from the user interface. The import and the export of these actions can be done using XML or JSON from the user interface. The custom modules can be imported and exported into the deployment environment. The imports and exports should have versions for different environments. The business services will have rules and logic which need to be versioned. This can be configured in a service configuration. The changes in metadata at different layers need to be versioned fat the application configuration level.
 
All the user interfaces will have online help and help documentation can be configured in the application metadata. The No-Code Platform framework will have the capability to create application documentation.