Glossary

This page describes Blocworx terminology. For any Blocworx no-code developers, knowing these would be a requirement to work on Blocworx.

• Server: In the context of Blocworx hosting, this is generally referencing the virtual machine that Blocworx is hosted on (most often an EC2 Instance), not the physical machine in the data centre. However sometimes may specify on-premise server or real life server, in which case we are talking about those.

• Project: A code and database combination of our software hosted on a server. Click for more information.

• Instance: A subdomain and domain that is being loaded inside a project, usually for a specific customer, e.g. customer.domain.com Click for more information.

• Page: A place where you can links, modules or more sub pages, its the high level of navigation in Blocworx. More Info.

• Module: Most often represents a core piece of activity for a client, but can also represent a collection of blocs (see below) when referring to it using perfect Blocworx terminology. Management and Sales will more often refer to a module as something a process/flow the business is doing.

• Bloc: A form and database table associated with it.

• Bloc Settings: The configurations that are set at bloc level.

• Field: The inputs or information displays in the form part of a bloc.

• Field Rules: A specific list of features you can set on a field that apply rules to their values, for example, "Cannot be equal a certain value"

• Field Actions: Anything that is triggered as a result of a field value changing (or other means of triggering)

• Field Parameters: A series of settings at field level, some of which cause actions to occur.

• Roles: A group that you can apply to users, which allows them access to modules and blocs, but also can contain permissions (see below)

• Permissions: Specific rules that can be applied to users (via adding to roles), like "Can edit data"