Welcome to Jenercode

Getting Started

All you need to get started is to register a new account at Jenercode

Create your first team, create a project, and then start designing your data fields and user profiles

Core Concepts

Data Fields

Data fields are organised by into models and roughly translate to database tables and fields, but it important not to view them as just the database structure.

You will not need to include primary / foreign key fields, or timestamps as this are automatically added to every table when the code is generated.

Where the data design makes more sense to create many-to-many or polymorphic relationships, the underlying database design can be quite different to the model view.

Fields like geo-fields or number ranges may create more than one corresponding database field.

User Profiles

A default admin super user is created for all accounts automatically. This user type has full permissions to edit / create all data on the site.

To limit the permissions a user has, create a new user profile and explicitly give them permission to view / edit / create fields by creating components and mapping the fields to the specific component.

Component fields can take on more properties such as business logic, or provide further limitations on the data that can be set. A component field can never allow a wider set of data than the original field defines. This direction of data limitation from the fields to the individual user component fields is important for the security considerations.

Order and Nesting Matters

All fields, components fields, models and components can be re-ordered by dragging and dropping within the app. Model, components and component fields can all be nested.

Nested elements cannot occur before the parent element, e.g. for a nested model structure of customer > customer address, the customer address can not be created until after the customer is created.

Hints Everywhere

Hint boxes are included next to all fields to give more information.

Only Set Values when Required

If you don't need a default value, don't set one. If you don't need business logic, leave the fields blank. Sensible default values will be created.