Replace schemas
Creatio development is based on the main principles of object-oriented programming. In particular, the Creatio extension model is based on the open-closed principle: the major Creatio logic is open for extension but closed for modification. This means that new features must be developed by introducing new entities rather than modifying the existing entities.
The schemas in pre-installed packages are closed for modification on the system level. Develop and modify the functionality in custom packages using the replacement mechanism. In Creatio, the replacement implementation is based on the concepts of replacing and replaced schemas.
The replacing schema is a schema that replaces another schema of the corresponding type.
The replaced schema is a schema that is replaced by another schema of the corresponding type.
Creatio IDE lets you replace the following schema types:
-
Client module that defines the view model.
Client modules implement the front-end part of Creatio. To create a replacing client module, use the replacing view model schema. Instructions: Client module.
-
Object.
Objects implement the back-end of Creatio. To create a replacing object, use the replacing object schema. Instructions: Object.
-
Source code.
Source code implements the back-end of Creatio. Classes serve as replacing schemas. To create a replacing class, use the schema of the "Source code" type schema. Instructions: "Source code" type schema.
After you implement the replacing schema, Creatio will execute the logic of the replacing schema when accessing the element.
Creatio IDE lets you replace a single schema in multiple user-made packages. The hierarchy of packages that contain the replacing schemas defines the resulting implementation of the replacing schema in the compiled configuration.