• Default Value - Text entered by default into all required fields.

• Double-clicking an object opens... - Sets the behavior of the application after double-clicking a selected object (computer, user, etc.) both in tree-form managers and in any list view or report that supports double-clicking. Available default action: Launch the Properties dialog box for an object or open its Detailed Report.

• Verification of uniqueness of Identification values - Object property controls can verify identifying values for the fields: ID, Inventory number, and Barcode and present an appropriate icon to indicate verification results. You can define the scope of the uniqueness verification process or disable it. Check uniqueness within object collection means that the application will verify the uniqueness, for instance, of the computer identifier (ID, Inventory Number, Barcode) by analyzing other identifiers only in the collection of computers. This setting allows different types of objects to have the same identification numbers.

• Specify prompts in the properties dialog box - Object property controls are equipped with a dropdown list of prompts with values that are present in and dynamically collected from the database (no need to create any glossaries). The list of prompts can be displayed (dropped down) by clicking it or by calling it with the ALT+Down shortcut. When the option is enabled, the application will also filter prompts, considering the data already defined for an object, e.g. the list of hardware manufacturers for the printer category will be populated only with printer manufacturers, etc.

• Purchase document date is the date the object was added - This option concerns the object creation log that can indicate the current date or the date of the relevant purchase document (according to the preferences of the application user).

• Ask before closing the application - Enables or disables the display of the confirmation inquiry before closing the application.

• Database system - Codenica Inventory can store data in two database operation modes: the default internal file system mode or Microsoft SQL mode. It is recommended to store data in MSSQL format. Any server type (free or commercial) since version 2005 can be used.

• Application Operating Mode - The application can operate in two modes: Standalone mode or Network mode (shared database). The second mode should always be selected when the database is used by several workstations with installed Codenica Inventory software. When network mode is enabled, the application ensures the safety of simultaneous writing data to records, refreshes data more often, and reserves generated identification numbers.

• Authentication, UserID, and Password - Responsible for proper logging into a selected Microsoft SQL Server according to its settings.

• Server - The path to a Microsoft SQL Server (free or commercial, version 2005 or later).
It should be typed in the format: Hostname\SQL instance name

• Database - An arbitrary target name of the database.

Many inventories can be created on any number of Microsoft SQL servers, and you can flexibly switch between them. After each connection to a new data source, the application always offers to migrate the currently displayed data. Because of this, you should be very careful not to accidentally overwrite an existing database. NOTE: If the data migration option is selected for an empty database, the application will understand it as a command to remove the data from the connected database. In the case of network access, it is important for less-advanced users to be prevented from using data migration privileges.
This can be done with the following option: Settings > User Privileges »

See the user guide's "Database" chapter »

• Limit of Simultaneous Threads - Corresponds to the number of simultaneous threads used for computer scanning. In the case of heavily overloaded networks, it is recommended to reduce the number of threads to avoid additional network overloading.

• Timeout for WMI and Registry Queries (seconds) - When scanning computers that are difficult to access due to network overloading or its reduced throughput, you can increase the query timeout. Remember that certain scanned WMI classes (e.g. Win32_Product – disabled by default) are characterized by a very long access time even on local computers. When remote scanning such classes, it is recommended to increase the timeout.

• Scanning - The audit range (the main sections of an audit to be performed) can be selected according to individual preferences.

• Recognition Process - This action is performed automatically after completion of a scanning procedure. It is responsible for correctly generating objects (computers, hardware, and software) based on (source) objects detected in WMI, registry, and files. By editing a scanning model, one can fine-tune the process of its recognition.

To learn more about the auditing process, read chapter: Audit »

Codenica Audit does not impose or hide any objects to be audited. Each audited element is described in the form of a scanning model, where you can select a WMI class, the values to be collected, and the recognition plan (transformation of source data into computer, hardware and software objects) according to individual preferences. This feature ensures high flexibility for auditing.

The description of the dialog box for editing the WMI scanning model (see section below) shows the method for creating a user-defined scanning model.

The Reset button restores the default set of scanning models.

WARNING: For WMI scanning to be possible, it is also necessary to enable the option in the program settings tab, accessible through: Settings > Audit > General »

To learn more about the auditing process, read chapter: Audit »

The dialog box allows you to fine-tune the configuration of an audited WMI object. It is required to provide the name of the scanning model, the WMI class, and the identifying property. The Identifying Property is supposed to return a unique value for a given object that will be responsible for preventing object duplicates from being created and for correctly relating an audited object to an inventoried object in an export to inventory scheme. A Name, Caption, DeviceID, or SerialNumber (depending on a particular object) can function as an identifying property.

• Collected Properties - To speed up transfer and reduce network load during remote audit (DCOM), it is best to specify only the properties of scanned objects that are of interest in order to reduce the amount of collected data. This can be checked in detail by testing a given class by clicking the Test button.

• Recognition Plan - Define a preferred method for relating the data collected from WMI to the properties of created hardware or software items. (The type of a recognized object is set with the Recognize as Object option in the top part of the control.) When you add a value that does not belong to the group of collected WMI class properties, the application will treat it as a string constant. For instance, you type "PC Workstation" in the Category field, which will display this value in each newly-recognized computer (created based on a scan). Using a recognition plan, the final objects (computer, hardware, and software) strictly compliant with individual preferences.

EXAMPLE:
Creation of a custom WMI model - a list of services launched on an audited computer

1.) Select the NEW button in Settings > Audit > Scanning: WMI
2.) In the dialog box displayed above, type (without quotes):
a.) Name - "Running services" or any other preferred name
b.) WMI class - "Win32_Service"
c.) Recognize as object - "(do not recognize)"
d.) Identifying property - "Caption"
e.) Additional query string - "Where started=true"
3.) To select collected properties, click the TEST button now and check which property is responsible for the required value. You can also let all properties be collected (which is excessive, as indicated above, but it can be left as in this example).

And that's it. Once you click OK, all of the dialog box settings are confirmed. After the next scan, you can right-click a selected host and display the list of the services launched in an audited computer using the context menu: Show Detected (source)>WMI>Running Services.

WARNING: For WMI scanning to be possible, it is also necessary to enable the option in the program settings tab, accessible through: Settings > Audit > General »

To learn more about the auditing process, read chapter: Audit »

The list of registry scanning models is similar to the list of WMI models (see section above). Like before, you can create customized models of audited objects. The difference is that, instead of working with WMI, you configure the paths, properties, and key values of the Windows Registry.

See Scanning: WMI Settings »

The Reset button restores the default set of scanning models.

WARNING: For registry scanning to be possible, it is also necessary to enable the option in the program settings tab, accessible through: Settings > Audit > General »

To learn more about the auditing process, read chapter: Audit »

The settings tab has a similar structure to what is used for the WMI scanning model (described above and accompanied by the above example of adding a new model). The WMI class field is replaced here by the Registry Path field, and the Additional Query String field by the Property collection mode field, which determines the mode of reading data from a registry key.

See Creating a WMI Scanning Model »

WARNING: For registry scanning to be possible, it is also necessary to enable the option in the program settings tab, accessible through: Settings > Audit > General »

To learn more about the auditing process, read chapter: Audit »

A detailed audit of a computer can also be based on the analysis of scanned files. This settings tab allows you to fine-tune the configuration of scanned files, their types (defined according to user preferences), and extensions.

For instance, you can add mp3 files to be scanned by typing mp3 and Music in the extension and type fields at the bottom of the control. Then, click the + button, which places the newly-added extension and file type to the central "Scanned File Types" list. After a completed computer audit, you can right-click a related host and display the list of detected mp3 files in the audited computer using the context menu: Show Detected (source)>Files>Music.

Skipped Folders tab - Allows you to add folders that should be skipped during scans.

Collected Properties and File Filter tab - Allows you to select the file properties that are to be collected. (To reduce the amount of data and speed up the process, it is recommended to collect small amounts of file data.) Using the filter, the scanning process can be restricted, for instance, only to files used in the current month [LastAccessTime equals (current month)] or according to any other conditions.

WARNING: For file scanning to be possible, it is also necessary to enable the option in the program settings tab, accessible through: Settings > Audit > General ». When remote DCOM scanning, it is necessary to grant access to scanned folders for the duration of an audit procedure.

To learn more about the auditing process, read chapter: Audit »

The settings tab allows you to select alerts scanned and analyzed during the process of auditing. Some alerts are generated when scanning, and others are generating during recognition (analysis of product keys and license keys).

Antivirus alerts require antivirus software that supports WMI. Therefore, not all antivirus applications can be examined in this manner. (It depends on the manufacturer of the antivirus software.)

Some alerts can also be undetectable by older versions of Windows or because updated service packs have not been installed.

WARNING: For alert scanning to be possible, it is also necessary to enable the option in the program settings tab, accessible through: Settings > Audit > General »

To learn more about the auditing process, read chapter: Audit »

Some alerts can be customized within the ranges of their respective triggering variables. A tip concerning the format of data introduced into the Details field is always located in the bottom right corner of the configuration dialog box if customization of a given alert is supported.

See the list of scanned alerts »

WARNING: For alert scanning to be possible, it is also necessary to enable the option in the program settings tab, accessible through: Settings > Audit > General »

To learn more about the auditing process, read chapter: Audit »

The process of license auto-matching in an audit automatically relates real-world licenses (introduced manually into the software – Codenica Audit) to detected software. Codenica Audit does not presume license possession on the basis of detected applications or by reading application keys. This would mislead the user into believing that all of their software is licensed.

In order for the license auto-matching feature to work properly, owned licenses that meet with all the requirements of particular software manufacturers (invoice, license certificates, original media, holographic stickers, etc.) should be manually entered into Codenica Audit and assigned to hosts, where they are used.

You can choose the software record color, which is required when there is no license. Thus, the software in question will be visible for at each stage of data processing (in wizards, selection dialog boxes, and list views).

Compared properties of "License" and "Software" objects - To match owned licenses (assigned to audited hosts) in an auditing process, the application must analyze their identification data. The name of a license and detected software are the basic elements of the matching process. You can also include the remaining fields in the analysis, when the matching feature returns ambiguous results.

Include only 100% matches - The option sets the application to perform a direct analysis, without any sampling feature applied to license and software names.

NOTE: The license auto-matching feature is a solution that makes it easier to audit for software licensing, but it is not required. A software licensing audit can also be carried out manually, by assigning owned software licenses to recognized applications, once computer scanning is finished.

To learn more about the auditing process, read chapter: Audit »

Software Verification - A software audit can be performed based on installed applications detected through WMI, registry, and file scanning. Since the same software can be detected by all the above-mentioned scanned sources, apply a method for verifying recognized software. Remember that data from the same program can differ slightly in each of the sources, which can result in duplicate recognition results. The software name is the basic verification element. Its version is an additional feature that can be compared directly, or you can attempt to match it to software.

The method of adding information about software makes the application attempt to collect any possible data about software under recognition from any sources.

Software Packages - The package feature allows the application to create a single piece of software (e.g. Microsoft Office 2003) during recognition (based on software definitions), instead of returning all its components separately, one by one (e.g. Word 2003, Excel 2003, etc.). You can create customized software packages using the Software Definitions » feature.

To learn more about the auditing process, read chapter: Audit »

Remote authorization is required for remote DCOM connections (agentless remote connection). Each remotely audited host must have a correctly configured administrator's access login and password. When configuring a remote authorization pool, start by choosing a name for a given authorization (the first dropdown list from the top) and then define the data required in the Logging Accounts group in the required format.

WARNING: Incorrectly configured remote authorization will result in an "Access denied" error, which makes it impossible to audit the computer in question until the administrator login and password are correctly configured.

Default Authorization - Allows you to select one of the configured authorizations (administrator login and password) as the default one that can be applied to all newly-added hosts.

To learn more about the auditing process, read chapter: Audit »

Codenica Audit is distributed with a comprehensive database of software definitions. The software definition feature is for ordering and formatting applications detected during the auditing process. The solution is very flexible and allows you to easily and automatically create customized definitions.

The top part of the settings tab contains the list of software definitions. The bottom part contains the list of associated files related to selected software. The Known Products label displays numeric data in the following format: number of built-in definitions / number of user-added definitions.

Using the toolbar above the software list, you can create and edit definitions, join them into packages, decide whether given software is to be recognized (i.e. returned in the list of audit results), and decide whether it requires licenses, etc.

The bottom list displays file definitions related to the software selected in the top list. The Known Files label displays numeric data in the following format: number of built-in file definitions / number of user-added file definitions.

To learn more about the auditing process, read chapter: Audit »

The dialog box for editing software definitions allows you to enter software data that will be used in the application recognition process (creating a software object based on data acquired from scanning). The License Required option determines whether a piece of software should be treated as properly licensed (no assigned license required) when there is no license related to it. The Recognize option allows you to include a given piece of software in or exclude it from the recognition process. As a result, even if a given program appears in the (source) scanning data, no software object will be created based on the program as a result of an audit procedure. This option is best used to exclude applications associated with drivers for small presentation software from being recognized.

To learn more about the auditing process, read chapter: Audit »

The dialog box for assigning a selected software definition to a package allows you to assign elements both to an existing package and to a newly-created one. A software definition can be assigned simultaneously to multiple packages.

To add a definition to an existing package, select the package from the dropdown list and click the button located to the right of the list. The name of the selected package will appear in the list of assigned packages.

To add a definition to a customized, newly-created package, select the Assign to New Package (create) button and input the data required for a new package. Once the package is approved, it will appear in the list of assigned packages.

To learn more about the auditing process, read chapter: Audit »

To use the automatic generation feature for software definitions, the auditing process must include scanned files.

See general audit settings »

Generating software definitions is an automatic process. As any such process, it can return results differing from the user's expectations. Therefore, it is recommended to check the list of proposed new software definitions before entering them into the definitions database. You can use the bulk data modification feature that is available in the controls from the Edit Fields of Selected Records group. Modifications are made by clicking the Apply button, which applies them only to the definitions selected in the list. Before confirming new definitions (OK button), remember to select them first in the list. Clicking the field located in the top left corner of the list (the first from the left) selects all listed records.

To learn more about the auditing process, read chapter: Audit »

The Settings tab allows all users to support the process of creating and editing the built-in database of software definitions with their own definitions. The sending process is fast and anonymous. It does not use your e-mail, as it uses Gmail SMTP (our Gmail account) and operates in the background. Software definitions do not contain any user-related data.

To learn more about the auditing process, read chapter: Audit »

The Object Caption feature is aimed at adapting the display of single-line object description strictly to individual preferences. Its configuration is very important, as the application uses this feature very frequently in many places.

The application uses the object caption when creating lists of objects (e.g. selection dialog boxes, wizard controls, and print forms), when creating the most recent nodes symbolizing objects in tree-form managers (Object Manager, Network Manager, and Audit Manager), when creating detailed reports, and when filling the Object Caption column in list views and in all other places where the single-line object description needs to be displayed.

An object caption is set separately for each object type (user, computer, hardware, software, license, etc.). Its configuration is very simple. You select properties (and their order) that will return values to be used in a single-line object caption. Additionally, you can define a custom separator that can consist of any characters. The separator will separate individual values in an object caption. Prefix and Postfix are string constants that delimit a selected value. A prefix begins and a postfix ends a value. Below shows how to use an object caption in practice.

Examples of Using the Application's Object Caption Feature
• Tree-form managers (most recent nodes)
• List views (Object Caption column)
• Object selection dialog box

The settings tab allows you to enable or disable the display of selected object properties in its Properties dialog box. The options can be set separately for each object type. For some object types, they can be set separately for each existing object category. Within the hardware group, you can display some properties in the Object Properties dialog box for the processor, while other properties are displayed for the printer, etc.

The Properties dialog box is the basic dialog box for editing single objects. Open it from an object's context menu, using the ALT+Enter shortcut or by double-clicking an object (when the action is set in Settings > General)

• See the Object Properties dialog box »
• See the settings of behavior after double-clicking an object »

The settings are similar to the above-described case of object properties, but they apply to the template of a selected object type.

Object template is a solution that enhances the process of data introduction and editing. When the user's company owns or frequently purchases the same types or models of computers, hardware, software, licenses, or consumables, simply save an object as a template to avoid re-entering data each time. Because object templates are saved in the XML format, they can be easily edited, even in Windows Notepad.

To save an object as a template, use its context menu or select the Save to template command from the Other menu. The same can also be done with the "Save" button in the Object Properties dialog box. To reproduce template data in an object, select the button with the "Open File" icon in the Object Properties dialog box.

See the Object Properties dialog box »

Object status is a dynamic property that allows you to quickly get information about the status of a given object (under repair, in store, in use, free seats for licenses, etc.). Information about object status is additionally enhanced by displaying color icons with the symbol of a given object status.

Type of Behavior (activity) - Select an action to be applied to an object (enter new, assign, disconnect, etc.)

Object Type - Select the type of a configured object (user, computer, hardware, software, license, etc.)

Property Behavior (status) - This option indicates whether an object status should be changed to another value (according to the user preferences) or left unchanged.

Status icons are designed to quickly provide information about the status of an object without displaying its properties dialog box. The icons are visible in tree-form managers (Object Manager, Audit Manager), inside object selection dialog boxes, and in wizards and list views.

To change an icon with a given status, first select or type the value of a configured status into the first field at the top. Then, select one of the available icons and click the Apply button.

These settings configure the automatic numbering of the ID property feature. Automatic numbering can be mass applied to all objects or applied individually to a given object type. For some objects, it is possible to apply separate automatic numbering scheme, broken down into object categories (e.g. separate numbering schemes for processors and for printers). Using the visible controls, you can enable automatic numbering for a given object type or for a given category. When applying changes individually, remember to use the Apply button. Prefix and Postfix are string constants that delimit an automatically-incremented ID number. To disable automatic numbering for all objects, select the Common Numbering option and check the Disable Automatic Numbering box.

These settings configure the automatic numbering applied to the Inventory number property feature. Automatic numbering can be mass applied to all objects or applied individually to a given object type. For some objects, it is possible to apply separate automatic numbering scheme, broken down into object categories (e.g. separate numbering schemes for processors and for printers). Using the visible controls, you can enable automatic numbering for a given object type or for a given category. When applying changes individually, remember to use the Apply button. Prefix and Postfix are string constants that delimit an automatically-incremented ID number. To disable automatic numbering for all objects, select the Common Numbering option and check the Disable Automatic Numbering box.

These settings configure the automatic numbering of the Barcode property feature. Automatic numbering can be mass applied to all objects or applied individually to a given object type. For some objects, it is possible to apply separate automatic numbering scheme, broken down into object categories (e.g. separate numbering schemes for processors and for printers). Using the visible controls, you can enable automatic numbering for a given object type or for a given category. When applying changes individually, remember to use the Apply button. Prefix and Postfix are string constants that delimit an automatically-incremented ID number. To disable automatic numbering for all objects, select the Common Numbering option and check the Disable Automatic Numbering box.

Each object in an inventory can generate very detailed history logs of actions that include:

• Creating an object in the inventory
• Editing an object in the inventory
• Assigning and removing a relationship with another object
• repair, service, upgrade, and maintenance of an object
• and other actions

Each history entry contains all indispensable information about a modification:

• Modification date
• User who performed the modification
• Value before and after modification
• Computer where the modification was made

History logs can be viewed in a list view or in the History tab in the object properties dialog box.
See the Object Properties dialog box »

The Application Event Log is a toolbox panel docked by default at the bottom of the application screen.
See the description of the Application Event Log in chapter: Toolbox Panels > Application Event Log »

Select the types of application event logs to be displayed in the Application Event Log toolbox panel. When there is a large amount of data (over 20,000 objects in an inventory), it is recommended to limit the generated event logs or disable the Application Event Log to ensure better application performance. You can also enable the performance option that disables automatic refreshing of the Application Event Log.

See application performance settings »

You can enable or disable the automatic log cleaning feature in the Application Event Log and define the limit value that triggers the cleaning mechanism after application start-up.

The list allows you to specify in detail the categories of deleted application event logs. The "Cleanup Logs Now" button immediately deletes selected log categories from the Application Event Log.

List view statistics are visible in the bottom panel of each list view and allow you to create any summary using counting and totalling features. Although it may seem difficult at first, the feature is very simple to use and it provides great flexibility in terms of configuration. Please refer to a separate section on list view statistics in chapter: List views and Reports (see link below).

See List view statistics »

Value Limit - Defines how many numbers summarizing a set statistics should be displayed. When the list view contains multiple values (e.g. when the set statistics processes all inventory numbers appearing in a list view, the application will return multiple values along with information on the frequency of a particular value, up to the defined limit that allows only the first 10 values to be displayed). When the value limit is exceeded, a given statistics ends with three dots.

Pointer (prefix) - The prefix of each set statistics that begins the result or list of results in this list view statistics.

Value Separator - A string of characters placed between successive results of a set statistics.

Each computer has a set of properties that dynamically count any costs of its functioning. Display the computer properties dialog box to quickly get information about the related costs shown in the Total Costs group. (The screenshot with a view of the properties for a computer is shown below.)

Computer properties can be used as columns in any list view that covers computers.

The settings accessible in this control allow you to select types of computer-related objects, the values of which are to be added to the value of the computer itself.

View of the Total Costs Group in the Computer Properties Dialog Box.

If the Print Form wizard sets objects to be printed in detailed mode (property – value), the settings tab allows you to select the properties to be included in a print form.

See Print Form wizard »

The Settings tab allows you to select related objects that are included in forms for each object type. Related objects are printed with their object captions.

• See Print Form wizard »
• See Object Caption settings »

When Codenica Inventory is used in a network by multiple users, it is recommended to indicate a separate folder on a network server with a periodic backup mechanism where to store all related files. This solution will protect files and allow for easy switching (if need be) of the access computer with Codenica Inventory installed.

Also remember the Related File Management wizard that allows any folders with related attached files to be quickly mapped, which includes the option of copying them to a new location. The wizard is launched with the Menu > File > Related Object Files command.

See the Related File Management wizard »

The feature for configuring user privileges allows you to create any number of application users, to define their logins and passwords, and to grant them very specific functional privileges concerning the use of the application. Apart from the rights to perform typical actions on particular types of objects in an inventory (create, edit, delete), it is possible to configure access rights to the tabs of program settings described here and to the functionality of the database itself.

To monitor the current status of hosts (online, offline, under auditing, etc.), the application uses the ICMP protocol. For very heavily loaded networks, it is recommended to not use this functionality or to increase the interval between network messages. Current host statuses are presented in the form of dynamic icons in the Network Manager.

These settings are of particular interest for users who store very large amounts of data (when an inventory exceeds considerably 20,000 objects) in heavily overloaded and restricted computer networks. The settings shown below can considerably speed up the work with the application by disabling data refreshing or reducing the number of related objects included in list views.

To ensure that data displayed in any visible window are always up-to-date, the application uses the automatic refresh feature. Therefore, when there is a large amount of data (over 20,000 objects in an inventory), the application operation can be considerably slowed down (especially when it is shared over overloaded and restricted computer networks).

In such case, the automatic refreshing of toolbox panels can be disabled so that the process of refreshing is not triggered before the user focuses on (clicks) a given window.

List views available in the application can show any object data (both data collected directly from object properties and data acquired by collecting values from related objects remaining in any possible relationships). When a large number of objects is stored in an inventory (over 20,000), the amount of data in particular list view cells can grow to reach values exceeding what can reasonably be shown on a printed page. These settings are designed to reduce the amount of data in a single list view cell, which ensures faster processing of list views.

One of the main objectives of Codenica Audit is to support and automate the process of creating inventories in Codenica Inventory. Once an audit is completed, the data can be sent to the inventory system using the export-to-inventory wizard (Menu > Audit > Export to Inventory).
See the description of export to inventory in chapter: Export to inventory »

The first step in configuring the export of audited data to the IT inventory management system is to set up a connection to the Codenica Inventory software. The configuration is similar to the configuration of the database in Codenica Inventory.

• See database settings »
• See chapter: Export to inventory »

Objects that are not supposed to be inventoried can be excluded from the export process using a filter. For instance, you can use the filter to exclude hardware in the "Serial Port" category or software in the "Games" category. Filtering conditions are arbitrary, and their number is unlimited. They depend entirely on the user's preferences.

• Filtering Mechanism Operation »
• See chapter: Export to inventory »

To avoid overloading a particular inventory, users often do not want to inventory all object properties, but only those that are of interest in a particular case. These settings are designed precisely for this purpose. They allow you to select only the object properties that are supposed to be exported to the Codenica Inventory system.

See chapter: Export to inventory »

Update object data... - These options enable or disable data updates in an inventory with data acquired in an audit. Often, users prefer to retain custom data in inventoried objects (these are more complete data, especially complemented by the user) instead of automatically introducing data from objects recognized in an audit. In such cases, these options can be disabled, and the export can focus exclusively on newly-identified objects. You can also enable them and configure only the properties expected to be updated in the Export - Object Properties settings tab (see section above).

Export object relationships... - These options are designed to analyze the relationships of single objects recognized in an audit and export them, together with relationships, to an inventory. You can decide which related objects of a given type are to be exported and which ones should be skipped (according to individual preferences).

See chapter: Export to inventory »

These options allow you to customize the rendered color scheme for the application and the appearance of borders inside controls with split containers (split containers are containers with bars that allow you to modify the size of panels with controls placed inside).