Structure

 

In this section, we'll begin by establishing the foundational structure and elements of our application. This includes creating Trackor Types, setting up their parent-child relationships (Trackor Tree), and adding a new menu with menu items. We'll also populate each Trackor Type with basic fields in the General Info tab to get the groundwork in place.

 

Build the Trackor Types

The case study Equipment Checkout application has the following Trackor Types:

  • Warehouse Location

  • Equipment Master

  • Asset

  • Transactions

  • Assignee

Considerations

There are several common decisions that must be made when building Trackor Types.

  • Trackor Type Name and Prefix: Ensure each is unique. The prefix, visible system-wide, should clearly reflect the Trackor Type for easy user recognition.

  • Key Generation: Should the system auto-generate the field that identifies each Trackor record (Xitor key) when new records are added or not? What is the key format?

  • Cloning: Is cloning of a Trackor Record permitted for this Trackor Type?

  • Workplan: Will the Trackor Type include a workplan?

Case Study: Trackor Types

For our case study Equipment Checkout app, we are going to:

  • set up automatic key generation for the Transaction, Asset, and Equipment Master Trackor Types, and manual key generation on the Location Trackor Type;

  • allow Cloning only on the Asset Trackor Type (this can be adjusted later);

  • and will not include a Workplan anywhere in the app. (Workplans are always added after Trackor Type creation and can be added later.)

See detailed documentation about workplans on the User Guide. https://onevizion.atlassian.net/wiki/spaces/USER/pages/279773242

 

Create Trackor Types

Create Trackor Types

1

Navigate to Dev Center > Design Applications > Trackor Types.

2

To create a Trackor Type, press the Add button. A new window will appear.

Populate the fields on the “General” tab first.

3

Create a Trackor Type Demo Video:

In this video, we create a single Trackor Type by completing the General tab. Since we will manually input the Trackor Records for this Trackor Type, we can skip the Key Generation tab.

4

Some of the key fields we populated on our Trackor Type:

  • Trackor Type Label – Represents the name of your Trackor Type that end users will see and reference.

  • Trackor Type Name – Represents the database name. This should not be changed change after Trackor Type creation.

  • “Item ID” Label – The label name of your key field (Xitor_Key)

  • “Class” Label - The label of your Xitor_Class field.

  • Prefix Label – All fields created in this Trackor will share the same Prefix Label defined here and shown throughout the platform every time the field is displayed.

Many of these fields will auto-populate after entering your “Trackor Type Label” field.

 

5

Let’s build the next Trackor Type in our list.

This time, we want the system to generate the key field for our Trackor Records, so we will complete the Key Generation tab.

Notice on this tab that Generate Key Automatically is checked. When Trackor Records are created in this Trackor Type, the key field (Xitor_Key) value will auto-generate based on an ascending numeric order. The “A” Static Text will be displayed as a prefix before the system generated ID number. Ex: “A00001.”

 

6

We added three additional Trackor Types in order to complete the process of creating 5 new Trackor Types.

 

For further details on Trackor Types, please visit the User Guide page: https://onevizion.atlassian.net/wiki/spaces/~62aa38907b388c0067220e6c/pages/277349063

 

Trackor Tree

The Vizion Platform allows you to piece information together in endless combinations and build many relationships between different Trackor Types. 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. A Trackor Type can be part of the tree root or nested under one or many other Trackor Types.

Case Study: Trackor Tree

Let’s put our case study Trackor Types into a Trackor Tree including the following relationships:

  • Warehouse Location (parent)

    • Asset (child)

      • Transaction (grandchild)

  • Equipment Master

  • Assignee

    • Transaction (child)

Notice that the Transaction Trackor Type is in the tree twice, once as a child of Assignee and once as a grandchild of Warehouse Location. It is acceptable for a Trackor Type to have multiple Parent Relations as found in this example.

Below is a visual depiction of our new Trackor Types and their relations to each other. All of these relations are of a “1 to Many” relationship from Parent to Child. For example 1 “Home Location” record can have 1 or many “Asset Items” records.

 

 

Below is a picture of the completed Trackor Tree structure that we will build out in the steps below. The structure is based on the diagram seen above.

 

Steps to Arrange the Trackor Tree

 

Steps to Arrange the Trackor Tree

 

1

In the menu, navigate to Dev Center > Design Applications > Trackor Tree.

2

The Trackor Tree page will always contain the Trackor Root by default. As it is the only item on Tree, it is highlighted. As we navigate, you will find the selected Trackor Type in the tree will always be highlighted in the system color.

 

3

Let’s assign our Trackor Types to the Trackor Tree in order to define our relations.

  1. Click Add

  2. Click the ellipsis to open the selector field and select the Trackor Type.

  3. In this case, we will select Home Location as our Trackor Type. Click OK.

  4. Review your Relation Settings. In this case we will not make further updates, so just click OK.

The Relation has been added in which Home Location is a child relation of the Trackor Root by default.

4

Repeat the steps above to build all of the relations for the Trackor Tree including all of the Trackor Types.

In the video, notice Home Location is selected (indicated by highlight color). When we press Add, the selected Trackor Type will be the parent of the added Trackor Type. In this case we will add Asset Items as a child relation.

We have now arranged our Trackor Type relations in the Trackor Tree.

For more information on the Trackor Tree, please visit the User Guide page:
https://onevizion.atlassian.net/wiki/spaces/USER/pages/277317887

 

Build Menu

Once the Trackor Types and Tree are built, you will create a Menu and will add “Menu Items” representing each Trackor Type. Creating a Menu allows you as an Admin to arrange an order for your Menu Items and encourage a simple navigation experience for your end users. Clicking on a Menu Item will open the affiliated Trackor Type page.

At this point, our Case Study Menu will only include Menu Items representing our Trackor Types. We will revisit and refine the menu later to add additional Menu Items representing additional page types.

Case Study: Menu

Create a Menu

Create a Menu

1

Navigate to Dev Center > Build Applications > Menu.

2

Click on Add Menu Application in the upper left.

Populate the Fields. Typically the Applications Name and Label values will be the same.

Select an icon to represent your new Menu using the selector field. In this example, we selected the “Maintenance” icon that includes a wrench.

Once complete, click OK to save and create your new Menu.

 

3

After saving, your new Menu will be listed with the given Applications Name (ex: “Equipment Checkout”) under Menu at the top and “Top Menu” will appear by default as a selected item in Yellow.

Akin to constructing the Trackor Tree, populating the Menu involves assigning “Menu Items” to represent your Trackor Types, following a similar approach.

 

4

Press Add to assign your first Menu Item.

After pressing “Add” a new window appears.

  • Ensure Menu Item radio button is selected.

  • In the Primary Trackor Type field select your desired Trackor Type (ex: Asset Items).

    • The Label Text field will auto-populate. If you would like an alternative name for your Menu Item, you can revise this value.

  • Select a View & Filter – Selecting items will force an end user’s page to always default to the selected View and or Filter. If you would like users to be able to return to their own View and Filter as they visit this Menu item, then don’t populate a value.

  • Select an Icon

  • Visible should be checked. Otherwise, your Menu Item will NOT be displayed on the Menu for end users.

Press OK to create your Menu Item and assign it to the Top Menu.

 

5

The Asset Items Menu item is now assigned to the Equipment Checkout Menu.

 

6

Video: Watch as we create and assign additional Menu Items for other Trackor Types and Menu Sub-Groups which works to expand or hide additional Menu Items.

We added direct links to the Trackor Types in a Sub-Menu named “Support Tables”. This will allow users to get direct access to the Trackor Type grids.

 

7

With a Menu now established, after refreshing your browser page, you will see the Equipment Checkout Menu and can use it to navigate to the pages representing your Trackor Types.

Note: We will continue to revise and explore our Menu and Menu Items as additional pages are added during the configuration process.

 

 

Continue Training

https://onevizion.atlassian.net/wiki/spaces/USER/pages/3068264480