Subsystems

   

Scope: managed applications, ordinary applications.

Best practices

1.1. By using subsystems, you can achieve two goals:

• Create the global command interface in the main application window to provide the users with the general impression about the application features and tools.
• Combine metadata objects into groups, depending on their functional purposes, which makes application development more convenient.

In a trivial case, the structure of subsystems meets both goals.

For example, the "Inventory" and "Services" sections of the user interface can be used for development. In Designer, you can use these subsystems to look through the objects they contain in one click, to copy them to another configuration, or to set up the scope of the global search.

These subsystems must have the Include in the command interface checkbox selected.

1.2. Sometimes, subsystems and command interface sections don't match, that is, contain different sets of metadata objects. In this case, you can group the metadata objects into subsystems by their functional purpose. For such subsystems, the Include in the command interface checkbox must be cleared.

Examples:

• The Products catalog logically belongs to the "Master data" functional subsystem. However, it is displayed in the command interface of the "Master data" and "Marketing" sections.
• The "Settings and system administration" command interface section contains a list of objects that logically belong to different functional subsystems.

1.3. It is recommended that you include objects that are not displayed in the command interface—such as common modules, scheduled jobs, constants, and event subscriptions—in functional subsystems only.