This sub-section allows creating an unlimited number of Object types and custom management fields. Here, for instance, you may add administrative fields to the PCs that are automatically uploaded by Synexsys Inventory.
The window is vertically divided into two parts. On the left, you may create Objects and custom management fields. On the right you may view the identification details of Objects and Fields.
An Object can represent virtually any asset or equipment you have decided to manage with Synexsys, whether it is hardware or not. For instance: PDAs, scanners, tower CD duplicators, external recording devices, projectors, copiers, faxes, cellular phones, radio equipment, measuring devices, machines, stock, loan centres, office furniture, vehicles, libraries, books, CDs, internal applications, projects, training courses, leasing contracts, maintenance contracts, etc.
Whenever a new Object type is defined in this panel, a new container is created, and not its contents. You may create Object occurrences in the "Objects" sub-section of the "Inventory" Section.
Once the Object has been created, you can then define the fields that will be used to identify and describe it. For instance: Identifier, Provider, Purchase Date, Price, Warranty, Brand, Model, Technical Features a, b, c, etc. , Budget, Location, etc.
Management fields can be of different types and be subject to strict input rules, so as to avoid ambiguity and input errors. They are associated with information Categories for greater clarity.
![]() |
Place the cursor on the left column of the Object definition grid and select "New object" from the context menu (right-click) or press the F9 function key. A screen will ask you to name the Object. |
|
|
![]() |
The first thing that needs to be defined for each Object is a system field named Visual Key. This field will be displayed by the Synexsys Console in the trees and in the Object lists. The visual key allows the visual recognition of an Object in the Synexsys Console. The Visual Key doesn't need to be unique, but it is required since Synexsys doesn't know which value needs to be displayed if it doesn't exist. For PCs, the default Visual Key is the HOSTNAME, but it can be modified as needed. When Synexsys displays an Object in lists or trees, only one of the Object's features is visible. At times, the Object's true identifier (see Merging Key below) can be different from the one you wish the system to display in order to manipulate the Objects on screen. For instance, a PC's serial number can be defined as true identifier (Merging Key), but you may prefer working with its HOSTNAME instead. This is the reason why Synexsys allows choosing the feature you wish the system to display. |
|
|
![]() |
If you intend to import data to Synexsys using SXSimport, or if you want to be protected against SID losses in a PC, you should create a Merging Key. The Merging Key can identify Objects during an import process with SXSimport and update the existing information with the new source data. For instance, import the users list and update it daily. The basic condition for the merge process to function properly requires the value of the Merging Key present in Synexsys to correspond exactly to the value that will be imported by SXSimport (more information on the Merging Key). |
|
|
![]() |
IMPORTANT The Merging Key is also used to avoid duplicates from being created whenever the Synexsys identification file (SID.TXT) disappears from a PC, for instance, when the hard disk is replaced or cloned. In this case, the Merging Key allows the Synexsys Server to automatically consolidate audit data with the PC's original data. (more information on merging PC data) |
|
|
![]() |
Exclusively for PCs, a Preliminary Key can be defined. This key allows entering or importing information on the PCs before they are audited by the Synexsys agent. This assures that the Synexsys Server will automatically merge the data that has been previously entered with the data resulting from the automatic audit process. The PC's serial number is normally used as Preliminary Key. (more information regarding pre-entering PC information) |
|
|
![]() |
The object's icon can be changed using the context menu or the key combination CTRL+i. |
![]() |
READ BEFORE STARTING The fields you create are associated to the Object for which they are defined, to avoid polluting other Objects with useless fields. At times, using identical fields for Objects of a different type is necessary. So, to solve this problem, Synexsys allows creating what is known as common fields. Learn more about this possibility by clicking here BEFORE defining custom fields. |
|
|
![]() |
Before creating fields, you need to create the Categories that will contain such fields. To create a Category, place the cursor on the left column of the Object definition grid and select "New category" from the context menu (right-click), or press the F10 function key. Then, name the Category. |
|
|
![]() |
Place the cursor on the Category under which you wish to create a field and select "New field" from the context menu. A sub-menu will allow you to select the type of data the field will contain. Once you've made the selection, the system automatically takes you to the area where you may edit the field's details, on the right-hand side of the screen. ALTERNATIVES: Use the "New" button to create fields. This button is located in the lower right-hand side of the screen and makes the creation of consecutive fields easier. You can also use the "Create as" menu option or button. This button allow you to create several fields based on the same model. |
|
|
![]() |
You may modify the order in which fields are displayed using the context menu options or the control key combinations CTRL+U (Up) CTRL+D (Down). |
![]() |
REMARK |
A field's type cannot be changed once it has been created. If you have made a mistake, delete the field and create a new one. |
|
||
![]() |
HINT |
Use the context menu options or the control key combinations CTRL+D / CTRL+U to fully expand all Categories and all of an Object's nodes. |
|
||
![]() |
ID (system) |
Field internal reference. It is used for support and advanced options. |
|
||
![]() |
Order (system) |
Order in which the field appears in its Category (see below how to change the order). |
|
||
![]() |
Name |
Field label. The field's label can be changed at any time. |
|
||
![]() |
Mandatory |
The user will be forced to enter a value in this field while editing the Summary tab. Mandatory fields are displayed in red in the Summary tab. |
|
||
![]() |
Display |
This option will display the field in the helpdesk form. |
|
||
![]() |
If needed, you may define a mask that will determine the format in which data is entered. For example, to force a specific telephone number format. |
|
|
||
![]() |
Default value |
Enter here the default value you wish the system to display when a new standard Object type occurrence is created. The system does not check this value's consistency with the context. |
|
||
HINT: For date type fields, you may enter the value @TODAY so the system retrieves the current date by default whenever a new Object occurrence is created. |
||
|
||
![]() |
Minimum / Maximum |
Authorised threshold values. |
|
||
![]() |
Choice |
List of valid values. Enter a value in each line followed by the ENTER key. These values are displayed to the user in a selection list. If the option "Force choice in list" (see below) is selected, only values from the list will be valid. If the option is not active, the user may select any element from the list or enter a value in this field. If the field isn't mandatory, it can be left empty. |
|
||
HINT: If you wish to sort the selection list in alphabetical order, enter the various elements without worrying about their order and click the "A/Z" button when you are finished. Elements will then be automatically sorted. |
||
|
||
![]() |
Number of visible lines |
This value determines the number of lines displayed on screen for plain text (Text) and formatted text (RichText) fields. |
|
||
![]() |
INI File Registry Key |
Information on Registry or INI File type fields. Click here to see the details. |