Hyperon is designed to let developers make any part of their application configurable on the fly. The easiest way to do that is make application's code dependent on parameters and their values. This is what we call parameterization.
That's why parameter is the basic concept in Hyperon. It is conceptually similar to decision table - the term commonly used in rules engines.
Each parameter is defined as matrix or table, in which we can configure how parameter's value depends on the context data. If application is connected to Hyperon in proper way, context can provide any data application works on. Parameter's matrix is unlimited in size and works fast whether it has 1000 rows or 1 million rows.
Below you can see parameter called "tariff" which returns tariff factor depending on client's age and type of agreement:
How this parameter can be used in application's code?
As you can see -- client's fee calculation is parameterized and uses tariff parameter. Value of tariff parameter is defined in Hyperon, outside of application's code.
You can say that parameter is the basic concept that allows to separate business logic from application's code.
Following image shows another parameter defined in Hyperon Studio.
Each parameter has its unique name, configured dependencies and output value. It can return single value, multiple values or even sub-matrix. See Using parameters for details on how to define and use parameters.
