Hooray! Throughout January we’ve had great progress with the NoCode-X platform. Many of the basic features have been implemented and tested. A small summary of each of those features can be found below. Be sure to keep an eye on this blog or sign up to our newsletter below because we will zoom in on key features in future blogposts!
Enter your description
Creating / Editing webpages, mobile pages, pdf\'s should be possible by dragging & dropping components on screen. The editor should facilitate adding new component types easily.
Creating data in a json format should be possible by using the action editor. This functionality will lay the fundamentals for creating data objects and calling Rest API\'s.
The no code pages built with NoCode-X should be embeddable in "high-code" web applications. This should be language agnostic and sufficient attention to security aspects should be taken into account.
Creating / Editing Api\'s and exposing them should be as easy as filling in a form and linking logic to the Api.
We should provide different API versions out of the box. The latest version will always be default. Other API versions can be used by providing the version name in the request headers. This will offer clients a huge help towards keeping their API\'s backwards compatible.
Creating / Editing data formats in the form of JSON schema\'s should be as easy as filling in a form. Additionaly it has to be possible to trigger logic upon create/update/delete events.
A graphical user interface should allow users to create programs. The graphical programming language should contain all basis constructs like: For loop, For Each, If statements, switch statements, etc... and should be turing complete.
Templates should be able to inherit from one another. This inheritance should make it possible to create pages in a hierarchical manner. For example: Top level template could contain: navigations, header, footer, etc... while lower level templates could contain detail specific to the page in the application.
Templates should be able to exist in multiple languages. Adding/updating/removing components to/from one language should result in the update happening in the other languages.
It should be possible to translate a template in different languages just by clicking a few buttons. The automatic translation should be qualitative enough that only a check (and some changes) are necessary afterwards.
Different versions of applications should be able to exist. Adding / updating (the metadata) such a version should be as easy as filling in a form. Promoting a version througout DTAP environments should be possible by clicking a few buttons.
All applications should have a set of DTAP environments. The way we implement this should lay the fundament for offering local (or developer specific) development environments.
Creating PDF\'s should be as easy as creating webpages through the template editor.
The value(s) of all available form components should be able to be read/written using the action-editor.
Creating roles/rights should be possible on application level. Enforcing rights should be able on template/component/api and action level. The users should exist on company level which will enable a single signon experience on all applications for a certain company.
Applications should be able to contain a library of media files. These files can either be added upon creating the application by the "no coder" or while using the application by the user.
Creating roles/rights should be possible on application level. Enforcing rights should be able on template/component/api and action level. The users should exist on company level which will enable a single signon experience on all applications for a certain company.
Creating roles/rights should be possible on application level. Enforcing rights should be able on template/component/api and action level. The users should exist on company level which will enable a single signon experience on all applications for a certain company.
Applications should be able to contain a library of media files. These files can either be added upon creating the application by the "no coder" or while using the application by the user.
Creating roles/rights should be possible on application level. Enforcing rights should be able on template/component/api and action level. The users should exist on company level which will enable a single signon experience on all applications for a certain company.
The no code pages built with NoCode-X should be embeddable in "high-code" web applications. This should be language agnostic and sufficient attention to security aspects should be taken into account.
The value(s) of all available form components should be able to be read/written using the action-editor.
Creating data in a json format should be possible by using the action editor. This functionality will lay the fundamentals for creating data objects and calling Rest API\'s.
Creating PDF\'s should be as easy as creating webpages through the template editor.
All applications should have a set of DTAP environments. The way we implement this should lay the fundament for offering local (or developer specific) development environments.
Different versions of applications should be able to exist. Adding / updating (the metadata) such a version should be as easy as filling in a form. Promoting a version througout DTAP environments should be possible by clicking a few buttons.
It should be possible to translate a template in different languages just by clicking a few buttons. The automatic translation should be qualitative enough that only a check (and some changes) are necessary afterwards.
Templates should be able to exist in multiple languages. Adding/updating/removing components to/from one language should result in the update happening in the other languages.
Templates should be able to inherit from one another. This inheritance should make it possible to create pages in a hierarchical manner. For example: Top level template could contain: navigations, header, footer, etc... while lower level templates could contain detail specific to the page in the application.
A graphical user interface should allow users to create programs. The graphical programming language should contain all basis constructs like: For loop, For Each, If statements, switch statements, etc... and should be turing complete.
Creating / Editing data formats in the form of JSON schema\'s should be as easy as filling in a form. Additionaly it has to be possible to trigger logic upon create/update/delete events.
We should provide different API versions out of the box. The latest version will always be default. Other API versions can be used by providing the version name in the request headers. This will offer clients a huge help towards keeping their API\'s backwards compatible.
Creating / Editing Api\'s and exposing them should be as easy as filling in a form and linking logic to the Api.
Creating / Editing webpages, mobile pages, pdf\'s should be possible by dragging & dropping components on screen. The editor should facilitate adding new component types easily.
Interested in all updates to our platform? Subscribe to our newsletter.