Understanding the Trackor Tree
Intro to Trackor Types
Before learning about the Trackor Tree, you must first understand Trackors and Trackor Types. OneVizion is comprised of Trackors or "Trackor/Object" references. This is different from a traditional database where data is stored in tables and rows of data. A Trackor is an individual data element that can have many relationships in place. A Trackor Type is a designation for Trackors. For example, a Trackor Type may be “Permits”, and the Trackors would be the individual permits you wish to organize within OneVizion. A Trackor Type can have many attributes associated with it (i.e., all the data points you wish to track about permits.
OneVizion allows you to piece the information together in endless combinations, and build as many relationships between different Trackor Types as you like. The Trackor Tree is the hierarchical structure that contains all of the Trackor Types, defines their parent/child relationships, and displays them in a simple tree.
Note that a Trackor Type can be associated with multiple parent/child relationships, resulting in some Trackor Types appearing in multiple places within the Trackor Tree.
In order for Trackor Types to be both visible and usable, they need to be a part of the Trackor Tree. The Trackor Tree is the hierarchical structure that contains all of the Trackor Types, defines their parent/child relationships, and displays them in a simple and clear way. A new Trackor Type is added to the root of the Trackor Tree if it has no parent defined by the user.
You can find the Trackor Tree in the Menu Bar to the left.
When you are setting up the Trackor Tree page for the first time, it will include only the topmost level of the hierarchy (or configuration), so you will have to add your Trackor Types in a top-down manner, starting from the top-level Trackor Types and adding subsequent child and grandchild ones.
The Trackor Tree view can be expanded to view grandchildren.
Tip: Use the Trackor Selector when a new relationship might pollute the Trackor Tree.
After you add the Trackor Type to the Tree, you must set permissions for users to be able to read, add, edit, or delete the Trackor.
Adding a Trackor Type to the Trackor Tree
You can add a Trackor Type to the Trackor Tree by highlighting the parent Trackor Type and clicking the Add button.
This will open the General tab of the New Relation Applet.
General Tab
The General tab contains general information about the new Trackor Type's relations.
Field Name | Field Description |
|---|---|
Memo | A horizontal representation of the Trackor Tree branch you are adding the new Trackor Type to. This field will display every parent Trackor Type for the Trackor Type you are adding to the Trackor Tree. |
Relation Type ID | Contains the relation ID number. The ID is automatically assigned by the system upon creation. This number is used for Reports, Rules, and Imports. |
Trackor* | Contains the name of the Trackor Type you are adding. Click the Ellipsis Icon to choose from the available Trackor Types. |
Cardinality* | Indicates the type of parent Trackor Type relationship. If you want the Trackor Type to have just a one parent, select “1 to many”. ”Many to many” cardinality will complicate any future relations that this Trackor Type will be involved in. Only select this if you have a clear understanding of entity relationships in databases. |
Unique By | Enables you to specify how a particular Trackor Record is unique from other Trackor Records of the same type. |
Color Code | Allows to differentiate the parent/child relationship with a color highlight. You can select from the available colors defined in the system. |
PL/SQL ID Reference | This feature allows Administrators to promote rules without having to hardcode the relation ID. In the past, the PL/SQL ID reference had to be hardcoded into the Rule. This feature will simplify the process of creating rules. We have added a Relation Type ID reference to the ID package. It is now accessible via: id.*trackor_type_name*.rel.*parent_trackor_type_name*. |
Child Requires Parent | When this checkbox is checked, the system will require a parent to be specified when adding a new Trackor Record. |
On Parent Delete Cascade | This checkbox is available only if cardinality is set to “1 to many”. |
Lockable | Locks the parent of a Trackor Record to prevent changes in the relationship. |
Show All Records in Trackor Container | When selected, all records related to a Trackor Record will be displayed regardless of what level of Trackor Tree is open. In those cases:
|
The Role Privs Tab
The Role Privs tab contains the Security Privileges settings for Security Roles applicable to the Trackor Tree entry.
For more information on Security Roles and Privileges please see the Security Roles documentation.
Components Audit Log Tab
The Components Audit Log tab records and displays all the changes made to Components. It will appear after you create a Trackor Tree entry.
Role Lock Privs Tab
If the Lockable checkbox is checked after you create the Trackor Tree entry the Role Lock Privs Tab will appear along with the Components Audit Log tab. It will allow the admin to pick the users that will have the ability to lock or unlock certain fields.
A checked box in the Lock column will allow the corresponding role to lock the fields, and one in the Unlock column – to unlock them.
To mass assign the Lock and Unlock columns, click the Select/Deselect All Privs double tick in the Lock and Unlock column headers.
Rearranging the Trackor Tree
A newly added Trackor Type will appear in the tree after the trackors that were previously added to the same level.
You can rearrange the Trackor Types by highlighting the trackor you wish to move and clicking the “Up” and “Down“ buttons.
This only moves the currently selected Trackor Type relative to the other Trackor Types belonging to the same level of the Trackor Tree and does not change any parent/child relationships between Trackor Types.
When you click on a Trackor Type, all matching nodes will highlight in the system color everywhere a selected Trackor Type exists in the tree.
To help users understand the relationship type for a node, The Many to many icon shows nodes with the many-to-many relation. Nodes without this icon use the one-to-many relation.
