Functionality
Introduction to Functionality​
menu Business logic > Functionality
Using the Functionality screen, you can develop and test the application's business logic that cannot be modeled. This business logic not only comprises traditional business rules  but also the logic to control the user interfaces, process flows and messages.
The functionality screen consists of six tabs:
-
Control procedures - Define the business logic. See 1. Create a control procedure.
-
Template - Templates contain the actual source code for the business logic. See 2. Add a template.
-
Assigning - For statically assigned business logic, you can assign a template to the various program objects. Parameter values can be specified for every assignment. See 3. Assign a template.
-
Deploy - This is where the program objects that use the template are (re)generated and can be applied to the database. See 4. Apply the functionality.
-
Unit tests - The place to create, maintain and run unit tests. See 5. Run unit tests.
-
Code review - The code review is based on the live code of the control procedure. See 6. Complete the control procedure.
-
Validation - This tab shows validation messages regarding the selected business logic.
Functionality
Definitions​
Control procedures​
A control procedure is a placeholder for a specific piece of business logic. The control procedure describes the business logic, defines where and how it is applied, and shows the development, test and review status of the functionality.