BOM project and BOM editor

When you write business model definitions, or import event types from an XML schema, Insight Designer generates a business object model (BOM) that you can view in the BOM editor.

With the vocabulary that is created from the BOM, rule authors can write the rules that control their business operations in a business rule language.

A BOM contains the classes and methods that rules act on. The BOM is based on the business model definitions that you created in .bmd files or by importing XML schemas (.xsd). The model consists of classes that are grouped into packages.

Example of a rule and the corresponding business object model

The business object model contains the types that correspond to the entities and events that you define. You can view these types and navigate the structure in the explorer view and in the BOM editor.

Model that is displayed in the BOM editor

The business model definitions (.bmd) create a model BOM entry. The import of XML schemas (.xsd) creates a BOM entry with the name that you entered when you imported the schema.

A business object model can contain one or more BOM entries. A BOM entry defines a set of business elements in the business object model.

A BOM contains the following files:
  • A BOM file, which describes the structure of the BOM.
  • A VOC file, which describes the vocabulary for the BOM entries.

Restrictions

Although the BOM editor has some editing capabilities, it contains features that are not applicable and not supported for the types that are generated from business model definitions (.bmd) or XSD. On these generated types, you cannot use BOM-to-XOM mapping to create virtual classes and methods that are mapped to an execution object model (XOM). These types have a de.generated property, and are managed by the runtime environment. Editing features related to decision validation services (DVS) are not supported either.

If you need to modify the default verbalization after an XSD import, you can do it in the Verbalization sections of the BOM editor. On a BOM generated from a .bmd file, if you modify the BOM or the verbalization, the BOM is no longer updated with the changes made in the .bmd file. A warning is displayed in the Problems view that states that this BOM entry is not synchronized with the corresponding .bmd file. You can disable the automatic generation of the BOM from the .bmd files, as described in Managing the BOM generation from BMD files.

The solution BOM is generated in a BOM project that is shared by all agents of the solution. This BOM project can contain only BOMs that result from the .bmd or from .xsd import. The BOM project cannot contain BOM entries created from a XOM or through the New BOM Entry wizard.