Name | Comment |
LS_AUTHENTICATION_METHOD | Contains authentication methods available for the LS_LDAP_SERVER table |
LS_EMAIL | Contains email addresses for license server users (email) |
LS_EMAIL_TYPE | Contains email types stored in the LS_EMAIL table |
LS_EVENT | Lists license server events with a date/time component (Event) |
LS_EVENT_DETAIL | Contains license server event details referenced by license pool, number of licenses available, and number of licenses used (EventDetails) |
LS_EVENT_TYPE | Contains event types from the license server (EventType) |
LS_EVENT_USER | Lists users affected by the license server event with product and license type (EventUser) |
LS_LDAP_FIELD | Relates the LS_LDAP_SERVER table to a user field that stores the LDAP_FIELD information |
LS_LDAP_SERVER | Contains LDAP and Active Directory (AD) servers configured in the license server (lsldapserver) |
LS_LICENSE | Lists licenses added to the license server (License) |
LS_LICENSE_TYPE | Lists types of licenses available in the license server (LicenseType) |
LS_PHONE | Lists user phone numbers (PhoneNum) |
LS_PHONE_TYPE | Lists types of phone numbers stored in the LS_PHONE table. Phone number types are stored in the license server application only. |
LS_POOL | Contains a list of license pools used by the license server. A pool is an allocation of product licenses that can have usage limits. (Pool) |
LS_PRODUCT_NAME | Products supported by the license server (ProductName) |
LS_SSO_SETTING | Describes the single sign-on setting for the license server |
LS_USER | Users registered with the license server (lsuser) |
LS_USER_FIELD | Contains user field information |
LS_USER_LICENSE | Contains associations of users to licenses, often in a pool (UserLicense) |
LS_USER_LICENSE_TYPE | Lists the available user license types. This is an enumerated value in the source system, but in the data warehouse, it is translated to a lookup table for end user use. |
QAW_LOAD_TEST | Represents a load test. Provides information about load test playback sessions. |
QAW_PLAYBACK_SESSION | User-initiated session that performs a test in QA Wizard Pro. From the user interface, the run starts from the Run, Run Multiple, Run Remote, Run Multiple Remote, Run Load Test, Run Main Script, or Run Main Script Remote commands. Debug Script, Record Into Script, and Debug Main Script commands are not included because they are not recorded. From the command line, the run starts using QAWRunScript or QAWRunLoadTest with any options. |
QAW_SCRIPT | A script that ran. |
QAW_SCRIPT_LINE_RUN | An individual line of script that ran. |
QAW_SCRIPT_LINE_RUN_MESSAGE | A message (error, warning, or output) that occurred on a script line during playback. |
QAW_SCRIPT_RUN | An instance of a script that ran. |
QAW_STACK_FRAME | A group of related script lines in the context of a script, function, or subroutine call or Try, Catch, or Finally block. Provides a logical division of the script run. A new frame is created for each context and added to the call stack. |
REP_AVAILABLE_TT_REPORT | Contains a row for each report created in Helix ALM. Used to display Helix ALM reports in ALMRP dashboards. |
REP_SOURCE | Lists the source systems that populate the data warehouse |
REP_USER | Lists the association between users of different products. Users are mapped between Surround SCM (SCM), Helix ALM License Server (LC), and Helix ALM (TTP, TCM, and RM). |
REP_USER_QAW_USER | Maps a data warehouse user to one or more QA Wizard Pro users in one or more sources. |
REP_USER_SCM_USER | Maps a data warehouse user to one or more Surround SCM users in one or more sources |
REP_USER_TT_USER | Maps a data warehouse user to one or more Helix ALM users in one or more sources. Helix ALM users are defined by project so there can be multiple Helix ALM users per data warehouse user. The user may also exist across many Helix ALM sources. |
SCM_ARCHIVE_FILE | Contains the master list of files in Surround SCM (ARCHIVEFILE) |
SCM_ARCHIVE_FILE_TYPE | Lookup table for the bitwise FILE_TYPE field in the ARCHIVE_FILE table |
SCM_BRANCH | Lists the branches for the mainline branches in the RDBMS database (BRANCH) |
SCM_BRANCH_CREATION | Information about who created a branch and when |
SCM_BRANCH_FILE | Associates SCM_BRANCH to SCM_ARCHIVE_FILE. A branched file also has its own attributes such as status, current version, and time last renewed. (BranchFile) |
SCM_BRANCH_FILE_STATUS | Decodes the bitwise STATUS_FLAG values in the SCM_BRANCH_FILE table |
SCM_BRANCH_FILE_VERSION | Contains file version data for Surround SCM branches (BranchFileVersion) |
SCM_BRANCH_FILE_VERSION_FLAG | Decodes the version flag on the SCM_BRANCH_FILE_VERSION table |
SCM_BRANCH_FLAG | Lists allowed flags for a branch. A branch can have multiple flags simultaneously. |
SCM_BRANCH_FLAG_BRANCH | Breaks out the BRANCH_FLAG attribute from the SCM_BRANCH table in a many-to-many relationship for branches with multiple flags |
SCM_BRANCH_REPOSITORY | Contains repository data for Surround SCM branches (BranchRepository) |
SCM_BRANCH_REPO_PATH | Lists the fully qualified path to the repository. Useful when constructing sscm links to the application in reports. |
SCM_CHANGELIST | Contains information for pending and committed changelists (Changelist) |
SCM_CHANGELIST_CUSTOM_FLDVAL | Contains the custom field values associated with a changelist (ChangeListCustomFieldValue) |
SCM_CHANGELIST_EVENT | Contains the events associated with a changelist (Changelistevent) |
SCM_CHECKOUT_FILE | Contains all file check out information (CheckoutFile) |
SCM_COMMAND | Lists security commands used to assign Surround SCM permissions |
SCM_CUSTOM_FIELD | Contains custom field rules used in filters, reports, and triggers (ScmCustomFlds) |
SCM_EVENT | Contains a list of events performed in Surround SCM (event) |
SCM_EVENT_CUSTOM_FIELD_VALUE | Contains historical information about file custom field value changes (eventcustomfieldvalue) |
SCM_EVENT_DEFECT_ATTACH | Relates a Helix ALM defect to a Surround SCM file and the event that describes the attachment |
SCM_EVENT_REQUIREMENT_ATTACH | Relates a Helix ALM defect to a Surround SCM file and the event that describes the attachment |
SCM_EVENT_TESTCASE_ATTACH | Relates a Helix ALM test case to a Surround SCM file and the event that describes the attachment |
SCM_EVENT_TYPE | Lists the event type used for the SCM_EVENT table. This is an enum value in the source product. For reporting purposes, the value is decoded into this table and a foreign key was created to the SCM_EVENT table. |
SCM_FILE_CUSTOM_FIELD_VALUE | Contains all file custom field values (filecustomfieldvalue) |
SCM_FILE_REVISION | Contains the master list of file revisions in Surround SCM (filerevision) |
SCM_GROUP | Contains information about Surround SCM security groups (SCMGroups) |
SCM_GROUP_COMMAND | Lists commands for a Surround SCM security group. The commands are a list in the Surround SCM code. (scmgroupcmds) |
SCM_LABEL | Contains all Surround SCM labels (Label) |
SCM_LABEL_EVENT | Contains all events related to Surround SCM labels (Labelevent) |
SCM_LABEL_EVENT_TYPE | List of Surround SCM label event types |
SCM_LABEL_FILE | Contains label association and file information (Labelfile) |
SCM_MAINLINE | Contains the list of Surround SCM mainline branches that reside in the RDBMS database (Mainline) |
SCM_MERGE_EVENT | Stores the file versions that were merged into the same file on a different branch |
SCM_REPOSITORY | Contains the master list of Surround SCM repositories (Repository) |
SCM_STATE | Contains information about Surround SCM workflow states (scmstates) |
SCM_TTP_DB_CONFIGURATION | Contains information about Helix ALM connections configured in Surround SCM (Helix ALMDBCONF) |
SCM_USER | Contains information about Surround SCM users (scmusers) |
SCM_USER_GROUP | Contains users in Surround SCM security groups (scmusergrp) |
SCM_WORKFLOW | Contains information about Surround SCM workflows (scmworkflows) |
SCM_WORKFLOW_STATE | Contains states associated with Surround SCM workflows (scmwrkflwstates) |
TT_ASSIGNED_DEFECT_USER | Lists the users currently assigned to a defect. Can also be used to view the defects assigned to a user across multiple projects. This table is not available in Helix ALM and is a break out of a multi-list. |
TT_ASSIGNED_DOCUMENT_USER | Lists the users currently assigned to a requirement document. Can also be used to view the documents assigned to a user to across multiple projects. This table is not in available in Helix ALM and is a break out of a multi-list. |
TT_ASSIGNED_REQUIREMENT_USER | Lists the users currently assigned to a requirement. Can also be used to view the requirements assigned to a user across multiple projects. This table is not in available in Helix ALM and is a break out of a multi-list. |
TT_ASSIGNED_TESTCASE_USER | Lists the users currently assigned to a test case. Can also be used to view the test cases assigned to a user across multiple projects. This table is not in available in Helix ALM and is a break out of a multi-list. |
TT_ASSIGNED_TESTRUN_USER | Lists the users currently assigned to a test run. Can also be used to view the test runs assigned to a user across multiple projects. This table is not in available in Helix ALM and is a break out of a multi-list. |
TT_AUDITLOG | Contains the changes made to defect, test case or test run records. Each row records changes made to an entity and information regarding who, when, and how changes were made. Change information isstored in such a way that, if the user information is modified or deleted at a later date, the audit log table represents the information as it was when the changes were made. |
TT_CUSTOM_DEFECT_EVENT_VAL | Contains custom field values for defect workflow events. Each row represents one custom field value for a single event. This table has a many-to-one relationship with the TT_DEFECT_EVENT and TT_FIELD_DEFINITION tables. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables, user/customer tables, or TT_CUSTOM_POPUP_FIELD tables are set depending on the list value type. |
TT_CUSTOM_DEFECT_VALUE | Contains information related to defect custom fields. Each table row represents one custom field value associated with a single defect. This table has a many-to-one relationship with the TT_DEFECT and TT_FIELD_DEFINITION table. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables, user/customer tables, or TT_CUSTOM_POPUP FIELD tables are set depending on list value type. (CUSTMVAL) |
TT_CUSTOM_DOCUMENT_EVENT_VAL | Contains custom field values for requirement document workflow events. Each table row represents one custom field value for a single event. This table has a many-to-one relationship with the TT_DOCUMENT_EVENT and the TT_FIELD_DEFINITION tables. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables, user/customer tables, or TT_CUSTOM_POPUP_FIELD tables are set depending value list type. (CSRDEVTVL) |
TT_CUSTOM_DOCUMENT_VALUE | Contains information related to custom fields on a requirement document. Each table row represents one custom field value associated with a single document. This table has a many-to-one relationship with the TT_DOCUMENT table and TT_FIELD_DEFINITION table. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables, user/customer tables, or TT_CUSTOM_POPUP_FIELD tables are set depending value list type. (CSDOCVAL) |
TT_CUSTOM_POPUP_FIELD | Contains custom field pop-up menu values. Each table row represents one pop-up menu item. This table has a many-to-one relationship with the TT_FIELD_POPUP_LIST table. Each row in this table has a pop-up menu record ID that matches a record ID in the TT_FIELD_POPUP_LIST table. (FLDCUSTM) |
TT_CUSTOM_REQMENT_EVENT_VAL | Contains custom field values for requirement workflow events. Each table row represents one custom field value for a single event. This table has a many-to-one relationship with the TT_REQUIREMENT_EVENT and the TT_FIELD_DEFINITION tables. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables, user/customer tables, or TT_CUSTOM_POPUP_FIELD tables are set depending on the list value type. (CSREVTVL) |
TT_CUSTOM_REQUIREMENT_VALUE | Contains information related to requirement custom fields. Each table row represents one custom field value associated with a single requirement. This table has a many-to-one relationship with the TT_REQUIREMENT and TT_FIELD_DEFINITION tables. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables, user/customer tables, or TT_CUSTOM_POPUP_FIELD tables are set depending on the list value type. (CSREQVAL) |
TT_CUSTOM_TESTCASE_EVENT_VAL | Contains custom field values for test case workflow events. Each table row represents one custom field value for a single event. This table has a many-to-one relationship with the TT_TESTCASE_EVENT and TT_FIELD_DEFINITION tables. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables, user/customer tables, or TT_CUSTOM_POPUP_FIELD tables are set depending on the list value type. (CSTTCEVTVAL) |
TT_CUSTOM_TESTCASE_VALUE | Contains information related to custom test case fields. Each table row represents one custom field value associated with a single test case. This table has a many-to-one relationship with the TT_TESTCASE table and TT_FIELD_DEFINITION tables. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables, user/customer tables, or TT_CUSTOM_POPUP_FIELD tables are set depending on the list value type. |
TT_CUSTOM_TESTRUN_EVENT_VAL | Contains custom field values for test run workflow events. Each table row represents one custom field value for a single event. This table has a many-to-one relationship with the TT_TESTRUN_EVENT and TT_FIELD_DEFINITION tables. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables, user/customer tables, or TT_CUSTOM_POPUP_FIELD tables are set depending on the list value type. (CSTTREVTVAL) |
TT_CUSTOM_TESTRUN_VALUE | Contains information related to test run custom fields. Each table row represents one custom field value associated with a single test run. This table has a many-to-one relationship with the TT_TESTRUN and TT_FIELD_DEFINITION tables. If the custom field is a drop-down list, comma-separated record IDs of inherent field tables or user/customer tables or TT_CUSTOM_POPUP_FIELD tables are set depending on the list value type. (CUSTTRVAL) |
TT_DATABASE_OPTION | Contains database option name/value pairs. |
TT_DEFECT | Contains Helix ALM defect information. Each table row represents one defect. Additional information associated with a defect is in the TT_DEFECT_EVENT table. This table has a one-to-one relationship with the TT_STATE, TT_FIELD_TYPE, TT_FIELD_PRODUCT, TT_FIELD_DISPOSITION, TT_FIELD_PRIORITY, TT_FIELD_COMPONENT, and TT_FIELD_SEVERITY tables. This table has a many-to-many relationship with the TT_USER table. (DEFECTS) |
TT_DEFECTITEM_ATTACHMENT | Contains defect file attachment information. Each table row represents one file attached to the defect record. (ATTACHMT) |
TT_DEFECT_ATTACHMENT | Contains defect file attachment information. Each table row represents one file attached to the defect report record. (ATTACHMT) |
TT_DEFECT_EVENT | Contains workflow event information for each event recorded on a defect. Each table row represents a single defect event. This table has a many-to-one relationship with the TT_DEFECT, TT_EVENT, TT_USER, and TT_STATE tables. (DEFECTEVTS) |
TT_DEFECT_EVENT_ASGN_USER | List of assigned users for a defect event. This table is not available in Helix ALM and is a break out of the multi-user AsgndUsers field. |
TT_DEFECT_EVENT_ATCHMT | Contains defect event file attachment information. Each table row represents one file attached to the record. This table has a many-to-one relationship with the TT_DEFECT_EVENT table. Each row has a reported by record ID that matches a record in the TT_DEFECT_EVENT table. (ATTACHMT) |
TT_DEFECT_LOG | Contains historical log information about changes made to defect records. Each row in this table represents a log entry in a defect record. Each row has a defect record ID that matches a record in the TT_DEFECT table. (DEFLOG) |
TT_DEFECT_REPORT | Contains defect reported by information. Each table row represents one defect report. This table has a many-to-one relationship with the TT_DEFECT table because Helix ALM allows multiple reports in one defect. Each row in this table has a defect record that matches a record in the TT_DEFECT table. (Reportby) |
TT_DEFECT_SELECT_FIELD | If the custom field is a pop-up menu, the selected values relate back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table. Not available in the Helix ALM application. |
TT_DEFECT_SELECT_USER | If the custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table. Not available in the Helix ALM application. |
TT_DEFEVENT_SELECT_FIELD | If the event custom field is a pop-up menu, the selected values relate back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table |
TT_DEFEVENT_SELECT_USER | If the defect event custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table |
TT_DOCEVENT_RESULT_STATE | Lists the states for a requirement document workflow event. In the source system, the Event.RsltStates field is a space-delimited list of states for the event. The data warehouse breaks these states into a normalized list for easier reporting. |
TT_DOCEVENT_SELECT_FIELD | If the requirement document custom field is a pop-up menu, the selected values relate back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table |
TT_DOCEVENT_SELECT_USER | If the requirement document custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table |
TT_DOCUMENT | Contains requirement document information. Each table row represents one requirement document. (DOCUMENT) |
TT_DOCUMENT_ATTACHMENT | Contains requirement document file attachment information. Each table row represents one file attached to the record. This table has a many-to-one relationship with the TT_DOCUMENT table. Each row has a reported by record ID that matches a record ID in the TT_DOCUMENT table. (ATTACHMT) |
TT_DOCUMENT_CHANGE | Contains the original values for fields that changed after a requirement document snapshot was created. The document always stores the current value. (DOCCHNGS) |
TT_DOCUMENT_EVENT | Contains workflow event information for each event recorded in a requirement document. Each table row represents a single document event. This table has a many-to-one relationship with the TT_DOCUMENT, TT_EVENT, TT_USER, and TT_STATE tables. (DOCEVTS) |
TT_DOCUMENT_EVENT_ASGN_USER | Lists assigned users for a requirement document event. This table is not available in Helix ALM and is a break out of the multi-user DocEvts.AsgndUsers field from the application. |
TT_DOCUMENT_EVENT_ATCHMT | Contains requirement document workflow event file attachment information. Each table row represents one file attached to the record. This table has a many-to-one relationship with the TT_DOCUMENT_EVENT table. Each row has a reported by record ID that matches a record ID in the TT_DOCUMENT_EVENT table. (ATTACHMT) |
TT_DOCUMENT_LOG | Contains historical log information about changes made to requirement document records. Each row in this table represents a log entry in one of the document records. Each row has a document record ID that matches a record in the TT_DOCUMENT table. (DOCLOG) |
TT_DOCUMENT_REQUIREMENT_TREE | Contains the requirement relationship tree for the current version of the requirement document (DOCTREE) |
TT_DOCUMENT_SELECT_FIELD | If the custom field is a pop-up menu, the selected values relate back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table |
TT_DOCUMENT_SELECT_USER | If the custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table |
TT_DOCUMENT_SNAPSHOT | Contains requirement document snapshot information. Each table row represents one document snapshot. (DOCSNPST) |
TT_EMAIL | Contains tracked email information. Each table row represents one email. This table has a one-to-one relationship with the group of tables that used to be emailassoc in the application (e.g., TT_EMAIL_DEFECT, TT_EMAIL_DOCUMENT, etc.). (EMAIL) |
TT_EMAIL_DEFECT | Contains information about defects that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
TT_EMAIL_DOCUMENT | Contains information about requirement documents that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
TT_EMAIL_RECIPIENT | Contains email recipient information. This table has a many-to-one relationship with the TT_EMAIL table.(EMAILRECP) |
TT_EMAIL_REQUIREMENT | Contains information about the requirements that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
TT_EMAIL_TESTCASE | Contains information about the test cases that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
TT_EMAIL_TESTRUN | Contains information about the test runs that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
TT_EMAIL_TYPE | Lists email types. Not available in the Helix ALM application. Used to describe email types to data warehouse users. |
TT_ENTITY_TYPE | Contains Helix ALM entity codes that correspond to the table they represent. Can be used filter states, events, and other areas based on a specific entity type |
TT_EVENT | Contains workflow event definition information. Each table row represents one event definition. This table has a many-to-one relationship with the TT_FIELD_DEFINITION table. (EVENTS) |
TT_EVENT_RESULT_STATE | List of states for a workflow event. In the source system, the Event.RsltStates field is a space-delimited list of states for the event. The data warehouse breaks these states into a normalized list for easier reporting. |
TT_EXTERNAL_PROVIDER | Contains external source control provider information (Git, GitHub, etc.) |
TT_FIELD_COMPONENT | Contains the Component field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDCOMP) |
TT_FIELD_DEFINITION | Contains definitions for fields of all entity types and event fields. Each table row represents a single field. Custom pop-up fields, for both entity and entity events, have many-to-one relationship with the TT_FIELD_POPUP_LIST table that links to pop-up menu items in TT_CUSTOM_POPUP_FIELD table. (FLDDFNTN) |
TT_FIELD_DISPOSITION | Contains the Disposition field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDDISPO) |
TT_FIELD_POPUP_LIST | Contains pop-up list names. The TT_FIELD_DEFINITION table maps to TT_FIELD_POPUP_LIST record for each pop-up menu item. The list of actual values for each pop-up menu is stored in the TT_CUSTOM_POPUP_FIELD table. This relationship generally exists only for FieldType of 1 (Dropdown), but in the data warehouse, all possible list items that relate to an encoded list type are pushed to this table as a custom list with values. (FLDPULIST) |
TT_FIELD_PRIORITY | Contains the Priority field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDPRIOR) |
TT_FIELD_PRODUCT | Contains the Product field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDPROD) |
TT_FIELD_REPRODUCED | Contains the Reproduced field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDREPRO) |
TT_FIELD_REQUIREMENT_PRIORITY | Contains the requirement Priority field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDRPRIO) |
TT_FIELD_SEVERITY | Contains the Severity field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDSEVER) |
TT_FIELD_STYLE | Contains field value style information |
TT_FIELD_STYLE_POPUP | Contains associations between field value styles and pop-up menu items or workflow states |
TT_FIELD_STYLE_STATE | Contains associations between fields and workflow states with field value styles |
TT_FIELD_TESTOBJECT_TYPE | Contains test object Type field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDTOTP) |
TT_FIELD_TYPE | Contains the Type field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDTYPE) |
TT_FOLDER | Contains folder information. Each table row represents one folder. Folder item information is in the area-specific TT_FOLDER_* tables (e.g., TT_FOLDER_DEFECT). This table has a one-to-many relationship with the TT_FOLDER_* tables. (FOLDER) |
TT_FOLDER_DEFECT | Contains folder information for defects. Each table row represents one folder item. This table has a many-to-one relationship with the TT_FOLDER table. (FLDRITEM) |
TT_FOLDER_DETAIL | Contains the additional folder details for the Folder table (FLDRDTL) |
TT_FOLDER_DOCUMENT | Contains folder information for requirement documents. Each table row represents one folder item. This table has a many-to-one relationship with the TT_FOLDER table. (FLDRITEM) |
TT_FOLDER_LOG | Contains historical log information about changes to folders. Each row in this table represents a log entry for a folder. Each row has a folder record that matches a record in the TT_FOLDER table. (FLDRLOG) |
TT_FOLDER_REQUIREMENT | Contains folder information for requirements. Each table row represents one folder item. This table has a many-to-one relationship with the TT_FOLDER table. (FLDRITEM) |
TT_FOLDER_TESTCASE | Contains folder information for test cases. Each table row represents one folder item. This table has a many-to-one relationship with the TT_FOLDER table. (FLDRITEM) |
TT_FOLDER_TESTRUN | Contains folder information for test runs. Each table row represents one folder item. This table has a many-to-one relationship with the TT_FOLDER table. (FLDRITEM) |
TT_FOLDER_TYPE | Contains folder type information. Each table row represents one type value. (FLDRTYP) |
TT_LINK | Contains a list of items added to a link (LINKS) |
TT_LINK_DEFINITION | Contains a list of user-defined link definitions (LINKDFNTN) |
TT_LINK_HISTORY | Contains a history of changes made to links (LINKHISTRY) |
TT_LINK_ITEM | Contains information for a single item in a link in the TT_LINK table (LINKITEM) |
TT_LINK_WORKFLOW | Contains the options that describe the workflow behavior for items in the TT_LINK_DEFINITION table (LINKWRKFLW) |
TT_LOCATION_TYPE | Breaks out the list of Helix ALM location types. This table is not available in Helix ALM. |
TT_NOTIFY_DEFECT_USER | Lists users or customers to notify about defect changes |
TT_NOTIFY_DOCUMENT_USER | Lists users or customers to notify about requirement document changes |
TT_NOTIFY_REQUIREMENT_USER | Lists users or customers to notify about requirement changes |
TT_NOTIFY_TESTCASE_USER | Lists users or customers to notify about test case changes |
TT_NOTIFY_TESTRUN_USER | Lists users or customers to notify about test run changes |
TT_PHONE_TYPE | Lists phone number types allowed for Helix ALM users |
TT_PROJECT | Contains the list of Helix ALM projects stored in the RDBMS database (Helix ALMJECTS) |
TT_REQEVENT_RESULT_STATE | Lists the states for a requirement workflow event. In the source system, the Event.RsltStates field is a space-delimited list of states for the event. The data warehouse breaks these states into a normalized list for easier reporting. |
TT_REQEVENT_SELECT_FIELD | If the requirement custom field is a pop-up menu, the selected values relate back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table |
TT_REQEVENT_SELECT_USER | If the requirement custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table |
TT_REQMENT_EVENT_ATCHMT | Contains requirement workflow event file attachment information. Each table row represents one file attached to the record. This table has a many-to-one relationship with the TT_REQUIREMENT_EVENT table. Each row has a reported by record ID that matches a record ID in the TT_REQUIREMENT_EVENT table. (ATTACHMT) |
TT_REQUIREMENT | Contains requirement information. Each table row represents one requirement. (REQMNT) |
TT_REQUIREMENT_ATTACHMENT | Contains requirement file attachment information. Each table row represents one file attached to the record. This table has a many-to-one relationship with the TT_REQUIREMENT table. Each row has a reported by record ID that matches a record ID in the TT_REQUIREMENT table. (ATTACHMT) |
TT_REQUIREMENT_CHANGE | Contains the original values for fields changed after a requirement version was created. The requirement always stores the current value. (REQCHNGS) |
TT_REQUIREMENT_EVENT | Contains workflow event information for each event recorded in a requirement. Each table row represents a single requirement event. This table has a many-to-one relationship with the TT_REQUIREMENT, TT_EVENT, TT_USER, and TT_STATE tables. (REQEVTS) |
TT_REQUIREMENT_EVENT_ASGN_USER | Lists users currently assigned to a requirement. Can use to view requirements assigned to a user across all projects. This table is not available in Helix ALM. |
TT_REQUIREMENT_LOG | Contains historical log information about changes made to requirement records. Each row in this table represents a log entry in one of the requirement records. Each row has a requirement record that matches a record in the TT_REQUIREMENT table. (REQLOG) |
TT_REQUIREMENT_SELECT_FIELD | If the custom field is a pop-up menu, the selected values relate back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table |
TT_REQUIREMENT_SELECT_USER | If the custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table |
TT_REQUIREMENT_VERSION | Contains requirement version information. Each table row represents one requirement version. (REQVRSN) |
TT_SCM_CHANGELIST_DEFECT | Contains source control changelist information for defects |
TT_SCM_CHANGELIST_DOCUMENT | Contains source control changelist information for requirement documents |
TT_SCM_CHANGELIST_REQUIREMENT | Contains source control changelist information for requirements |
TT_SCM_CHANGELIST_TESTCASE | Contains source control changelist information for test cases |
TT_SCM_CHANGELIST_TESTRUN | Contains source control changelist information for test runs |
TT_SCM_FILE_DEFECT | Contains source control file information for defects. Each table row represents one file attached to an entity. This table has a many-to-one relationship with the corresponding entity table. Each row has an entity record ID. |
TT_SCM_FILE_DOCUMENT | Contains source control file information for requirement documents. Each table row represents one file attached to an entity. This table has a many-to-one relationship with the corresponding entity table. Each row has an entity record ID. |
TT_SCM_FILE_REQUIREMENT | Contains source control file information for requirements. Each table row represents one file attached to an entity. This table has a many-to-one relationship with the corresponding entity table. Each row has an entity record ID. |
TT_SCM_FILE_TESTCASE | Contains source control file information for test cases. Each table row represents one file attached to an entity. This table has a many-to-one relationship with the corresponding entity table. Each row has an entity record ID. |
TT_SCM_FILE_TESTRUN | Contains source control file information for test runs. Each table row represents one file that is attached to an entity. This table has a many-to-one relationship with the corresponding entity table. Each row has an entity record ID. |
TT_SNAPSHOT_REQUIREMENT_TREE | Contains the requirement relationship tree for a snapshot of the document (SNPSTTRE) |
TT_STATE | Contains information about states that an entity can transition to (STATES) |
TT_STEPDATA | Contains the step or expected result in the STEP_DATA field. The results field is only populated when the record is a step. |
TT_SUBTYPE | Contains requirement type information. Each table row represents one type value. (SUBTYPE) |
TT_SYSTEM_CONFIG | Contains test configuration information. Each table row represents one system test configuration. (SYSCONF) |
TT_SYSTEM_CONFIG_TYPE | Contains a break out of the system configuration types. In Helix ALM, the types are stored in memory, but this lookup table may be helpful to data warehouse users. |
TT_TCEVENT_RESULT_STATE | Lists the states for a test case workflow event. In the source system, the Event.RsltStates field is a space-delimited list of states for the event. The data warehouse breaks these states into a normalized list for easier reporting. |
TT_TCEVENT_SELECT_FIELD | If the test case custom field is a pop-up menu, the selected values relate back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table |
TT_TCEVENT_SELECT_USER | If the test case custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table |
TT_TESTCASE | Contains test case information. Each table row represents one test case. Additional information associated with a test case is in the TT_TESTCASE_EVENT table. This table has a one-to-one relationship with the TT_STATE and TT_FIELD_TESTOBJECT_TYPE tables. This table has a many-to-many relationship with the TT_USER table. (TESTCASE) |
TT_TESTCASE_ATTACHMENT | Contains test case file attachment information. Each table row represents one file attached to the record. This table has a many-to-one relationship with the TT_TESTCASE table. Each row has a reported by record ID that matches a record ID in the TT_TESTCASE table. (ATTACHMT) |
TT_TESTCASE_ATTACHMENT_INFO | Contains additional information about test case file attachments. Each table row represents one file attached to the record. This table has one-to-one relationship with TT_TESTCASE_ATTACHMENT table. (ATTACHINFO) |
TT_TESTCASE_EVENT | Contains workflow event information for each event recorded in a test case. Each table row represents a single test case event. This table has a many-to-one relationship with the TT_TESTCASE, TT_EVENT, TT_USER, and TT_STATE tables. (TCEVTS) |
TT_TESTCASE_EVENT_ASGN_USER | Lists users currently assigned to a test case. Can be used to see test cases assigned to a user across all projects. This table is not available in Helix ALM |
TT_TESTCASE_EVENT_ATCHMT | Contains test case workflow event file attachment information. Each table row represents one file attached to the record. This table has a many-to-one relationship with the TT_TESTCASE_EVENT table. Each row has a reported by record ID that matches a record ID in the TT_TESTCASE table. (ATTACHMT) |
TT_TESTCASE_LOG | Contains historical log information about changes made to test case records. Each row in this table represents a log entry in one of the test case records. Each table row has a test case record that matches a record in the TT_TESTCASE table. (TCLOG) |
TT_TESTCASE_SELECT_FIELD | If the custom field is a pop-up menu, the selected values are related back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table |
TT_TESTCASE_SELECT_USER | If the custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table |
TT_TESTRUN | Contains test run information. Each table row represents one test run. Additional information associated with a test run is found in the TT_TESTRUN_EVENT table. This table has a one-to-one relationship with the TT_STATE, TT_FIELD_TESTOBJECT_TYPE and TT_TESTRUN_SET tables. This table has a many-to-many relationship with the TT_USER table. (TESTRUN) |
TT_TESTRUN_ATTACHMENT | Contains test run file attachment information. Each table row represents one file attached to the record. This table has a many-to-one relationship with the TT_TESTRUN table. Each row has a reported by record ID that matches a record ID in the TT_TESTRUN table. (ATTACHMT) |
TT_TESTRUN_ATTACHMENT_INFO | Contains additional information about test run file attachments. Each table row represents one file attached to the record. This table has one-to-one relationship with TT_TESTRUN_ATTACHMENT table. (ATTACHINFO) |
TT_TESTRUN_EVENT | Contains workflow event information for each event recorded in a test run. Each table row represents a single test run event. This table has a many-to-one relationship with the TT_TESTRUN, TT_EVENT, TT_USER, and TT_STATE tables. (TREVTS) |
TT_TESTRUN_EVENT_ASGN_USER | Lists users currently assigned to a test run. Can be used to view test runs assigned to a user across all projects. This table is not available in Helix ALM. It is a relational table for the AsgndUsers multi-list field. |
TT_TESTRUN_EVENT_ATCHMT | Contains test run workflow event file attachment information. Each table row represents one file attached to the record. This table has a many-to-one relationship with the TT_TESTRUN_EVENT table. Each row has a reported by record ID that matches a record ID in the TT_TESTRUN table. (ATTACHMT) |
TT_TESTRUN_LOG | Contains historical log information about changes made to test run records. Each row in this table represents a log entry in one of the test run records. Each table row has a test run record ID that matches a record in the TT_TESTRUN table. (TRLOG) |
TT_TESTRUN_SELECT_FIELD | If the custom field is a pop-up menu, the selected values relate back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table |
TT_TESTRUN_SELECT_USER | If the custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table |
TT_TESTRUN_SET | Contains test run set pop-up menu values. Each row in this table represents one pop-up menu item. (FLDTRSET) |
TT_TILE | Contains information about widgets used on the Home page |
TT_TILE_COLOR_MAP | Contains color settings for Home page widgets |
TT_TREVENT_RESULT_STATE | Lists the states for a test run workflow event. In the source system, the Event.RsltStates field is a space-delimited list of states for the event. The data warehouse breaks these states into a normalized list for easier reporting. |
TT_TREVENT_SELECT_FIELD | Comment If the custom field is a pop-up menu, the selected values relate back to the pop-up menu list defined in the TT_CUSTOM_POPUP_FIELD table |
TT_TREVENT_SELECT_USER | If the custom field is a list of users or customers, the selected values relate back to the users defined in the TT_USER table |
TT_USER | Contains user and customer information. Each table row represents one user or one customer. (USERS) |
TT_USER_HIDDEN_TILE | Contains a row for each Home page widget hidden by a user |
TT_USER_SCM_FILE_DEFECT | Contains associations between a parent defect source control file record and one or more user records |
TT_USER_SCM_FILE_DOCUMENT | Contains associations between a parent requirement document source control file record and one or more user records |
TT_USER_SCM_FILE_REQUIREMENT | Contains associations between a parent requirement source control file record and one or more user records |
TT_USER_SCM_FILE_TESTCASE | Contains associations between a parent test case source control file record and one or more user records |
TT_USER_SCM_FILE_TESTRUN | Contains associations between a parent test run source control file record and one or more user records |