Modules. The "modules" property
Glossary Item Box
Introduction
The modules property contains a configuration object responsible for declaration and configuration of modules and details loaded to a page. The / ** SCHEMA_MODULES * / marker comments are required, since they are necessary for the work of the wizards.
 |
NOTE To load a detail to a page, use the details property. However, since details are essentially modules, we recommend using the modules property instead. |
An example of using the modules property
modules: /**SCHEMA_MODULES*/{ // Loading the module // Module title. Must be the same as the name property in the diff massive. "TestModule": { // Optional Loaded module id Will be generated by the system if not specified. "moduleId": "myModuleId",. // If the parameter is not specified, BaseSchemaModuleV2 will be used for loading. "moduleName": "MyTestModule", // Configuration object. When the module is loaded, it is passed as instanceConfig. It stores a set of initial parameter values for the module. "config": { "isSchemaConfigInitialized": true, "schemaName": "MyTestSchema", "useHistoryState": false, // Additional module parameters. "parameters": { // Parameters added to a schema during its initialization. "viewModelConfig": { masterColumnName: "PrimaryContact" } } } }, // Loading a detail. // Detail name. "Project": { // The name of a schema detail. "schemaName": "ProjectDetailV2", "filter": { // Section object schema column. "masterColumn": "Id", // Detail object schema column. "detailColumn": "Opportunity" } } }/**SCHEMA_MODULES*/
