The Catalog objects are intended for managing persistent and conditionally persistent data.
With catalogs objects, you can design and support a variety of catalogs. The properties of each catalog are described at the configuration stage. The customizable properties include the code length and type, the number of hierarchy levels, and the check for code uniqueness.
Aside from the code and name, you can create a set of attributes for storing custom data related to a catalog item, as well as tabular sections of variable length for storing similar pieces of data, such as a list of product component descriptions, a list of employee family members, a list of company telephone numbers, and so on.
Each catalog can have multiple predefined forms for viewing and editing.
You can use the subordinate catalogs to describe subordinate entities. In this scenario each item of a subordinate catalog belongs to a certain item of the parent (owner) catalog.
In addition to the common properties available for all metadata objects, catalogs have specific properties, which are listed in this section.
You can edit a catalog in the editor
window, which includes multiple tabs.
To make a catalog subordinate to other catalogs, select the owner catalogs in the Owners attribute. Also select the subordination method: subordinate to items, subordinate to folders, or subordinate to folders and items.
For a hierarchical catalog, specify the hierarchy type, the number of levels, and whether the number of levels is limited.
To add owner objects, click the Edit List Item button on the Owners tab and select the objects.
- The Editing method property defines how catalog items are created and edited. If In list is selected, the catalog item data is entered in the list form. If In dialog is selected, the catalog item data is entered in a separate form.
- The Default presentation property defines how catalog items are displayed in other configuration objects. For example, if a document field is filled with a catalog item, the default catalog item presentation is displayed in that field. You can select how the item is displayed: as code or as description.
There are many ways to create a catalog item (for example, one can do it in a list or in a dialog box). Moreover, you can assign different forms to catalog items and folders. You can design custom forms for selecting catalog item values.
- Input by string
You can specify the settings for the input by string feature on the Input fields tab.
You can select configuration objects that can be generated based on a catalog item, or configuration objects that can be used as a basis for generating a catalog item.
On the Other tab, you can specify fields used in managed transaction data locks and specify whether objects of this type are included in the full-text search.
Use the Update predefined data list to select one of the following predefined data update modes:
Auto. Automatically select the mode as follows: Update automatically for master infobase nodes, and Do not update automatically for subordinate infobase nodes.
Update automatically. Predefined data items are created and updated automatically during infobase restructuring.
Do not update automatically. Predefined data items are not created or updated automatically during infobase restructuring.