Documentation # 29

Open ID Connect & SAML integrations # 28

Auditing out of the box # 27

Encryption out of the box # 26

Upload component # 25

Bulk data import functionalities # 24

Data versioning # 23

Marketplace for components/logic/applications # 22

Create dashboards for managing your application # 21

Out of the box authorization # 20

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.

Media library # 19

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.

Out of the box authentication/authorization # 18

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.

No Code / Code hybrid # 17

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.

Gathering/Writing form values from pages in nocode # 16

The value(s) of all available form components should be able to be read/written using the action-editor.

Creating a json through no code # 15

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.

PDF Creation # 14

Creating PDF\'s should be as easy as creating webpages through the template editor.

DTAP out of the box # 13

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.

Application versioning # 12

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.

Auto translating templates in different languages # 11

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.

Template internationalization # 10

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.

Template inheritance # 9

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.

Action editor # 8

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.

Data format editor # 7

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.

API versioning # 6

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.

Api Editor # 5

Creating / Editing Api\'s and exposing them should be as easy as filling in a form and linking logic to the Api.

Template editor # 4

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.