Generally, when using Freedombase, business logic is applied against the Class itself. This means that updates to that Class will be applied consistently, regardless of what Web page the updates came from.

While it is possible to apply business logic via the Web templates, this should only occur as the exception, not the rule.

Business logic can be applied via calculations or expressions, which are a lot like spreadsheet calculations. If relationships have been defined between tables, these calculations can reference data in other tables, without requiring code to be written to do so. These calculations are a very quick, easy, powerful and flexible way to apply most business logic.

Calculations can be used to set the value of an attribute every time a record is updated through the Web interface. They can also be used to determine whether attribute values are valid or not, and to create custom error messages.

Calculations also allow the powerful Freedombase Cascade processing to occur – a very fast and effective method of cascading updates across the database, as a result of data changes made via the Web interface.

Please see the Calculation section in the Freedombase Help for more information on applying business logic using calculations.

Business logic can also be applied via Before or After (Pre or Post) custom code. This could be new code, or could include calls to existing subroutines or functions, or a mixture of the two.

Please see the separate Custom Code tutorial for more information on applying business logic using custom code.