TEAMS - Dictionaries in Settings

Owned by Natallia Navumava
Last updated: Jul 25, 2024Version comment
4 min read

The tab allows to manage dictionaries on the organization level and has the following subtabs:

Each subtab has the following elements:

  1. Table with the list of records of a dictionary.

    1. The list includes both active and inactive records. Active records are displayed as usual table rows, whereas inactive records are displayed as grey rows.

      1. If a dictionary record references another entity that has already become inactive, then a corresponding cell is displayed with the strikethrough style of the text.

    2. Each table supports pagination, sorting, filtering, and grouping. 

    3. A quick menu of each record contains the following options:

      1. Edit - available for active records only. Navigates to an edit sidebar.

      2. Delete - available for active records only. Allows to delete (deactivate) a record after confirmation. If the user confirms it, the record becomes inactive. 

      3. Restore - available for inactive records only. Allows to restore a record after confirmation. If the user confirms it, the record becomes active again.

  2. Add button, which navigates the user to a dictionary record creation sidebar.

 

Vendors

The Vendors tab contains the list of all existing Vendors.

The tab provides all the common dictionary management functionality described above.

image-20240417-173132.png

Vendor has the following attributes:

  1. Vendor - the name of a vendor. Required attribute. Must be unique.

  2. Working hours per day - number of working hours per day. Required attribute. Must be in the range of 0-24.

image-20240417-173216.png

The Working hours per day field is not available for editing after Vendor creation.

Vendor Locations

Vendor Location is a location where a Vendor performs its work. This tab allows to manage the list of such locations for each vendor.

The tab provides all the common dictionary management functionality described above.

For each Vendor Location, a Location Type must be specified. There are 3 available Location Types:

  1. Onshore

  2. Offshore

  3. Nearshore

Please note, that it is forbidden to create Vendor Location with the same combination of Vendor and Country twice.

The only attribute that is available for editing a Vendor Location record is the Location Type.

Once the Vendor Location record is created, a Country specified becomes available during the creation of a Rate Card of a Vendor Specified. (please see, https://telescope-ai.atlassian.net/wiki/spaces/EPMDMO/pages/1938751497/TEAMS+-+Finance#Adding-Rate-Card)

Locations

The Locations tab allows you to manage two dictionaries Countries and Cities.

The tab provides all the common dictionary management functionality described above.

Each City belongs to a Country. Cities in the table are grouped by Country by default.

Names of Countries must be unique across the Countries dictionary.

Names of Cities must be unique across the Country.

To use Locations in Rate Cards (please see, https://telescope-ai.atlassian.net/wiki/spaces/EPMDMO/pages/1938751497/TEAMS+-+Finance#Adding-Rate-Card), it is necessary to add an appropriate Vendor Location to the Vendor Locations dictionary.

Cost Types

Cost Types represent the classification of costs by their aim. The dictionary contains entities of two types: Cost Categories and Cost Types. The dictionary has a hierarchical structure, where Cost Categories may contain other Cost Categories and Cost Types. Hence, a Cost Category should be used to group other Cost Categories and Types. Whereas occurred costs and budget values are always linked to Cost Types and not Cost Categories.

The tab provides all the common dictionary management functionality described above.

In the stage of creating a new record, a user must specify all required fields and optionally the Parent Category field. Empty Parent Category field means root-level.

When editing a Cost Type (or Cost Category), you have the option to change its path and assign a new Parent Category. Alternatively, you can unassign a Parent Category if you want to move the entity to the root level.

Added Cost Types are used during the creation of Other Costs (please see, https://telescope-ai.atlassian.net/wiki/spaces/EPMDMO/pages/1774387217/TEAMS+-+Resource+Plan#Adding-Other-Cost).