Helix ALM Data Warehouse 2017.2 - 2018.2 ERD
Table: LS_AUTHENTICATION_METHOD
| Comment | Contains authentication methods available for the LS_LDAP_SERVER table |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| AUTHENTICATION_METHOD | Yes | NUMERIC(10) | Yes | Authentication method index |
| AUTH_METHOD_DESCRIPTION | No | NVARCHAR(50) | No | Authentication method description |
Table: LS_EMAIL
| Comment | Contains email addresses for license server users (email) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| EMAIL_ID | Yes | NUMERIC(10) | Yes | Email address unique identifier (idrecord) |
| LS_USER_ID | No | NUMERIC(10) | Yes | Email address owner. Foreign key to the LS_USER table. (userid) |
| EMAIL_ADDRESS | No | NVARCHAR(63) | No | User email address (address) |
| EMAIL_TYPE_ID | No | NUMERIC(10) | No | Email address type. Foreign key to the LS_EMAIL_TYPE table. (typeid) |
Table: LS_EMAIL_TYPE
| Comment | Contains email types stored in the LS_EMAIL table |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| EMAIL_TYPE_ID | Yes | NUMERIC(10) | Yes | LS_EMAIL_TYPE table numeric key |
| EMAIL_TYPE_DESCRIPTION | No | NVARCHAR(50) | Yes | Email type description (e.g., Internet, MAPI, or Other) |
Table: LS_EVENT
| Comment | Lists license server events with a date/time component (Event) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| EVENT_ID | Yes | NUMERIC(10) | Yes | Event unique identifier (id) |
| EVENT_DATE | No | DATETIME | Yes | Date/time the event occurred (eventdate) |
| EVENT_TYPE_ID | No | NUMERIC(10) | Yes | Event type. Foreign key to the LS_EVENT_TYPE table. (eventtypeid) |
Table: LS_EVENT_DETAIL
| Comment | Contains license server event details referenced by license pool, number of licenses available, and number of licenses used (EventDetails) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| EVENT_ID | Yes | NUMERIC(10) | Yes | Event recorded. Foreign key to the LS_EVENT table. (eventid) |
| POOL_ID | Yes | NUMERIC(10) | Yes | Pool the licenses were retrieved from. Foreign key to the LS_POOL table. (poolid) |
| USED | No | NUMERIC(10) | No | Number of licenses used in the pool when the row was created (used) |
| AVAILABLE | No | NUMERIC(10) | No | Number of licenses available in the pool when the row was created (available) |
Table: LS_EVENT_TYPE
| Comment | Contains event types from the license server (EventType) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| EVENT_TYPE_ID | Yes | NUMERIC(10) | Yes | Event type unique identifier (id) |
| EVENT_TYPE_NAME | No | NVARCHAR(40) | No | Event type description (name) |
Table: LS_EVENT_USER
| Comment | Lists users affected by the license server event with product and license type (EventUser) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| EVENT_USER_ID | Yes | NUMERIC(10) | Yes | Event user unique identifier (id) |
| EVENT_ID | No | NUMERIC(10) | Yes | Event that occurred. Foreign key to the LS_EVENT table. (eventid) |
| LS_USER_ID | No | NUMERIC(10) | Yes | User affected by the event. Foreign key to the LS_USER table. (userid) |
| PRODUCT_ID | No | NUMERIC(10) | Yes | Product in use for the event. Foreign key to the LS_PRODUCT_NAME table. (productid) |
| LICENSE_TYPE_ID | No | NUMERIC(10) | Yes | License type in use for the event. Foreign key to the LS_LICENSE_TYPE table. (typeid) |
Table: LS_LDAP_FIELD
| Comment | Relates the LS_LDAP_SERVER table to a user field that stores the LDAP_FIELD information |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| LDAP_SERVER_ID | Yes | NUMERIC(10) | Yes | References the LS_LDAP_SERVER table |
| USER_FIELD_ID | Yes | NUMERIC(10) | Yes | References the LS_USER_FIELD table |
| LDAP_FIELD | No | NVARCHAR(max) | No | Field information related to the LS_LDAP_SERVER table indicated by the row relationship |
Table: LS_LDAP_SERVER
| Comment | Contains LDAP and Active Directory (AD) servers configured in the license server (lsldapserver) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| LDAP_SERVER_ID | Yes | NUMERIC(10) | Yes | LDAP/AD server unique identifier (idrecord) |
| UORDER | No | NUMERIC(10) | No | LDAP/AD server ordinal index in the license server Server Options dialog (uorder) |
| DISABLED | No | NUMERIC(1) | No | If 1, LDAP/AD server is disabled (disabled) |
| SERVER_NAME | No | NVARCHAR(192) | No | LDAP/AD server alias used in the license server (name) |
| SERVER_BASE | No | NVARCHAR(765) | No | Base domain name (DN) used to find user objects in the LDAP/AD server (base) |
| SERVER_HOST | No | NVARCHAR(384) | No | Hostname of the primary LDAP/AD server (host) |
| SERVER_PORT | No | NUMERIC(10) | No | Port the primary LDAP/AD server listens on (port) |
| BK_HOST | No | NVARCHAR(384) | No | Hostname of the backup LDAP/AD server (bkhost) |
| BK_PORT | No | NUMERIC(10) | No | Port the backup LDAP/AD server listens on (bkport) |
| ANONYMOUS_LOGIN | No | NUMERIC(1) | No | If 1, bind to LDAP/AD server anonymously (anonlogin) |
| USER_NAME | No | NVARCHAR(max) | No | Username for binding to the LDAP/AD server (username) |
| USER_DN | No | NVARCHAR(765) | No | User DN for binding to the LDAP/AD server (userdn) |
| PASSWORD | No | NVARCHAR(max) | No | Password for binding to the LDAP/AD server (password) |
| IS_AD | No | NUMERIC(1) | No | If 1, server is Active Directory (isad) |
| DOMAIN | No | NVARCHAR(765) | No | Active Directory domain the AD server belongs to (domain) |
| SSO | No | NUMERIC(10) | No | Single sign-on setting- 0: disabled, 1: enabled, 2: required (sso) |
| AUTHENTICATION_METHOD | No | NUMERIC(10) | No | Password encryption setting- 0: Simple (plain text), 1: MD5, 2: GSSAPI, 3: Simple +SSL, 4: MD5+SSL, 5: GSSAPI+SSL (authmeth) |
| SYNC_ACTIVE | No | NUMERIC(1) | No | If 1, synchronize user activation settings from AD (syncactive) |
Table: LS_LICENSE
| Comment | Lists licenses added to the license server (License) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| LICENSE_ID | Yes | NUMERIC(10) | Yes | License unique identifier (idRecord) |
| LICENSE_KEY | No | NVARCHAR(32) | No | License key (LKey) |
| DISABLED | No | NUMERIC(1) | No | Indicates if the license is disabled (Disabled) |
| MAINTENANCE_EXTENSION | No | NUMERIC(1) | No | Indicates if the license is a maintenance extension key (MainExt) |
Table: LS_LICENSE_TYPE
| Comment | Lists types of licenses available in the license server (LicenseType) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| LICENSE_TYPE_ID | Yes | NUMERIC(10) | Yes | License type unique identifier (id) |
| LICENSE_TYPE_NAME | No | NVARCHAR(40) | No | License type description (name) |
Table: LS_PHONE
| Comment | Lists user phone numbers (PhoneNum) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | No | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PHONE_ID | Yes | NUMERIC(10) | Yes | Phone number unique identifier (idRecord) |
| PHONE_TYPE_ID | No | NUMERIC(10) | No | Phone number type. Foreign key to the LS_PHONE_EMAIL_TYPE table. (TypeID) |
| LS_USER_ID | No | NUMERIC(10) | Yes | User the phone number belongs to. Foreign key to the LS_USER table. (UserID) |
| PHONE_NUMBER | No | NVARCHAR(63) | No | User phone number (Num) |
Table: LS_PHONE_TYPE
| Comment | Lists types of phone numbers stored in the LS_PHONE table. Phone number types are stored in the license server application only. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| PHONE_TYPE_ID | Yes | NUMERIC(10) | Yes | Phone number type unique identifier |
| PHONE_TYPE_DESCRIPTION | No | NVARCHAR(50) | Yes | Phone number type description (e.g., Invalid, Work, Fax, Home, Pager, Mobile) |
Table: LS_POOL
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| POOL_ID | Yes | NUMERIC(10) | Yes | Pool unique identifier (id) |
| POOL_NAME | No | NVARCHAR(40) | Yes | Pool name (name) |
| PRODUCT_ID | No | NUMERIC(10) | Yes | Product the pool represents. Foreign key to the PRODUCT_NAME table. (productid) |
| LICENSE_TYPE_ID | No | NUMERIC(10) | Yes | License type the pool represents. Foreign key to the LICENSE_TYPE table. (typeid) |
| DELETED | No | NUMERIC(1) | Yes | Indicates if the pool was deleted (deleted) |
| IS_SYSTEM | No | NUMERIC(1) | No | Flag that indicates if the record is a system pool |
Table: LS_PRODUCT_NAME
| Comment | Products supported by the license server (ProductName) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| PRODUCT_ID | Yes | NUMERIC(10) | Yes | Unique product identifier (id) |
| PRODUCT_NAME | No | NVARCHAR(40) | No | Unique product name (name) |
Table: LS_SSO_SETTING
| Comment | Describes the single sign-on setting for the license server |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SSO | Yes | NUMERIC(10) | Yes | LS_SSO_SETTING table index |
| SSO_SETTING_DESCRIPTION | No | NVARCHAR(50) | No | Single sign-on setting value description |
Table: LS_USER
| Comment | Users registered with the license server (lsuser) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| LS_USER_ID | Yes | NUMERIC(10) | Yes | User ID from the license server (idRecord) |
| LDAP_SERVER_ID | No | NUMERIC(10) | No | LDAP server the user is related to. Foreign key to the LS_LDAP_SERVER table. (ldapsrvid) |
| FIRST_NAME | No | NVARCHAR(32) | No | User first name (FirstName) |
| LAST_NAME | No | NVARCHAR(32) | No | User last name (LastName) |
| LOGIN_NAME | No | NVARCHAR(2000) | Yes | Login name field (LoginName) |
| NOTES | No | NVARCHAR(max) | No | Notes about the user (Notes) |
| LOGOUT_DATE | No | DATETIME | No | Date/time the user last logged out (dateLogout) |
| COMPANY | No | NVARCHAR(63) | No | User company name (Company) |
| DIVISION | No | NVARCHAR(63) | No | User division (Division) |
| DEPARTMENT | No | NVARCHAR(63) | No | User department (Department) |
| ADDRESS | No | NVARCHAR(255) | No | User address (Address) |
| IS_CUSTOMER | No | NUMERIC(1) | No | Indicates if the user is a customer (IsCustomer) |
| COMM_DENIED | No | NVARCHAR(255) | No | String of numbers that indicate the license server functionality the user can access- 1, 2, 3: no access; 1, 2: unable to log in, but can retrieve user records from applications; 2, 3: able to log in, but only able to add/edit/delete user information; (empty string): full administrative access (CommDenied) |
| IS_DISABLED | No | NUMERIC(1) | No | Indicates if the user is disabled (IsDisabled) |
| DATE_PWD_CHANGED | No | DATETIME | No | Last date/time the password was changed (dtPwdChg) |
| PWD_MUST_CHANGE | No | NUMERIC(1) | No | Indicates if the password needs to be changed (pwdMustChg) |
| IS_DELETED | No | NUMERIC(1) | No | Indicates if the user was deleted (IsDeleted) |
| MODIFIED_DATE | No | DATETIME | No | Date of the last modification to the user record (dateModify) |
| CAN_CHANGE_PWD | No | NUMERIC(1) | No | Indicates if the user can change the password (CanChngPwd) |
| ALLOWS_SSO | No | NUMERIC(1) | No | Indicates if single-sign on is allowed (AllowSSO) |
| INITIALS | No | NVARCHAR(8) | No | User initials (Initials) |
| ADDITIONAL_INFO | No | NVARCHAR(max) | No | Additional user information (AddlInfo) |
| CREATED_DATE | No | DATETIME | No | Date user was created. NULL for existing users. |
Table: LS_USER_FIELD
| Comment | Contains user field information |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| USER_FIELD_ID | Yes | NUMERIC(10) | Yes | Primary key for the row |
| USER_FIELD | No | NVARCHAR(15) | No | User field description |
Table: LS_USER_LICENSE
| Comment | Contains associations of users to licenses, often in a pool (UserLicense) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| USER_LICENSE_ID | Yes | NUMERIC(10) | Yes | User/license combination unique identifier (idRecord) |
| LS_USER_ID | No | NUMERIC(10) | Yes | User ID for the license (UserID) |
| USER_LICENSE_TYPE | No | NUMERIC(10) | No | License type (Type) |
| LICENSE_ID | No | NUMERIC(10) | No | Links the license to the user (namedSNID) |
| POOL_ID | No | NUMERIC(10) | No | Associates the license to a specific pool. A license can only belong to one pool. (poolid) |
Table: LS_USER_LICENSE_TYPE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| USER_LICENSE_TYPE | Yes | NUMERIC(10) | Yes | User license type unique identifier (in license server code only) |
| USER_LICTYPE_DESCRIPTION | No | NVARCHAR(180) | Yes | License type description (e.g., Invalid Serial Number, Windows Dedicated, TCM Named) |
Table: QAW_LOAD_TEST
| Comment | Represents a load test. Provides information about load test playback sessions. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| LOAD_TEST_ID | Yes | BIGINT | Yes | Load test unique identifier |
| PLAYBACK_SESSION_ID | No | BIGINT | Yes | Load test playback session unique identifier |
| TOTAL_VIRTUAL_USERS | No | INTEGER | Yes | Total number of virtual users for the load test |
| PEAK_CONCURRENT_VIRTUAL_USERS | No | INTEGER | Yes | Peak number of virtual users running concurrently during the load test |
| NUM_PAGE_HITS | No | INTEGER | Yes | Number of page hits during the load test |
| NUM_BYTES_SENT | No | BIGINT | Yes | Total number of bytes received during the load test |
| NUM_BYTES_RECEIVED | No | BIGINT | Yes | Total number of bytes received during the load test |
| MIN_RESPONSE_TIME_MS | No | BIGINT | Yes | Minimum time it took the server to respond in milliseconds |
| MAX_RESPONSE_TIME_MS | No | BIGINT | No | Maximum time it took the server to respond in milliseconds |
| AVG_RESPONSE_TIME_MS | No | BIGINT | Yes | Average time it took the server to respond in milliseconds |
| NUM_WARNINGS | No | BIGINT | Yes | Total number of warnings that occurred during the load test |
| NUM_ERRORS | No | BIGINT | Yes | Total number of errors that occurred during the load test |
Table: QAW_PLAYBACK_SESSION
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PLAYBACK_SESSION_ID | Yes | BIGINT | Yes | Playback session unique identifier |
| PLAYBACK_SESSION_TYPE | No | SMALLINT | Yes | Playback session type - 0: Run, 1: Batch, 2: LoadTest |
| START_TIME | No | DATETIME | Yes | Date and time the playback session started in millisecond precision. UTC format. |
| END_TIME | No | DATETIME | No | Date and time the playback session ended in millisecond precision. UTC format. |
| USER_NAME | No | NVARCHAR(256) | Yes | Username that initiated the playback session. May not be the username that ran the playback session. For example, the username "bob" may start a remote load test from his workstation, but the remote computer may be set up to run as "automationuser". In this case, the USER_NAME value is "bob". |
| CONTAINER_NAME | No | NVARCHAR(1024) | No | Playback session container (workspace or logical name with extension), if available |
| RUN_STATE | No | SMALLINT | Yes | Run state for the entire playback session - 0: Active, 1: Succeeded, 2: Failed, 3: Inactive (has not sent information to the server in over 30 minutes), 4: Canceled |
| CONTAINER_FILE_NAME | No | NVARCHAR(1024) | No | Playback session container (workspace or batch file name with extension), if available |
| HOST_NAME | No | NVARCHAR(256) | No | For standard tests, host name the playback session occurred on. For load tests, name of the initiating host, even if the test was distributed across multiple hosts. |
| IS_REMOTE | No | BIT | No | Indicates if the playback session was run remotely. Null indicates the value is not relevant. Load test value is always null. |
| LS_AUTHENTICATED | No | BIT | No | Indicates if the playback session user authenticated with the Helix ALM License Server |
| TT_PROJECT_UUID | No | NVARCHAR(38) | No | Unique identifier for the Helix ALM project the associated test run is is included in. Null indicates the playback session was not associated with a test run. |
| TT_TESTCASE_ID | No | NUMERIC(10) | No | Unique identifier for the Helix ALM test case the associated test run was generated from. Null indicates the playback session was not associated with a test run. |
| TT_TESTRUN_ID | No | NUMERIC(10) | No | Unique identifier for a Helix ALM test run. Null indicates the playback session was not associated with a test run. |
| PLAYBACK_SESSION_NAME | No | VARCHAR(1024) | No | Name set for the playback session |
| PROTOCOL_VERSION | No | SMALLINT | No | Database version the playback session was created in |
Table: QAW_SCRIPT
| Comment | A script that ran. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| SCRIPT_ID | Yes | NUMERIC(10) | Yes | Script unique identifier |
| SCRIPT_NAME | No | VARCHAR(1024) | No | Logical script name. Does not include file system details, such as filename, extension, or path. |
Table: QAW_SCRIPT_LINE_RUN
| Comment | An individual line of script that ran. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| SCRIPT_LINE_RUN_ID | Yes | BIGINT | Yes | Script line run unique identifier |
| SCRIPT_RUN_ID | No | BIGINT | No | Script run unique identifier. QA Wizard Pro 2016.0 and earlier only. |
| PARENT_SCRIPT_LINE_RUN_ID | No | BIGINT | No | Script line run parent unique identifier. For example, script lines running in a function call reference the script line of the call to that function. QA Wizard Pro 2016.0 and earlier only. |
| RUN_STATE | No | SMALLINT | Yes | Run state of the script line run - 0: Active, 1: Not active (succeeded), 2: Not active (failed) |
| START_TIME | No | DATETIME | Yes | Date and time the script line started running in millisecond precision |
| END_TIME | No | DATETIME | No | Date and time the script line stopped running in millisecond precision |
| SCRIPT_CONTEXT_SWITCH_NUMBER | No | INTEGER | Yes | Context switch number. When the playback session switches context by running a different script or calling a function, the number increases. Includes Script.CallScript. Starts at 1. The same script run can have script line runs in different context switches. QA Wizard Pro 2016.0 and earlier only. |
| LINE_NUMBER | No | INTEGER | Yes | Line number in the running script. Uses 1-based indexing. |
| LINE_TEXT | No | NVARCHAR(1024) | No | Text of the running script line |
| SEQUENCE_NUMBER | No | BIGINT | Yes | Number used to order events in a playback session. Sets to 1 when a playback session starts and increments when the next event starts. |
| STACK_FRAME_ID | No | BIGINT | No | Frame unique identifier. Groups related script lines in the same context. |
Table: QAW_SCRIPT_LINE_RUN_MESSAGE
| Comment | A message (error, warning, or output) that occurred on a script line during playback. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| SCRIPT_LINE_RUN_MESSAGE_ID | Yes | BIGINT | Yes | Message unique identifier |
| SCRIPT_LINE_RUN_ID | No | BIGINT | Yes | Script line run unique identifier |
| SCRIPT_LINE_RUN_MESSAGE_TYPE | No | SMALLINT | Yes | Message type that occurred when running a script line - 0: Warning, 1: Unhandled error, 2: Handled error, 3: Output |
| MESSAGE_TEXT | No | NVARCHAR(1024) | Yes | Message text (if any) |
| SEQUENCE_NUMBER | No | BIGINT | Yes | Number used to order events in a playback session. Sets to 1 when a playback session starts and increments when the next event starts. |
Table: QAW_SCRIPT_RUN
| Comment | An instance of a script that ran. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| SCRIPT_RUN_ID | Yes | BIGINT | Yes | Script run unique identifier |
| PLAYBACK_SESSION_ID | No | BIGINT | Yes | Playback session unique identifier |
| SCRIPT_NAME | No | NVARCHAR(1024) | No | Logical script name. Does not include filesystem details, such as filename, extension, or path. |
| START_TIME | No | DATETIME | Yes | Date and time the script run started in the playback session in millisecond precision. UTC format. |
| END_TIME | No | DATETIME | No | Date and time the script run ended in the playback session in millisecond precision. UTC format. |
| RUN_STATE | No | SMALLINT | Yes | Run state of the script run - 0: Active, 1: Not active (succeeded), 2: Not active (failed) |
| DATASHEET_ITERATION | No | INTEGER | Yes | If a script has an associated data-sheet, the current row/iteration number of the script run. Uses 1-based indexing. For example, a script that runs once has an associated datasheet with 4 rows. Four script run rows in this table, each with an associated datasheet iteration number (1, 2, 3, 4). |
| RUN_NUMBER | No | INTEGER | Yes | Indicates the nth time a script runs within a playback session, regardless of the reason. Uses 1-based indexing. |
| SEQUENCE_NUMBER | No | BIGINT | Yes | Number used to order events in a playback session. Starts with 1 when a playback session begins and increments with each event that begins. |
| SCRIPT_ID | No | BIGINT | Yes | Script unique identifier |
Table: QAW_STACK_FRAME
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| STACK_FRAME_ID | Yes | NUMERIC(10) | Yes | Frame unique identifier. Groups related script lines in the same context. |
| SCRIPT_RUN_ID | No | NUMERIC(10) | Yes | Script run unique identifier |
| DECLARING_SCRIPT_ID | No | NUMERIC(10) | No | Unique identifier of the script the context was declared in |
| CALLING_SCRIPT_LINE_RUN_ID | No | NUMERIC(10) | No | Script line run parent unique identifier. For example, in the context of a function call, this identifies the script line that calls the function. |
| STACK_FRAME_NAME | No | VARCHAR(1024) | No | Frame name that describes the context. In the context of a called script, function, or subroutine, the called item’s name is used. In the context of a Try, Catch, or Finally block, the block name is used. |
| SEQUENCE_NUMBER | No | NUMERIC(10) | No | Number used to order events in a playback session. Sets to 1 when a playback session starts and increments when the next event starts. |
Table: REP_AVAILABLE_TT_REPORT
| Comment | Contains a row for each report created in Helix ALM. Used to display Helix ALM reports in ALMRP dashboards. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| REPORT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| REPORT_NAME | No | VARCHAR(128) | No | Helix ALM report name |
| OWNER_USER_ID | No | NUMERIC(10) | No | Helix ALM user who created the report |
| ACCESS_STATE | No | NUMERIC(1) | No | Report access setting - 1: Shared, 2: Private |
Table: REP_SOURCE
| Comment | Lists the source systems that populate the data warehouse |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | Primary key to the REP_SOURCE table |
| SOURCE_NAME | No | NVARCHAR(50) | Yes | Unique source name |
| SOURCE_TYPE | No | NVARCHAR(20) | Yes | Source type (License Server, QA Wizard Pro, Surround, or Helix ALM) |
| SOURCE_DESCRIPTION | No | NVARCHAR(180) | No | Source description |
| OWNER_LCK_DBVERSION | No | NVARCHAR(114) | No | Description of the database version the source is associated with. References the OWNERLCK.OwnerValue table/column. |
| SERVER_ID | No | NUMERIC(10) | No | Unique reference to the server where the data originated. References the SERVERID.idServer table/column. |
| SERVER_UUID | No | NVARCHAR(114) | No | Unique reference to the server where the data originated. References the SERVERID.ServUUID table/column. |
| SERVER_NAME_PORT | No | NVARCHAR(180) | No | Server and port used by the data warehouse to construct ttstudio or sscm links from a report to the source application |
| ITEM_UUID | No | NVARCHAR(114) | No | Universally unique identifier of imported source item |
Table: REP_USER
| Comment | 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). |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| REP_USER_ID | Yes | NUMERIC(10) | Yes | Data warehouse user unique identifier |
| DISPLAY_NAME | No | NVARCHAR(180) | No | Name to display on reports |
| LS_SOURCE_ID | No | NUMERIC(10) | No | Source for the license server user identity. Does not need to match the source for other entities. |
| LS_USER_ID | No | NUMERIC(10) | No | Username from the license server |
| LOGIN_NAME | No | NVARCHAR(2000) | No | Login name field |
Table: REP_USER_QAW_USER
| Comment | Maps a data warehouse user to one or more QA Wizard Pro users in one or more sources. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| REP_USER_ID | Yes | NUMERIC(10) | Yes | Repository username |
| QAW_USER_NAME | Yes | NVARCHAR(256) | Yes | Username indirectly associated with a playback session |
Table: REP_USER_SCM_USER
| Comment | Maps a data warehouse user to one or more Surround SCM users in one or more sources |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| REP_USER_ID | Yes | NUMERIC(10) | Yes | Data warehouse user the Surround SCM user is mapped to. Foreign key to the REP_USER table. |
| SCM_USER_ID | Yes | NUMERIC(10) | Yes | Surround SCM user the data warehouse user is mapped to. Foreign key to the SCM_USER table. |
Table: REP_USER_TT_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| REP_USER_ID | Yes | NUMERIC(10) | Yes | Data warehouse user mapped to the Helix ALM user |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | Helix ALM project the user belongs to |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | Helix ALM user mapped to the data warehouse user |
Table: SCM_ARCHIVE_FILE
| Comment | Contains the master list of files in Surround SCM (ARCHIVEFILE) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Parent mainline branch ID (MainlineID) |
| FILE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (FileID) |
| ORIGINAL_REPOSITORY_ID | No | NUMERIC(10) | Yes | Foreign key to the SCM_REPOSITORY table. Original repository where the archive file was added (OrigRepoID) |
| ORIGINAL_FILE_NAME | No | NVARCHAR(255) | Yes | Original archive file name (OrigFileName) |
| FILE_TYPE | No | NUMERIC(2) | Yes | Archive file type unique identifier. Foreign key to the SCM_ARCHIVE_FILE_TYPE table. |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the archive file was destroyed. Destroyed archive files cannot be restored. (Destroyed) |
Table: SCM_ARCHIVE_FILE_TYPE
| Comment | Lookup table for the bitwise FILE_TYPE field in the ARCHIVE_FILE table |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| FILE_TYPE | Yes | NUMERIC(2) | Yes | Archive file type identifier |
| FILE_TYPE_DESCRIPTION | No | NVARCHAR(50) | No | Archive file type text description (e.g., ASCII, Binary, MacBinary, UTF8, UTF16, Symlink) |
Table: SCM_BRANCH
| Comment | Lists the branches for the mainline branches in the RDBMS database (BRANCH) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Surround SCM branch ID (MainlineID) |
| BRANCH_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (BranchID) |
| DELETED | No | NUMERIC(1) | No | Indicates if the branch was deleted. Deleted branches can be restored if they have not been destroyed. (Deleted) |
| BRANCH_NAME | No | NVARCHAR(255) | No | Branch name. Unique name for mainline, baseline, and snapshot branches. Workspace branches can have the same name only if the OwnerID value is different. (BranchName) |
| BRANCH_TYPE | No | NUMERIC(2) | No | Branch type numeric identifier- 0: Workspace, 1: Baseline, 2: Snapshot (BranchType) |
| OWNER_ID | No | NUMERIC(10) | No | Branch owner. Foreign key to the SCMUSERS table.Null for baseline and snapshot branches. (OwnerID) |
| PARENT_BRANCH_ID | No | NUMERIC(10) | No | Parent branch. Foreign key to the BRANCH table. A null value indicates the branch is the mainline. (ParentBranchID) |
| BASE_REPOSITORY_ID | No | NUMERIC(10) | No | Base repository for the branch record. Foreign key to the REPOSITORY table. (BaseRepositoryID) |
| CREATED_DATE | No | DATETIME | No | Date/time the branch was created (DateCreated) |
| MODIFIED_DATE | No | DATETIME | No | Date/time the branch was last modified (DateModified) |
| SECURITY_SETTINGS | No | NUMERIC(1) | No | Security type numeric identifier- 0: Branch security that applies to all branches, 1: Branch has its own security, 2: Branch inherits the parent branch security(SecuritySettings) |
| BASE_PATH | No | NVARCHAR(1024) | No | Base repository path for the branch (BasePath) |
| ACCESSED_DATE | No | DATETIME | No | Date/time the branch was last accessed (DateAccessed) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the branch was destroyed. Destroyed branches cannot be restored. (Destroyed) |
| COMMENTS | No | NVARCHAR(max) | No | Branch description (Comments) |
Table: SCM_BRANCH_CREATION
| Comment | Information about who created a branch and when |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Foreign key to the SCM_MAINLNE table |
| BRANCH_ID | Yes | NUMERIC(10) | Yes | Foreign key to the SCM _BRANCH table |
| CREATOR_ID | No | NUMERIC(10) | No | Foreign key to the SCM_USER table |
| CREATION_TYPE | No | NUMERIC(2) | No | Branch creation type |
| STATE_ID | No | NUMERIC(10) | No | Foreign key to the SCM_STATE table |
| LABEL_ID | No | NUMERIC(10) | No | Foreign key to the SCM_LABEL table |
| DATE_CREATED | No | DATETIME | No | Date/time the branch was created |
Table: SCM_BRANCH_FILE
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Parent mainline branch ID (MainlineID) |
| BRANCH_FILE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (BranchFileID) |
| BRANCH_REPOSITORY_ID | No | NUMERIC(10) | No | Foreign key to the BRANCHREPOSITORY table Repository that contains this file. (BranchRepoID) |
| FILE_ID | No | NUMERIC(10) | No | Foreign key to the ARCHIVEFILE table. Base file of this branched file (FileID) |
| DELETED | No | NUMERIC(1) | No | Indicates if the file was deleted (Deleted) |
| STATUS_FLAG | No | NUMERIC(10) | No | Bitwise flag that indicates the branch file status. Foreign key to the SCM_BRANCH_FILE_STATUS table. |
| FILE_NAME | No | NVARCHAR(255) | No | Branch file name (FileName) |
| CURRENT_VERSION | No | NUMERIC(10) | No | Current file version number (CurrentVersion) |
| EXPAND_KEYWORD_OPTION | No | CHARACTER(1) | No | How to handle keyword expansion for the file- 0: User server default, 1: Expansion off, 2: Expansion on (ExpandKeywordOption) |
| TIME_LAST_RENAMED | No | DATETIME | No | Date/time branch file was last renamed (TimeLastRenamed) |
| SHARE_BASE_BRANCH_FILE_ID | No | NUMERIC(10) | No | Record ID in the BRANCHFILE table. Base share file if the file is shared. Not an enforced foreign key relationship. (ShareBaseBranchFileID) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the branched file was destroyed. Destroyed files cannot be restored. (Destroyed) |
| INHERITED_FILE_REVISION_ID | No | NUMERIC(10) | No | Record ID of the inherited file revision for the branch file. |
| INHERITED_STATE_ID | No | NUMERIC(10) | No | Record ID of the inherited state for the branch file. |
| INHERITED_BRANCH_FILE_ID | No | NUMERIC(10) | No | Record ID of the inherited branch file for the branch file. |
| INHERITED_VERSION | No | NUMERIC(10) | No | Record ID of the inherited version for the branch file. |
Table: SCM_BRANCH_FILE_STATUS
| Comment | Decodes the bitwise STATUS_FLAG values in the SCM_BRANCH_FILE table |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| STATUS_FLAG | Yes | NUMERIC(10) | Yes | Unique key value to the SCM_BRANCH_STATUS_FLAG table |
| STATUS_DESCRIPTION | No | NVARCHAR(50) | Yes | Descriptive name for the branched file status value (e.g., Branched, Shared, Shared base, Analyzer filename conflict) |
Table: SCM_BRANCH_FILE_VERSION
| Comment | Contains file version data for Surround SCM branches (BranchFileVersion) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Parent mainline branch ID (MainlineID) |
| BRANCH_FILE_ID | Yes | NUMERIC(10) | Yes | Foreign key to the SCM_BRANCH_FILE table, Branch file the version applies to. (BranchFileID) |
| LOCAL_VERSION | Yes | NUMERIC(10) | Yes | File version (LocalVersion) |
| FILE_REVISION_ID | No | NUMERIC(10) | No | Foreign key to the SCM_FILE_REVISION table. Internal Surround SCM version tree of the file. (FileRevisionID) |
| VERSION_TIMESTAMP | No | DATETIME | No | Date/time the file version was added (VersionTimestamp) |
| VERSION_FLAG | No | NUMERIC(5) | No | Bitwise flag that indicates the file version. Foreign key to the SCM_BRANCH_FILE_VERSION_FLAG table. |
| STATE_ID | No | NUMERIC(10) | No | Foreign key to the SCM_STATE table. Workflow state of the file version. (StateID) |
| ALT_FILE_REVISION_ID | No | NUMERIC(10) | No | Alternate file revision ID. References the FILEREVISION table. Used to track versions promoted and rebased to other branches. (AltFilerevisionID) |
| INHERITED_BRANCH_ID | No | NUMERIC(10) | No | References a branch record in the BRANCH table if the VersionFlag field indicates that the version was inherited from another branch (InheritedBranchID) |
| PROMOTED_FROM_BRANCH_ID | No | NUMERIC(10) | No | References a branch record in the BRANCH table. Branch that the version was promoted from. (PromotedFromBranchID) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the file version was destroyed. Destroyed file versions cannot be restored. (Destroyed) |
Table: SCM_BRANCH_FILE_VERSION_FLAG
| Comment | Decodes the version flag on the SCM_BRANCH_FILE_VERSION table |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| VERSION_FLAG | Yes | NUMERIC(5) | Yes | Version flag unique record ID |
| VERSION_FLAG_DESCRIPTION | No | NVARCHAR(50) | No | Branch file version description (e.g., Inherited, Alternate version is promoted/no merge, etc.) |
Table: SCM_BRANCH_FLAG
| Comment | Lists allowed flags for a branch. A branch can have multiple flags simultaneously. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| BRANCH_FLAG | Yes | NUMERIC(5) | Yes | Branch flag unique identifier |
| BRANCH_FLAG_DESCRIPTION | No | NVARCHAR(50) | No | Branch flag description (e.g., Frozen, Destroyed, Inactive, Hidden, Cache on Demand, Case Sensitive Filenames) |
Table: SCM_BRANCH_FLAG_BRANCH
| Comment | Breaks out the BRANCH_FLAG attribute from the SCM_BRANCH table in a many-to-many relationship for branches with multiple flags |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch ID the branch and branch flag pair belong to |
| BRANCH_ID | Yes | NUMERIC(10) | Yes | Branch ID the branch flag applies to |
| BRANCH_FLAG | Yes | NUMERIC(5) | Yes | Branch flag that applies to the branch |
Table: SCM_BRANCH_REPOSITORY
| Comment | Contains repository data for Surround SCM branches (BranchRepository) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Parent mainline branch ID (MainlineID) |
| BRANCH_REPOSITORY_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (BranchRepoID) |
| REPOSITORY_ID | No | NUMERIC(10) | No | Foreign key to SCM_REPOSITORY table. Base repository. (RepositoryID) |
| DELETED | No | NUMERIC(1) | No | Indicates if the branched repository was deleted (Deleted) |
| REPOSITORY_NAME | No | NVARCHAR(max) | No | Repository name (RepositoryName) |
| BRANCH_ID | No | NUMERIC(10) | No | Foreign key to the BRANCH table. Branch where the repository is located. (BranchID) |
| TIME_LAST_RENAMED | No | DATETIME | No | Date/time the repository was last renamed (TimeLastRenamed) |
| WORKFLOW_SETTINGS | No | CHARACTER(1) | No | Repository workflow settings - 0: No workflow, 1: Inherit parent workflow, 2: Use specific workflow (WorkflowSettings) |
| USE_WORKFLOW_ID | No | NUMERIC(10) | No | Foreign key to the SCM_WORKFLOW table. Workflow used for the repository (UseWorkflowID) |
| PARENT_BRANCH_REPOSITORY_ID | No | NUMERIC(10) | No | Foreign key to the SCM_BRANCH_REPOSITORY table. Parent repository. (ParentBranchRepoID) |
| COMMENTS | No | NVARCHAR(max) | No | Repository description (Comments) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the repository was destroyed. Destroyed repositories cannot be restored. (Destroyed) |
| EXCLUDED | No | NUMERIC(1) | No | Indicates a repository that is excluded from the branch based on the template |
Table: SCM_BRANCH_REPO_PATH
| Comment | Lists the fully qualified path to the repository. Useful when constructing sscm links to the application in reports. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Parent mainline branch ID (MainlineID) |
| BRANCH_ID | Yes | NUMERIC(10) | Yes | References the SCM_BRANCH table |
| REPO_PATH_ID | Yes | NUMERIC(10) | Yes | Primary key to the SCM_BRANCH_REPO_PATH table. Unique for each REPO_PATH. |
| BRANCH_REPOSITORY_ID | No | NUMERIC(10) | Yes | Uniquely identifies a row. Foreign key to the SCM_BRANCH_REPOSITORY table. This table is not in the source, but is generated to correctly match to the Helix ALM data by repository path. |
| PARENT_BRANCH_REPOSITORY_ID | No | NUMERIC(10) | No | Reference to the SCM_BRANCH REPOSITORY table as the parent branch |
| REPO_PATH | No | NVARCHAR(max) | No | Full path to the repository |
Table: SCM_CHANGELIST
| Comment | Contains information for pending and committed changelists (Changelist) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch where the changelist resides (MainlineID) |
| CHANGELIST_ID | Yes | NUMERIC(10) | Yes | Primary key to the SCM_CHANGELIST table. Unique within a source or mainline branch. (ChangelistID) |
| CHANGELIST_NAME | No | NVARCHAR(255) | No | Changelist name (ChangelistName) |
| BRANCH_ID | No | NUMERIC(10) | No | Optional branch for the changelist (BranchID) |
| USER_ID | No | NUMERIC(10) | No | User who created the changelist (UserID) |
| COMPUTER_NAME | No | NVARCHAR(64) | No | Computer name the changelist was created on (ComputerName) |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if the changelist is pending (IsPending) |
| DATE_TIME | No | DATETIME | No | Date/time the changelist was created (DateTime) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the changelist was destroyed (Destroyed) |
Table: SCM_CHANGELIST_CUSTOM_FLDVAL
| Comment | Contains the custom field values associated with a changelist (ChangeListCustomFieldValue) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the changelist custom field applies to (MainlineID) |
| CHANGELIST_EVENT_ID | Yes | NUMERIC(10) | Yes | Changelist event for the custom field (ChangelistEventID) |
| CUSTOM_FIELD_ID | Yes | NUMERIC(10) | Yes | Custom field identifier (CustomFieldID) |
| CHANGELIST_ID | No | NUMERIC(10) | Yes | Changelist identifier. Foreign key to the SCM_CHANGELIST table. (ChangelistID) |
| TEXT_VALUE | No | NVARCHAR(255) | No | Text custom field value (TextValue) |
| INTEGER_VALUE | No | NUMERIC(10) | No | Integer custom field value (IntegerValue) |
| DOUBLE_VALUE | No | DOUBLE PRECISION | No | Double custom field value (DoubleValue) |
| DATE_TIME_VALUE | No | DATETIME | No | Date/time custom field value (DateTimeValue) |
| CHECKBOX_VALUE | No | NUMERIC(1) | No | Check box custom field value (checked or unchecked) (CheckBoxValue) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the row was destroyed (Destroyed) |
Table: SCM_CHANGELIST_EVENT
| Comment | Contains the events associated with a changelist (Changelistevent) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the changelist event applies to (MainlineID) |
| CHANGELIST_EVENT_ID | Yes | NUMERIC(10) | Yes | Primary key to the SCM_CHANGELIST_EVENT table. Unique number assigned to each row in a source. (ChangelistEventID) |
| CHANGELIST_ID | No | NUMERIC(10) | No | Changelist the event is associated with (ChangelistID) |
| EVENT_TYPE | No | NUMERIC(3) | No | Event type. Look up values in the SCM_EVENT_TYPE table. In the source system, this value is only listed in an enum. (EventType) |
| MACHINE_NAME | No | NVARCHAR(255) | No | Computer that triggered the changelist event (MachineName) |
| FILE_VERSION | No | NUMERIC(10) | No | File version the changelist event was performed on (FileVersion) |
| BRANCH_REPOSITORY_ID | No | NUMERIC(10) | No | Repository the event was performed on (BranchRepoID) |
| BRANCH_FILE_ID | No | NUMERIC(10) | No | File the event was performed on (BranchFileID) |
| ORIG_BRANCH_NAME | No | NVARCHAR(255) | No | Original branch name (OrigBranchName) |
| ORIG_REPOSITORY_NAME | No | NVARCHAR(1024) | No | Original repository name (OrigRepoName) |
| ORIG_FILE_NAME | No | NVARCHAR(255) | No | Original file name (OrigFileName) |
| KEEP_CHECKED_OUT_BITMASK | No | NUMERIC(1) | No | Indicates if the file should remain checked out (KeepCheckoutOrBitMask) |
| LOCAL_FILE_OR_NEW_NAME | No | NVARCHAR(1024) | No | Local file or new name description (LocalFileOrNewName) |
| EXCLUSIVE_LOCK | No | NUMERIC(1) | No | Indicates if the user has an exclusive lock on the file (ExclusiveLock) |
| DO_NOT_RETURN_COPY | No | NUMERIC(1) | No | Indicates a local copy was not returned (DoNotReturnCopy) |
| EOL_FORMAT | No | CHARACTER(1) | No | End of line format used (EOLFormat) |
| FILE_TYPE | No | NUMERIC(2) | No | File type indicator (FileType) |
| FILE_MODIFIED_TIME | No | DATETIME | No | Last date/time the file was modified (FileModifiedTime) |
| UNDELETE_CHECKIN_IF_DELETED | No | NUMERIC(1) | No | Indicates if the file was undeleted and checked in (UndeleteAndCheckinIfDeleted) |
| MAKE_FILE_WRITABLE | No | NUMERIC(1) | No | Indicates if the file is writable (MakeFileWriteable) |
| LABEL_ID | No | NUMERIC(10) | No | Changelist event label ID (LabelID) |
| ALLOW_LABEL_OVERRIDE | No | NUMERIC(1) | No | Indicates if the label can be overridden (AllowLabelOverride) |
| FILE_STATE_ID | No | NUMERIC(10) | No | File workflow state. Foreign key to the SCM_STATE table. (FileStateID) |
| FORCE_CHECKIN_WITHOUT_MERGE | No | NUMERIC(1) | No | Indicates if check in should be forced if no merge is necessary (ForceCheckinWOMerge) |
| UPDATE_IF_NO_CHANGE | No | NUMERIC(1) | No | Indicates if the check in information should be updated if there is no change (UpdateIfNoChange) |
| REMOVE_LOCAL_FILE | No | NUMERIC(1) | No | Indicates if the local file should be removed (RemoveLocalFile) |
| MERGED_VERSION | No | NUMERIC(10) | No | Merged version number (MergedVersion) |
| MODIFIED_VERSION | No | NUMERIC(10) | No | Modified version number (ModifiedVersion) |
| COMMENTS | No | NVARCHAR(max) | No | Changelist event comments (Comments) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the changelist event was destroyed (Destroyed) |
| ROLLBACK_EVENT_ID | No | NUMERIC(10) | No | Foreign key to the SCM_EVENT table. Event ID for rollbacks. |
Table: SCM_CHECKOUT_FILE
| Comment | Contains all file check out information (CheckoutFile) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the file is checked out from (MainlineID) |
| BRANCH_FILE_ID | Yes | NUMERIC(10) | Yes | File ID. Foreign key to the SCM_BRANCH_FILE table (BranchFileID) |
| USER_ID | Yes | NUMERIC(10) | Yes | User who checked out the file (UserID) |
| FILE_VERSION | No | NUMERIC(10) | No | File version checked out (FileVersion) |
| CHECKOUT_TIME | No | DATETIME | No | Date/time the file was checked out (CheckoutTime) |
| CHECKOUT_COMPUTER | No | NVARCHAR(64) | No | Computer the file was checked out to (CheckoutComputer) |
| DESTINATION_INFO | No | NVARCHAR(255) | No | Destination information for the file (DestinationInfo) |
| COMMENTS | No | VARCHAR(max) | No | Checked out file comments (Comments) |
| CHECKOUT_FLAG | No | CHARACTER(40) | No | Indicates if the file is checked out (1) or checked in (0) (CheckoutFlag) |
| REBASE_PROMOTE_BRANCH_ID | No | NUMERIC(10) | No | Branch ID for rebasing the file (RebasePromoteBranchID) |
| REBASE_PROMOTE_BRANCH_VER | No | NUMERIC(10) | No | Branch version for rebasing the file (RebasePromoteBranchVer) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the checked out file was destroyed (Destroyed) |
Table: SCM_COMMAND
| Comment | Lists security commands used to assign Surround SCM permissions |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| COMMAND_ID | Yes | NUMERIC(10) | Yes | Command number from the enum list in Surround SCM |
| COMMAND_DESCRIPTION | No | NVARCHAR(180) | Yes | Command description (e.g., Edit Server Options, Create Mainline Branch, etc.) |
Table: SCM_CUSTOM_FIELD
| Comment | Contains custom field rules used in filters, reports, and triggers (ScmCustomFlds) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| CUSTOM_FIELD_ID | Yes | NUMERIC(10) | Yes | Custom field unique identifier (idCustomField) |
| DELETED | No | NUMERIC(1) | No | Indicates if the custom field was deleted (Deleted) |
| CUSTOM_FIELD_NAME | No | NVARCHAR(128) | Yes | Custom field name (Name) |
| CUSTOM_FIELD_TYPE | No | NUMERIC(5) | No | Custom field type (type) |
| DISPLAY_ORDER | No | NUMERIC(10) | No | Order to display the custom field (DisplayOrder) |
| FIELD_CODE | No | NVARCHAR(128) | No | Field type (e.g., OWNER, ASSIGNED, etc.) (FieldCode) |
| DFLT_NOT_SET | No | NUMERIC(1) | No | Indicates if there is a default field value. Defaults have an exclusive-or relationship. Only one default value is relevant based on the field type. (DfltNotSet) |
| LIMITS | No | NVARCHAR(max) | No | Coded value that indicates the custom field limit (Limits) |
| DFLT_INT_VALUE | No | NUMERIC(10) | No | Default integer field value (DfltIntValue) |
| DFLT_TEXT_VALUE | No | NVARCHAR(max) | No | Default text field value (DfltTextValue) |
| DFLT_DATE_VALUE | No | DATETIME | No | Default date field value (DfltDateValue) |
| DFLT_BOOL_VALUE | No | NUMERIC(1) | No | Default field value - 1:True, 0: False (DfltBoolValue) |
| DFLT_DOUBLE_VALUE | No | DOUBLE PRECISION | No | Default double field value (DfltDoubleValue) |
Table: SCM_EVENT
| Comment | Contains a list of events performed in Surround SCM (event) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Parent mainline branch ID (MainlineID) |
| EVENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (EventID) |
| BRANCH_ID | No | NUMERIC(10) | No | Foreign key to the BRANCH table. Branch the event was performed on. (BranchID) |
| BRANCH_REPOSITORY_ID | No | NUMERIC(10) | No | Foreign key to the SCM_BRANCH_REPOSITORY table that references the repository the event was performed on (BranchRepoID) |
| BRANCH_FILE_ID | No | NUMERIC(10) | No | Foreign key to the SCM_BRANCH_FILE table. File the event was performed on. (BranchFileID) |
| FILE_VERSION | No | NUMERIC(10) | No | File version the event was performed on (FileVersion) |
| EVENT_TYPE | No | NUMERIC(5) | No | Foreign key to the SCM_EVENT_TYPE table (EventType) |
| EVENT_DATE | No | DATETIME | No | Event timestamp (EventDate) |
| SCM_USER_ID | No | NUMERIC(10) | No | Foreign key to the SCM_USER table. User who performed the event. (UserID) |
| USER_NAME | No | NVARCHAR(255) | No | Username that performed the event (UserName) |
| CHANGELIST_ID | No | NUMERIC(10) | No | Foreign key that references the SCM_CHANGELIST table if the event was part of a changelist. (ChangelistID) |
| ALT_NAME1 | No | NVARCHAR(max) | No | Text field that contains additional event data based on the event type (AltName1) |
| ALT_NAME2 | No | NVARCHAR(max) | No | Text field that contains additional event data based on the event type (AltName2) |
| ALT_INTEGER1 | No | NUMERIC(10) | No | Numeric field that contains additional event data based on the event type (AltInteger1) |
| ALT_INTEGER2 | No | NUMERIC(10) | No | Numeric field that contains additional event data based on the event type (AltInteger2) |
| ALT_INTEGER3 | No | NUMERIC(10) | No | Numeric field that contains additional event data based on the event type (AltInteger3) |
| COMMENTS | No | NVARCHAR(max) | No | Event comments (Comments) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the event was destroyed. Destroyed events cannot be restored. (Destroyed) |
| ROLLBACK_TYPE | No | NUMERIC(5) | No | Indicates the action rolled back. Used when EVENT_TYPE value indicates a rollback. |
Table: SCM_EVENT_CUSTOM_FIELD_VALUE
| Comment | Contains historical information about file custom field value changes (eventcustomfieldvalue) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the event custom field belongs to (MainlineID) |
| EVENT_ID | Yes | NUMERIC(10) | Yes | Event ID the custom field applies to (EventID) |
| CUSTOM_FIELD_ID | Yes | NUMERIC(10) | Yes | Custom field applied to the event (CustomFieldID) |
| IS_PREVIOUS_VALUE | Yes | NUMERIC(1) | Yes | Indicates if the field value was previously used (IsPreviousValue) |
| TEXT_VALUE | No | NVARCHAR(255) | No | Text custom field value (TextValue) |
| INTEGER_VALUE | No | NUMERIC(10) | No | Integer custom field value (IntegerValue) |
| DOUBLE_VALUE | No | DOUBLE PRECISION | No | Double custom field value (DoubleValue) |
| DATE_TIME_VALUE | No | DATETIME | No | Date/time custom field value (DateTimeValue) |
| CHECKBOX_VALUE | No | NUMERIC(1) | No | Check box custom field value (checked or unchecked) (CheckBoxValue) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the custom field for the event was destroyed (Destroyed) |
Table: SCM_EVENT_DEFECT_ATTACH
| Comment | Relates a Helix ALM defect to a Surround SCM file and the event that describes the attachment |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the file belongs to |
| BRANCH_FILE_ID | Yes | NUMERIC(10) | Yes | References the SCM_BRANCH_FILE table. File attached to the defect. |
| EVENT_ID | Yes | NUMERIC(10) | Yes | Event that describes the attachment |
| BRANCH_ID | No | NUMERIC(10) | No | Branch the file is in |
| BRANCH_REPOSITORY_ID | No | NUMERIC(10) | No | Repository the file is in |
| DEFECT_ID | No | NUMERIC(10) | No | References the TT_DEFECT table for a direct link to the defect ID. An explicit foreign key is not available. |
| DEFECT_NUMBER | No | NUMERIC(10) | No | References the TT_DEFECT table for a direct link to the defect number. An explicit foreign key is not available. |
| TT_PROJECT_NAME | No | NVARCHAR(4000) | No | Helix ALM project the defect references in the Surround SCM event |
Table: SCM_EVENT_REQUIREMENT_ATTACH
| Comment | Relates a Helix ALM defect to a Surround SCM file and the event that describes the attachment |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the file belongs to (MainlineID) |
| BRANCH_FILE_ID | Yes | NUMERIC(10) | Yes | References the SCM_BRANCH_FILE table. File attached to the requirement |
| EVENT_ID | Yes | NUMERIC(10) | Yes | Event that describes the attachment |
| BRANCH_ID | No | NUMERIC(10) | No | Branch the file is in |
| BRANCH_REPOSITORY_ID | No | NUMERIC(10) | No | Repository the file is in |
| REQUIREMENT_ID | No | NUMERIC(10) | No | References the TT_REQUIREMENT table for a direct link to the requirement ID. An explicit foreign key is not available. |
| REQUIREMENT_NUMBER | No | NUMERIC(10) | No | References the TT_REQUIREMENT table for a direct link to the requirement number. An explicit foreign key is not available. |
| TT_PROJECT_NAME | No | NVARCHAR(4000) | No | Helix ALM project the requirement references in the Surround SCM event |
Table: SCM_EVENT_TESTCASE_ATTACH
| Comment | Relates a Helix ALM test case to a Surround SCM file and the event that describes the attachment |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the file belongs to |
| BRANCH_FILE_ID | Yes | NUMERIC(10) | Yes | References the SCM_BRANCH_FILE table. File attached to the test case. |
| EVENT_ID | Yes | NUMERIC(10) | Yes | Event that describes the attachment |
| BRANCH_ID | No | NUMERIC(10) | No | Branch the file is in |
| BRANCH_REPOSITORY_ID | No | NUMERIC(10) | No | Repository the file is in |
| TESTCASE_ID | No | NUMERIC(10) | No | References the TT_TESTCASE table for a direct link to the test case ID. An explicit foreign key is not available. |
| TESTCASE_NUMBER | No | NUMERIC(10) | No | References the TT_TESTCASE table for a direct link to the test case number. An explicit foreign key is not available. |
| TT_PROJECT_NAME | No | NVARCHAR(4000) | No | Helix ALM project the test case references in the Surround SCM event |
Table: SCM_EVENT_TYPE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| EVENT_TYPE | Yes | NUMERIC(5) | Yes | Event type |
| EVENT_DESCRIPTION | No | NVARCHAR(50) | Yes | Description of the event type related to the EVENT_TYPE numeric value (e.g., Added to repository, Promoted to branch, etc.) |
Table: SCM_FILE_CUSTOM_FIELD_VALUE
| Comment | Contains all file custom field values (filecustomfieldvalue) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the custom field value applies to (MainlineID) |
| BRANCH_FILE_ID | Yes | NUMERIC(10) | Yes | File the custom field value applies to (BranchFileID) |
| CUSTOM_FIELD_ID | Yes | NUMERIC(10) | Yes | Custom field the value applies to (CustomFieldID) |
| TEXT_VALUE | No | NVARCHAR(255) | No | Text custom field value (TextValue) |
| INTEGER_VALUE | No | NUMERIC(10) | No | Integer custom field value (IntegerValue) |
| DOUBLE_VALUE | No | DOUBLE PRECISION | No | Double custom field value (DoubleValue) |
| DATE_TIME_VALUE | No | DATETIME | No | Date/time custom field value (DateTimeValue) |
| CHECKBOX_VALUE | No | NUMERIC(1) | No | Check box custom field value (checked or unchecked) (CheckBoxValue) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the custom field was destroyed (Destroyed) |
Table: SCM_FILE_REVISION
| Comment | Contains the master list of file revisions in Surround SCM (filerevision) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Parent mainline branch ID (MainlineID) |
| FILE_REVISION_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (FileRevisionID) |
| FILE_ID | No | NUMERIC(10) | Yes | References the ARCHIVE_FILE table (FileID) |
| REVISION | No | NVARCHAR(256) | No | Revision number string. Used internally by Surround SCM to build a revision tree of file changes. (Revision) |
| PARENT_REVISION_ID | No | NUMERIC(10) | No | Foreign key that references the FILEREVISION table. Parent revision (ParentRevisionID) |
| ARCHIVE_DATE | No | DATETIME | No | Date/time the file revision was created (ArchiveDate) |
| MODIFY_DATE | No | DATETIME | No | Date/time the archive file was modified (ModifyDate) |
| FILE_SIZE | No | BIGINT | No | File size (FileSize) |
| FILE_CRC | No | NUMERIC(10) | No | File CRC. Used for binary, MacBinary, and UTF16 files. (FileCRC) |
| DELTA_COUNT | No | NUMERIC(10) | No | Number of delta chunks (DeltaCount) |
| DELTA_CHUNKSIZE | No | NUMERIC(10) | No | Delta chunk size (DeltaChunkSize) |
| DELTA_SIZE | No | BIGINT | No | Delta size (DeltaSize) |
| DELTA_CRC | No | NUMERIC(10) | No | CRC of delta (DeltaCRC) |
| DELTA_EOL_TYPE | No | NUMERIC(1) | No | End of line type for delta (DeltaEOLType) |
| TEXT_CRC | No | NUMERIC(10) | No | File text CRC. Used for ASCII, UTF8, and symlink files. (textCRC) |
| NEXT_BRANCH_NUMBER | No | NUMERIC(10) | No | Next number to add to the FILEREVISION.REVISION value if the file is branched (NextBranchNum) |
| USER_NAME | No | NVARCHAR(255) | No | User who created the revision. Used for keyword expansion. (Username) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the file revision was destroyed. Destroyed file revisions cannot be restored. (Destroyed) |
Table: SCM_GROUP
| Comment | Contains information about Surround SCM security groups (SCMGroups) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| GROUP_ID | Yes | NUMERIC(10) | Yes | Primary key to the SCM_GROUP table (idGroup) |
| GROUP_NAME | No | NVARCHAR(128) | No | Security group name (Name) |
| GROUP_DESCRIPTION | No | NVARCHAR(1020) | No | Security group description (Description) |
| GROUP_NOTES | No | NVARCHAR(max) | No | Additional security group information (Notes) |
| SECURITY_VERSION | No | NUMERIC(5) | No | Security version (SecurityVersion) |
Table: SCM_GROUP_COMMAND
| Comment | Lists commands for a Surround SCM security group. The commands are a list in the Surround SCM code. (scmgroupcmds) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| GROUP_ID | Yes | NUMERIC(10) | Yes | Group identifier related to the SCM_GROUP table (idGroup) |
| COMMAND_ID | Yes | NUMERIC(10) | Yes | Command identifier related to the SCM_COMMAND lookup table (idCommand) |
Table: SCM_LABEL
| Comment | Contains all Surround SCM labels (Label) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the label applies to (MainlineID) |
| LABEL_ID | Yes | NUMERIC(10) | Yes | Primary key to the SCM_LABEL table. Unique within a source/mainline branch. (LabelID) |
| BRANCH_ID | No | NUMERIC(10) | No | Branch the label applies to (BranchID) |
| IS_HIDDEN | No | NUMERIC(1) | No | Indicates if the label is hidden (IsHidden) |
| LABEL_NAME | No | NVARCHAR(255) | No | Label name (LabelName) |
| LABEL_DESCRIPTION | No | NVARCHAR(1024) | No | Label description (LabelDescription) |
| OWNER_ID | No | NUMERIC(10) | No | User who owns the label (OwnerID) |
| TIME_CREATED | No | DATETIME | No | Date/time the label was created (TimeCreated) |
| FILE_COUNT | No | NUMERIC(10) | No | Number of files the label is applied to (FileCount) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the label was destroyed (Destroyed) |
Table: SCM_LABEL_EVENT
| Comment | Contains all events related to Surround SCM labels (Labelevent) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the label event applies to (MainlineID) |
| LABEL_EVENT_ID | Yes | NUMERIC(10) | Yes | Table row unique identifier (LabelEventID) |
| LABEL_ID | No | NUMERIC(10) | No | Label ID the event applies to (LabelID) |
| EVENT_TYPE | No | NUMERIC(5) | No | Foreign key to the LABEL_EVENT_TYPE table - 0: Create label, 1: Add label, 2: Remove label from a file, 3: Rename label, 4: Hide label, 5: Unhide label, 6: Update labeled file version (EventType) |
| SCM_USER_ID | No | NUMERIC(10) | No | User ID that performed the event (UserID) |
| EVENT_TIME | No | DATETIME | No | Date/time the event occurred (EventTime) |
| FILE_COUNT | No | NUMERIC(10) | No | Number of files labeled (FileCount) |
| COMMENTS | No | NVARCHAR(max) | No | Comments entered by the user when the event occurred (Comments) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the label was destroyed (Destroyed) |
Table: SCM_LABEL_EVENT_TYPE
| Comment | List of Surround SCM label event types |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| EVENT_TYPE | Yes | NUMERIC(5) | Yes | Label event type unique identifier |
| EVENT_TYPE_DESCRIPTION | No | NVARCHAR(50) | No | Label event type description (e.g., Create label, Label hidden, etc.) |
Table: SCM_LABEL_FILE
| Comment | Contains label association and file information (Labelfile) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Mainline branch the file label is associated with (MainlineID) |
| LABEL_ID | Yes | NUMERIC(10) | Yes | File label (LabelID) |
| BRANCH_FILE_ID | Yes | NUMERIC(10) | Yes | File the label is applied to (BranchFileID) |
| FILE_VERSION | No | NUMERIC(10) | No | File version associated with the label and file (FileVersion) |
| LABEL_EVENT_ID | No | NUMERIC(10) | No | Label event (LabelEventID) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the label was destroyed (Destroyed) |
Table: SCM_MAINLINE
| Comment | Contains the list of Surround SCM mainline branches that reside in the RDBMS database (Mainline) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Parent mainline branch ID. All other mainline-related tables link to this ID. (MainlineID) |
| MAINLINE_NAME | No | NVARCHAR(128) | No | Unique mainline name (MainlineName) |
| MAINLINE_UUID | No | NVARCHAR(114) | No | Universally unique mainline identifier (MainlineUUID) |
| DISASSOCIATED | No | NUMERIC(1) | No | Indicates if the mainline was removed, but not destroyed, from the Surround SCM Server (Disassociated) |
| MAINLINE_VERSION | No | NVARCHAR(30) | No | Mainline schema version number (MainlineVers) |
| LOAD_BRANCH | No | NVARCHAR(1024) | No | Comma-separated list of branch IDs (from the SCM_BRANCH table) that load into the server cache when the mainline is loaded (LoadBranch) |
| NAME_CASE_SENSITIVE | No | NUMERIC(1) | No | Indicates if the mainline allows case-sensitive file and repository names. Default is false. (NameCaseSensitive) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the mainline was destroyed. Destroyed mainlines cannot be used or restored. (Destroyed) |
| ACTIVE | No | NUMERIC(1) | No | Indicates if the mainline is active. Originates from the source system REPODBS.ACTIVE field. REPODBS is for reporting purposes and is only required to indicate if the mainline is active. (repodbs.active) |
Table: SCM_MERGE_EVENT
| Comment | Stores the file versions that were merged into the same file on a different branch |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | References the SCM_MAINLINE table. Mainline branch the data originated from. |
| MERGE_EVENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| BRANCH_FILE_ID_FROM | No | NUMERIC(10) | Yes | File ID the changes originated from |
| LOCAL_VERSION_START | No | NUMERIC(10) | Yes | Starting revision of the merge to file indicated by BRANCH_FILE_ID_FROM |
| LOCAL_VERSION_END | No | NUMERIC(10) | Yes | Ending revision of merge to file indicated by BRANCH_FILE_ID_FROM |
| BRANCH_FILE_ID_TO | No | NUMERIC(10) | Yes | File ID the changes are merged into |
| LOCAL_VERSION | No | NUMERIC(10) | Yes | File version where changes were merged indicated by BRANCH_FILE_ID_TO |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the merge was destroyed |
Table: SCM_REPOSITORY
| Comment | Contains the master list of Surround SCM repositories (Repository) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| MAINLINE_ID | Yes | NUMERIC(10) | Yes | Parent mainline branch ID (MainlineID) |
| REPOSITORY_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (RepositoryID) |
| PARENT_REPOSITORY_ID | No | NUMERIC(10) | No | Foreign key to the SCM_REPOSITORY table. Parent repository. (ParentRepoID) |
| DESTROYED | No | NUMERIC(1) | No | Indicates if the repository was destroyed. Destroyed repositories cannot be restored. (Destroyed) |
Table: SCM_STATE
| Comment | Contains information about Surround SCM workflow states (scmstates) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| STATE_ID | Yes | NUMERIC(10) | Yes | Primary key to the SCM_STATE table (idState) |
| DELETED | No | NUMERIC(1) | No | Indicates if the state was deleted (Deleted) |
| STATE_NAME | No | NVARCHAR(128) | Yes | State name (Name) |
| STATE_DESCRIPTION | No | NVARCHAR(1020) | No | State description (Description) |
Table: SCM_TTP_DB_CONFIGURATION
| Comment | Contains information about Helix ALM connections configured in Surround SCM (Helix ALMDBCONF) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TTP_DB_CONFIG_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idHelix ALMDbConf) |
| CONFIG_NAME | No | NVARCHAR(128) | No | Helix ALM connection name (e.g., Helix ALM Bugs) (ConfigName) |
| DISPLAY_ORDER | No | NUMERIC(5) | No | Indicates the display order for the record in the Helix ALM configuration list in the Surround SCM Client (DisplayOrder) |
| TT_PROJ_UUID | No | NVARCHAR(38) | No | Helix ALM project unique identifier |
| TT_SERVER_IP | No | NVARCHAR(512) | No | Helix ALM Server host and IP address (TTServerIP) |
| TT_SERVER_PORT | No | NUMERIC(5) | No | Helix ALM Server port (TTServerPort) |
| TT_DB_NAME | No | NVARCHAR(128) | No | Helix ALM project name (TTDbName) |
| TT_DB_ID | No | NUMERIC(10) | No | Helix ALM project ID (TTDbID) |
Table: SCM_USER
| Comment | Contains information about Surround SCM users (scmusers) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| SCM_USER_ID | Yes | NUMERIC(10) | Yes | Primary key to the SCM_USER table (idUser) |
| SCM_USER_NAME | No | NVARCHAR(255) | No | Username (Username) |
Table: SCM_USER_GROUP
| Comment | Contains users in Surround SCM security groups (scmusergrp) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| GROUP_ID | Yes | NUMERIC(10) | Yes | Security group the user belongs to. A user can belong to multiple groups. (idGroup) |
| SCM_USER_ID | Yes | NUMERIC(10) | Yes | Users in the security group (idUser) |
Table: SCM_WORKFLOW
| Comment | Contains information about Surround SCM workflows (scmworkflows) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| WORKFLOW_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idWorkFlow) |
| WORKFLOW_NAME | No | NVARCHAR(128) | Yes | Workflow name (Name) |
| WORKFLOW_DESCRIPTION | No | NVARCHAR(1020) | No | Workflow description (Description) |
| STATE_ID | No | NUMERIC(10) | No | Default workflow state ID for the workflow (idDefaultState) |
| ROLLBACK_OPTION | No | NUMERIC(1) | No | Indicates if the state is rolled back when the file version is rolled back (RollbackOption) |
Table: SCM_WORKFLOW_STATE
| Comment | Contains states associated with Surround SCM workflows (scmwrkflwstates) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| WORKFLOW_ID | Yes | NUMERIC(10) | Yes | Workflow ID the state is associated with (idWorkFlow) |
| STATE_ID | Yes | NUMERIC(10) | Yes | State definition ID that describes the state (idState) |
| DISPLAY_ORDER | No | NUMERIC(5) | No | Numeric value that indicates the display order for the state list in the Surround SCM Client (DisplayOrder) |
Table: TT_ASSIGNED_DEFECT_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users the defect is assigned to |
| DEFECT_ID | Yes | NUMERIC(10) | Yes | References the TT_DEFECT table. Defects assigned to the user. |
Table: TT_ASSIGNED_DOCUMENT_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users the document is assigned to |
| DOCUMENT_ID | Yes | NUMERIC(10) | Yes | Indicates the requirement document assigned to the user. Foreign key to the TT_DOCUMENT table. |
Table: TT_ASSIGNED_REQUIREMENT_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users the requirement is assigned to |
| REQUIREMENT_ID | Yes | NUMERIC(10) | Yes | Requirement assigned to the user. Foreign key to the TT_REQUIREMENT table. |
Table: TT_ASSIGNED_TESTCASE_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users the test case is assigned to |
| TESTCASE_ID | Yes | NUMERIC(10) | Yes | Foreign key to the TT_TESTCASE table. Test case assigned to the user. |
Table: TT_ASSIGNED_TESTRUN_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users the test run is assigned to |
| TESTRUN_ID | Yes | NUMERIC(10) | Yes | Foreign key to the TT_TESTRUN table. Test run assigned to the user. |
Table: TT_AUDITLOG
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | Helix ALM project ID, identifies row’s parent project |
| AUDITLOG_ID | Yes | NCHAR(10) | Yes | Record ID that uniquely identifies a table row. |
| AUDIT_DATETIME | No | DATETIME | Yes | Date and time change was made; changed item identified by ENTITYTYPE and ENTITYID |
| LOGIN_NAME | No | NVARCHAR(356) | Yes | User login name |
| FULL_NAME | No | NVARCHAR(65) | Yes | Full name (last, first) of user making the changes |
| ENTITY_TYPE | No | NUMERIC(10) | Yes | Entity to which the changes are linked to, defects, test cases or test runs |
| ENTITY_ID | No | NUMERIC(10) | Yes | Link to the record ID in the table specified by ENTITYTYPE |
| AUTO_REASON | No | NVARCHAR(255) | Yes | Description of how item was changed (e.g., renumbered, changed via bulk field changes) |
| ENTITY_IDEN | No | NVARCHAR(255) | No | Description of changed item |
| MAN_REASON | No | NVARCHAR(255) | No | Reason, entered by user, describing why changes were made; identified by ENTITYTYPE and ENTITYID |
| MOD_SOURCE | No | NVARCHAR(255) | No | Description of source of changes (e.g, Web, SOAP, XML) |
| MOD_TYPE | No | NVARCHAR(255) | No | Description of how source changes were made (e.g. Edit Window, List window, bulk field changes) |
| CHANGES | No | NVARCHAR(max) | No | XML-formatted text documents changes |
| HASH | No | NVARCHAR(255) | No | An MD5 hash of the LOGINNAME and DATETIME; verifies that data for this row has not been modified |
| SIG_CAPTURED | No | NUMERIC(1) | No | Indicates if electronic signatured is captured for this change. |
Table: TT_CUSTOM_DEFECT_EVENT_VAL
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record in the TT_FIELD_DEFINITION table (idCustRec) |
| DEFECT_EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_DEFECT_EVENT table (idDefEvt) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Custom values for a defect event (CustValue) |
Table: TT_CUSTOM_DEFECT_VALUE
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DEFECT_ID | No | NUMERIC(10) | No | References a record in the TT_DEFECT table (ParentID) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record in the TT_FIELD_DEFINITION table (idCustRec) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Custom values for a defect (CustValue) |
Table: TT_CUSTOM_DOCUMENT_EVENT_VAL
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record ID in the TT_FIELD_DEFINITION table (idCustRec) |
| DOCUMENT_EVENT_ID | No | NUMERIC(10) | No | References a record ID in the TT_DOCUMENT_EVENT table (idEvent) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Custom values for a document event (CustValue) |
Table: TT_CUSTOM_DOCUMENT_VALUE
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DOCUMENT_ID | No | NUMERIC(10) | No | References a record ID in the TT_DOCUMENT table (ParentID) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record ID in the TT_FIELD_DEFINITION table (idCustRec) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Document custom values (CustValue) |
Table: TT_CUSTOM_POPUP_FIELD
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| POPUP_ID | No | NUMERIC(10) | Yes | References a record ID in the TT_FIELD_POPUP_LIST table (idPUList) |
| FIELD_ORDER | No | NUMERIC(10) | No | Item order relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for pop-up menu items (Descriptor) |
Table: TT_CUSTOM_REQMENT_EVENT_VAL
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| REQUIREMENT_EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_REQUIREMENT_EVENT table (idEvent) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record ID in the TT_FIELD_DEFINITION table (idCustRec) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Requirement event custom values (CustValue) |
Table: TT_CUSTOM_REQUIREMENT_VALUE
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| REQUIREMENT_ID | No | NUMERIC(10) | Yes | References a record ID in the TT_REQUIREMENT table (ParentID) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record ID in the TT_FIELD_DEFINITION table (idCustRec) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Requirement custom values (CustValue) |
Table: TT_CUSTOM_TESTCASE_EVENT_VAL
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTCASE_EVENT_ID | No | NUMERIC(10) | No | References a record ID in the TT_TESTCASE_EVENT table (idDefEvt) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record ID in the TT_FIELD_DEFINITION table (idCustRec) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Test case event custom values (CustValue) |
Table: TT_CUSTOM_TESTCASE_VALUE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTCASE_ID | No | NUMERIC(10) | No | References a record ID in the TT_TESTCASE table (ParentID) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record ID in the TT_FIELD_DEFINITION table (idCustRec) |
| COVERAGE_VARIABLE_STATE | No | NUMERIC(5) | No | Coverage variable type- 0: Unknown, 1: Required, 2: Excluded, 3: Generated, 4: Additional, 5: All Coverage (CvVrState) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Test case custom values (CustValue) |
Table: TT_CUSTOM_TESTRUN_EVENT_VAL
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record ID in the TT_FIELD_DEFINITION table (idCustRec) |
| TESTRUN_EVENT_ID | No | NUMERIC(10) | No | References a record ID in TT_TESTRUN_EVENT table (idDefEvt) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Test run event custom values (CustValue) |
Table: TT_CUSTOM_TESTRUN_VALUE
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTRUN_ID | No | NUMERIC(10) | No | References a record ID in the TT_TESTRUN table (ParentID) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record ID in the TT_FIELD_DEFINITION table (idCustRec) |
| COVERAGE_VARIABLE_STATE | No | NUMERIC(5) | No | Coverage variable type- 0: Unknown, 1: Required, 2: Excluded, 3: Generated, 4: Additional, 5: All Coverage (CvVrState) |
| CUSTOM_VALUE | No | NVARCHAR(max) | No | Test run custom values (CustValue) |
Table: TT_DATABASE_OPTION
| Comment | Contains database option name/value pairs. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| OPTION_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row. |
| OPTION_NAME | No | VARCHAR(252) | No | Option name in the name/value pair |
| OPTION_VALUE | No | VARCHAR(1020) | No | Option value in the name/value pair |
Table: TT_DEFECT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| DEFECT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| CREATED_DATE | No | DATETIME | No | Date/time (in GMT) the defect was added to the database (dateCreate) |
| CREATED_BY | No | NUMERIC(10) | No | User who added the defect. References a record ID in the TT_USER table. (idCreateBy) |
| MODIFIED_DATE | No | DATETIME | No | Date/time (in GMT) the defect was last modified (dateModify) |
| MODIFIED_BY | No | NUMERIC(10) | No | User who last modified the defect. References a record ID in the TT_USER table. (idModifyBy) |
| DEFECT_NUMBER | No | NUMERIC(10) | No | Defect number. Value is zero if a number is not assigned. (DefectNum) |
| SUMMARY | No | NVARCHAR(255) | No | Summary field (Summary) |
| STATE_ID | No | NUMERIC(10) | No | Defect state. References a record ID in the TT_STATE table. (Status) |
| INIT_STATUS | No | NUMERIC(10) | No | Initial defect state (InitStatus) |
| TYPE_ID | No | NUMERIC(10) | No | Type field. References a record ID in the TT_FIELD_TYPE table. (idType) |
| PRODUCT_ID | No | NUMERIC(10) | No | Product field. References a record ID in the TT_FIELD_PRODUCT table. (idProduct) |
| REFERENCE | No | NVARCHAR(255) | No | Reference field (Reference) |
| ENTERED_BY | No | NUMERIC(10) | No | Entered by field. References a record ID in the TT_USER table. (idEnterBy) |
| ENTERED_DATE | No | DATETIME | No | Date/time entered field (in GMT) (dateEnter) |
| DISPOSITION_ID | No | NUMERIC(10) | No | Disposition field. References a record ID in the TT_FIELD_DISPOSITION table. (idDisposit) |
| PRIORITY_ID | No | NUMERIC(10) | No | Priority field. References a record ID in the TT_FIELD_PRIORITY table. (idPriority) |
| COMPONENT_ID | No | NUMERIC(10) | No | Component field. References a record ID in the TT_FIELD_COMPONENT table. (idCompon) |
| SEVERITY_ID | No | NUMERIC(10) | No | Severity field. References a record ID in the TT_FIELDS_SEVERITY table. (idSeverity) |
| ADD_LOCATION_TYPE | No | NUMERIC(5) | No | Method used to add the defect- 0: unknown, 1: Add Defect window, 2: SoloSubmit, 3: SoloBug file, 4: Email import, 5: Text file import, 6: Helix ALM user duplicated a defect. If a defect was created during a conversion from a Helix ALM 1.8.x or Workgroup database, the value is set to unknown (AddLocat) |
| WORKAROUND_DESCRIPTION | No | NVARCHAR(max) | No | Workaround field (Workaround) |
| TICKET_ID | No | NUMERIC(10) | No | Reserved for future functionality (idTicket) |
Table: TT_DEFECTITEM_ATTACHMENT
| Comment | Contains defect file attachment information. Each table row represents one file attached to the defect record. (ATTACHMT) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DEFECT_ID | No | NUMERIC(10) | No | Foreign key to the TT_DEFECT table. Indicates the defect the file is attached to. In Helix ALM, this is EntityRID. |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type - 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before attached to the defect (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date/time (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date/time (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | WYSIWYG field ID that contains inline images (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs to. (SubtypeID) |
Table: TT_DEFECT_ATTACHMENT
| Comment | Contains defect file attachment information. Each table row represents one file attached to the defect report record. (ATTACHMT) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| REPORTED_ID | No | NUMERIC(10) | No | Foreign key to the TT_DEFECT_REPORT table. Defect report the file is attached to. In Helix ALM, this is EntityRID. |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type - 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to the defect (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date/time (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date/time (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | WYSIWYG field ID that contains inline images (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs to. (SubtypeID) |
Table: TT_DEFECT_EVENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| DEFECT_EVENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_EVENT table (EvtDefID) |
| ORDER_NUM | No | NUMERIC(5) | No | Order the defect event was created relative to other defect events. Internal counter for a specific defect. (OrderNum) |
| DEFECT_ID | No | NUMERIC(10) | Yes | References a record in the TT_DEFECT table (ParentID) |
| PARENT_DEFECT_EVENT_ID | No | NUMERIC(10) | No | References a record ID in TT_DEFECT_EVENT table. If the event is a response to a multi-user assignment, the field contains the parent event record ID. If the event is not a response to a multi-user assignment, the field contains -1. (EvtMUParnt) |
| TT_USER_ID | No | NUMERIC(10) | No | References a record ID in TT_USER table. If a user created the event, the field contains the user record ID. If the event was generated by Helix ALM, the field contains a record ID of -2 translated to NULL for the data warehouse. (idUser) |
| EVENT_DATE | No | DATETIME | No | Defect event date/time (dateEvent) |
| NOTES | No | NVARCHAR(max) | No | Notes field (Notes) |
| TIME_SPENT | No | NUMERIC(20, 2) | No | If the definition for this event (TT_EVENT table) has the time tracking option selected, contains the time entered by the user. If time tracking is not enabled, the value is -1. (TimeSpent) |
| STATE_ID | No | NUMERIC(10) | No | References a record ID in the TT_STATE table. If the event affects the resulting state, the field contains the resulting state record ID. If the event does not affect the resulting state, the value is 0. (RsltState) |
| RELEASE_VERSION | No | NVARCHAR(255) | No | Notes field if the event is configured to include release notes information (RelVersion) |
| GENERATED_BY_TYPE | No | NUMERIC(2) | No | How the event was created - 0: Created by user, 1: Created by multi-user assignment, 2: Created by auto assignment, 3: Created by auto escalation (GenByType) |
| CREATED_BY | No | NUMERIC(10) | No | Reserved for future use (CreatorID) |
| DEFAULT_ASSIGN_EFFECT | No | NUMERIC(2) | No | Assignment for the event when it was added - 1: Event results in new assignment, 2: Event has no effect on assignment, 3: Event clears assignment. Intended to preserve history if the event definition is modified (DefAsgEff) |
| WORKFLOW_OVERRIDE | No | NUMERIC(1) | No | Indicates if the event is a result of a workflow override (OvrWF) |
| WORKFLOW_OVERRIDE_USER_ID | No | NUMERIC(10) | No | References the TT_USER table. If the event is a result of a workflow override, the value is the record ID in use. Otherwise, the value is 0. (OvrWFUsrID) |
| ITEM_MARK_SUSPECT | No | NUMERIC(1) | No | Indicates if the user marked dependent items as suspect (SspLnkItms) |
Table: TT_DEFECT_EVENT_ASGN_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | User the defect is assigned to |
| DEFECT_EVENT_ID | Yes | NUMERIC(10) | Yes | Defect assigned to the user |
Table: TT_DEFECT_EVENT_ATCHMT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DEFECT_EVENT_ID | No | NUMERIC(10) | No | Foreign key to the TT_DEFECT_EVENT table. Defect event the file is attached to. (EntityRID) |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type - 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to an entity (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that contains the WYSIWYG inline image (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs to. (SubtypeID) |
Table: TT_DEFECT_LOG
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| DEFECT_LOG_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TT_USER_ID | No | NUMERIC(10) | No | User who made the change. References a record in the TT_USER table. (idUser) |
| DEFECT_ID | No | NUMERIC(10) | No | References a record in the TT_DEFECT table (ParentID) |
| LOG_DATE | No | DATETIME | No | Date/time the change occurred (dateLog) |
| NOTES | No | NVARCHAR(4000) | No | Change description (Notes) |
Table: TT_DEFECT_REPORT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| REPORTED_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DEFECT_ID | No | NUMERIC(10) | Yes | References a record in the TT_DEFECT table (idDefRec) |
| FOUND_BY | No | NUMERIC(10) | No | Found by field. References a record in the TT_USER table. (idFoundBy) |
| FOUND_DATE | No | DATETIME | No | Found by date field (dateFound) |
| ORDER_NUM | No | NUMERIC(5) | No | Reported by record order relative to other reported by records. Internal counter for a specific defect. (OrderNum) |
| VERSION_FOUND | No | NVARCHAR(32) | No | Version found field. Stores item text if it is selected from the FLDVERSN table in the application, but that table is not carried over because no foreign key is needed. This value is stored as the actual version. (VersnFound) |
| REPORT_DESCRIPTION | No | NVARCHAR(max) | No | Description field (Descrptn) |
| REPRODUCED_ID | No | NUMERIC(10) | No | Reproduced field. References a record ID in the TT_FIELD_REPRODUCED table. (idReprod) |
| REPRODUCED_STEPS | No | NVARCHAR(max) | No | Steps to reproduce field (ReproSteps) |
| TEST_CONFIG_TYPE | No | NUMERIC(5) | No | Computer configuration field type - 1: User Test Configuration, 2: Standard Test Configuration (TstConType) |
| CONFIG_ID | No | NUMERIC(10) | No | Standard computer configuration field. References a record ID in the TT_SYSTEM_CONFIG table. (idConfig) |
| OTHER_HARDWARE_SOFTWARE | No | NVARCHAR(max) | No | Other hardware and software field (OtherHwSw) |
| CONTACT_INFORMATION | No | NVARCHAR(63) | No | User contact information (phone number or email address) (Contact) |
Table: TT_DEFECT_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. Not available in the Helix ALM application. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_DEFECT_VALUE table. Defect and field definition |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Custom pop-up menu field |
Table: TT_DEFECT_SELECT_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_DEFECT_VALUE table. Defect and field definition |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer. |
Table: TT_DEFEVENT_SELECT_FIELD
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_DEFECT_EVENT_VALUE table. Defect event and field definition |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Custom pop-up menu field |
Table: TT_DEFEVENT_SELECT_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_DEFECT_EVENT_VALUE table. Defect event and field definition |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer |
Table: TT_DOCEVENT_RESULT_STATE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| STATE_ID | Yes | NUMERIC(10) | Yes | Event resulting state |
| DOCUMENT_EVENT_ID | Yes | NUMERIC(10) | Yes | Requirement document event the state relates to |
Table: TT_DOCEVENT_SELECT_FIELD
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_DOCUMENT_EVENT_VALUE table. Document event and field definition |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Pop-up menu field |
Table: TT_DOCEVENT_SELECT_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_DOCUMENT_EVENT_VALUE table. Document event and field definition |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer |
Table: TT_DOCUMENT
| Comment | Contains requirement document information. Each table row represents one requirement document. (DOCUMENT) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| DOCUMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| CREATED_DATE | No | DATETIME | No | Date/time (in GMT) the document was added to the database (dateCreate) |
| CREATED_BY | No | NUMERIC(10) | No | User who added the document. References a record in the TT_USER table. (idCreateBy) |
| MODIFIED_DATE | No | DATETIME | No | Date/time (in GMT) document was last modified (dateModify) |
| MODIFIED_BY | No | NUMERIC(10) | No | User who last modified the document. References a record in the TT_USER table. (idModifyBy) |
| DOCUMENT_NUMBER | No | NUMERIC(10) | No | Document number. Value is 0 if a number is not assigned. (DocNum) |
| DOCUMENT_NAME | No | NVARCHAR(255) | No | Document name (Name) |
| STATE_ID | No | NUMERIC(10) | No | Current document workflow state. References a record in the TT_STATE table. (idStatus) |
| ADD_LOCATION | No | NUMERIC(5) | No | Location in the application the document was added from (e.g., Add Requirement Document window) (AddLocat) |
| DOCUMENT_VERSION | No | NUMERIC(10) | No | Current document version number (Version) |
| DOCUMENT_DESCRIPTION | No | NVARCHAR(max) | No | Document description (Descrptn) |
| PAGE_WIDTH | No | NUMERIC(10, 3) | No | Page width for multi-line text fields in the Specification Document window (PgWidth) |
| LEFT_MARGIN | No | NUMERIC(10, 3) | No | Left margin indent in the Specification Document window (LeftMargin) |
| UNIT_TYPE | No | NUMERIC(2) | No | Units the page width and left margin are specified in- 0: Pixels, 1: Inches, 2: Centimeters (UnitType) |
| INITIAL_STATE | No | NUMERIC(10) | No | Record ID of the initial state for the document |
Table: TT_DOCUMENT_ATTACHMENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DOCUMENT_ID | No | NUMERIC(10) | No | Foreign key to the TT_DOCUMENT table. Document the attachment is associated with. (EntityRID) |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type - 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to an entity (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in the database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that contains the WYSIWYG inline image (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs. (SubtypeID) |
Table: TT_DOCUMENT_CHANGE
| Comment | Contains the original values for fields that changed after a requirement document snapshot was created. The document always stores the current value. (DOCCHNGS) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| DOCUMENT_CHANGE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| SNAPSHOT_ID | No | NUMERIC(10) | No | References a record in the TT_DOCUMENT_SNAPSHOT table (ParentID) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record in the TT_FIELD_DEFINITION table. (idField) |
| HAS_VALUE | No | NUMERIC(1) | No | Indicates if the OrigValue field represents original value. If false, the original value was NULL. (HasValue) |
| ORIGINAL_VALUE | No | NVARCHAR(max) | No | Original value for the field stored as the string value (OrigValue) |
Table: TT_DOCUMENT_EVENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| DOCUMENT_EVENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_EVENT table (EvtDefID) |
| ORDER_NUMBER | No | NUMERIC(5) | No | Identifies the order the document event was created relative to other document events. Internal counter for a specific document. (OrderNum) |
| DOCUMENT_ID | No | NUMERIC(10) | Yes | References a record in the TT_DOCUMENT table (ParentID) |
| PARENT_DOCUMENT_EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_DOCUMENT_EVENT table. If the event is a response to a multi-user assignment, the value is the record ID of the parent event. If the event is not a response to a multi-user assignment, the value is -1. (EvtMUParnt) |
| TT_USER_ID | No | NUMERIC(10) | No | References a record in the TT_USER table. If a user entered the event, the value is the record ID of the user. If the event was generated by Helix ALM, the field contains a record ID of -2. (idUser) |
| EVENT_DATE | No | DATETIME | No | Document event date (dateEvent) |
| NOTES | No | NVARCHAR(max) | No | Notes field (Notes) |
| TIME_SPENT | No | NUMERIC(20, 2) | No | If the definition for this event (TT_EVENT table) has the time tracking option selected, contains the time entered by the user. If time tracking is not enabled for the event, the value is -1. (TimeSpent) |
| RELEASE_VERSION | No | NVARCHAR(255) | No | Notes field if event is configured to include release notes information (RelVersion) |
| GENERATED_BY_TYPE | No | NUMERIC(2) | No | How the event was created - 0: Created by user, 1: Created by multi-user assignment, 2: Created by auto assignment, 3: Created by auto escalation (GenByType) |
| CREATED_BY | No | NUMERIC(10) | No | Reserved for future use (CreatorID) |
| DEFAULT_ASSIGN_EFFECT | No | NUMERIC(2) | No | Assignment for the event when it was run - 1: Event results in new assignment, 2: Event has no effect on assignment, 3: Event clears assignment. Intended to preserve history if the event definition is modified (DefAsgEff) |
| WORKFLOW_OVERRIDE | No | NUMERIC(1) | No | Indicates if the event is a result of a workflow override (OvrWF) |
| WORKFLOW_OVERRIDE_USER_ID | No | NUMERIC(10) | No | References the TT_USER table. If the event is a result of a workflow override, the value is the record ID of use. Otherwise, field value is 0. (OvrWFUsrID) |
| ITEM_MARK_SUSPECT | No | NUMERIC(1) | No | Indicates if the user selected the option to mark dependent items as suspect (SspLnkItms) |
| DOCUMENT_VERSION | No | NUMERIC(10) | No | Version number of the document that was current when the event was entered (Version) |
Table: TT_DOCUMENT_EVENT_ASGN_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users the document events are assigned to |
| DOCUMENT_EVENT_ID | Yes | NUMERIC(10) | Yes | List of document events assigned to a user |
Table: TT_DOCUMENT_EVENT_ATCHMT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DOCUMENT_EVENT_ID | No | NUMERIC(10) | No | References the TT_DOCUMENT_EVENT table. Document event the file is attached to. (EntityRID) |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type - 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to an entity (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that contains the WYSIWYG inline image (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs. (SubtypeID) |
Table: TT_DOCUMENT_LOG
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| DOCUMENT_LOG_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TT_USER_ID | No | NUMERIC(10) | No | User who made change. References a record in the TT_USER table. (idUser) |
| DOCUMENT_ID | No | NUMERIC(10) | No | References a record in the TT_DOCUMENT table (ParentID) |
| LOG_DATE | No | DATETIME | No | Date/time the change occurred (dateLog) |
| NOTES | No | NVARCHAR(4000) | No | Change description (Notes) |
Table: TT_DOCUMENT_REQUIREMENT_TREE
| Comment | Contains the requirement relationship tree for the current version of the requirement document (DOCTREE) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TREE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DOCUMENT_ID | Yes | NUMERIC(10) | Yes | References a record in the TT_DOCUMENT table (idDocument) |
| PARENT_TREE_ID | No | NUMERIC(10) | No | References a record ID in the TT_DOCUMENT_REQUIREMENT_TREE table. Contains the record of the parent node in the tree. If the node is at the top level, the value is 0. (ParentID) |
| REQUIREMENT_ID | No | NUMERIC(10) | No | References a record in the TT_REQUIREMENT table (idReqmnt) |
| SIBLING_ORDER | No | NUMERIC(10) | No | Order of the node relative to siblings in the parent node (SibOrder) |
| IS_SUSPECT | No | NUMERIC(1) | No | Indicates if the node is marked as suspect (IsSuspect) |
Table: TT_DOCUMENT_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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_DOCUMENT_VALUE table. Document and field definition |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Custom pop-up menu field |
Table: TT_DOCUMENT_SELECT_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_DOCUMENT_EVENT_VALUE table. Document and field definition |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer |
Table: TT_DOCUMENT_SNAPSHOT
| Comment | Contains requirement document snapshot information. Each table row represents one document snapshot. (DOCSNPST) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| SNAPSHOT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DOCUMENT_ID | No | NUMERIC(10) | No | References a record in the TT_DOCUMENT table (idDocument) |
| CREATED_DATE | No | DATETIME | No | Date/time (in GMT) snapshot was added to the database (dateCreate) |
| CREATED_BY | No | NUMERIC(10) | No | User who added the snapshot. References a record in the TT_USER table. (idCreateBy) |
| SNAPSHOT_VERSION | No | NUMERIC(10) | No | Snapshot version number (Version) |
| SNAPSHOT_LABEL | No | NVARCHAR(32) | No | Snapshot label (Label) |
| SNAPSHOT_COMMENT | No | NVARCHAR(max) | No | Snapshot comment (Commnt) |
Table: TT_EMAIL
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EMAIL_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| IS_ORPHAN | No | NUMERIC(1) | No | Indicates if email is associated with an entity (IsOrphan) |
| EMAIL_SUBJECT | No | NVARCHAR(255) | No | Email subject (Subject) |
| EMAIL_BODY | No | NVARCHAR(max) | No | Email message body (Body) |
| SENT_DATE | No | DATETIME | No | Date/time email was sent (DateSent) |
| RECEIVED_DATE | No | DATETIME | No | Date/time email was received (DateRecd) |
| THREAD_MESSAGE_ID | No | NVARCHAR(255) | No | Email message ID in the thread (ThdMsgID) |
| EMAIL_DIRECTION | No | NUMERIC(5) | No | Indicates if the email was sent or received - 0: outgoing, 1: incoming (Direction) |
| IS_HTML | No | NUMERIC(1) | No | Indicates if the email is in HTML format (IsHtml) |
Table: TT_EMAIL_DEFECT
| Comment | Contains information about defects that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EMAIL_DEFECT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DEFECT_ID | No | NUMERIC(10) | No | References a record ID in the TT_DEFECT table (EntityRID) |
| EMAIL_ID | No | NUMERIC(10) | No | References a record ID in the TT_EMAIL table (EmailID) |
| PARENT_EMAIL_ID | No | NUMERIC(10) | No | Parent email ID (ParentID) |
Table: TT_EMAIL_DOCUMENT
| Comment | Contains information about requirement documents that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EMAIL_DOCUMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| DOCUMENT_ID | No | NUMERIC(10) | No | References a record ID in the TT_DOCUMENT table (EntityRID) |
| EMAIL_ID | No | NUMERIC(10) | No | References a record ID in the TT_EMAIL table (EmailID) |
| PARENT_EMAIL_ID | No | NUMERIC(10) | No | Parent email ID (ParentID) |
Table: TT_EMAIL_RECIPIENT
| Comment | Contains email recipient information. This table has a many-to-one relationship with the TT_EMAIL table.(EMAILRECP) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EMAIL_RECIPIENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| EMAIL_ID | No | NUMERIC(10) | No | References a record ID in the TT_EMAIL table (EmailID) |
| RECIPIENT_TYPE | No | NUMERIC(1) | No | Recipient type - 1: From, 2: To, 3: Cc, 4: Bcc (Type) |
| TT_USER_ID | No | NUMERIC(10) | No | Reference a record ID in the TT_USER table (UserID) |
| EMAIL_ADDRESS | No | NVARCHAR(63) | No | Recipient email address (Address) |
Table: TT_EMAIL_REQUIREMENT
| Comment | Contains information about the requirements that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EMAIL_REQUIREMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| REQUIREMENT_ID | No | NUMERIC(10) | No | References a record ID in the TT_REQUIREMENT table (EntityRID) |
| EMAIL_ID | No | NUMERIC(10) | No | References a record ID in TT_EMAIL table (EmailID) |
| PARENT_EMAIL_ID | No | NUMERIC(10) | No | Parent email ID (ParentID) |
Table: TT_EMAIL_TESTCASE
| Comment | Contains information about the test cases that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EMAIL_TESTCASE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTCASE_ID | No | NUMERIC(10) | No | References a record ID in the TT_TESTCASE table (EntityRID) |
| EMAIL_ID | No | NUMERIC(10) | No | References a record ID in the TT_EMAIL table (EmailID) |
| PARENT_EMAIL_ID | No | NUMERIC(10) | No | Parent email ID (ParentID) |
Table: TT_EMAIL_TESTRUN
| Comment | Contains information about the test runs that tracked emails are associated with. Each table row represents an email association with one entity. (EMAILASSOC) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EMAIL_TESTRUN_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTRUN_ID | No | NUMERIC(10) | No | References a record ID in the TT_TESTRUN table (EntityRID) |
| EMAIL_ID | No | NUMERIC(10) | No | References a record ID in the TT_EMAIL table (EmailID) |
| PARENT_EMAIL_ID | No | NUMERIC(10) | No | Parent email ID (ParentID) |
Table: TT_EMAIL_TYPE
| Comment | Lists email types. Not available in the Helix ALM application. Used to describe email types to data warehouse users. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| EMAIL_TYPE | Yes | NUMERIC(2) | Yes | Email type unique identifier |
| EMAIL_DESCRIPTION | No | NVARCHAR(50) | Yes | Email type description (e.g., Internet, MAPI, Other) |
Table: TT_ENTITY_TYPE
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| ENTITY_TYPE | Yes | NUMERIC(10) | Yes | Helix ALM internal code for the entity type |
| ENTITY_TYPE_DESCRIPTION | No | VARCHAR(180) | Yes | Entity name the code relates to |
Table: TT_EVENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| ENTITY_TYPE | No | NUMERIC(10) | No | Foreign key to the TT_ENTITY_TYPE table. Entity type the event is linked to. (EntityType) |
| EVENT_NAME | No | NVARCHAR(32) | No | Event name (Name) |
| EVENT_DESCRIPTION | No | NVARCHAR(255) | No | Event description (EventDesc) |
| ACTIVE | No | NUMERIC(1) | No | Indicates if the event is active in the workflow (Active) |
| EVENT_ORDER | No | NUMERIC(10) | No | Order events are displayed in the workflow configuration dialog boxes (EventOrder) |
| INFORMATIONAL_ONLY | No | NUMERIC(1) | No | Indicates if the event is informational only or affects the current state of the entity (Inform) |
| ALLOW_ATTACHMENT | No | NUMERIC(1) | No | Indicates if files can be attached to the event (AllowAttch) |
| TIME_TRACK_ENABLE | No | NUMERIC(1) | No | Indicates if time tracking is enabled for the event (TimeTrk) |
| TIME_TRACK_OPERATION | No | NUMERIC(2) | No | How time tracking works - 1: display sum of event hours, 2: display last even hours (TimeTrkOpt) |
| ASSIGN_EFFECT | No | NUMERIC(2) | No | Assignment value - 1: event results in new assignment, 2: event has no effect on assignment, 3: event clears assignment (AssignEff) |
| QUICK_LINK_ICON | No | NVARCHAR(255) | No | File name used as a graphic on the Helix ALM Web list window for the event (QkLinkIcon) |
| EVENT_ICON | No | IMAGE | No | Binary data for the toolbar icon displayed in the Helix ALM Windows Client (EventIcon) |
| ICON_ON_WINDOWS_TOOLBAR | No | NUMERIC(1) | No | Indicates if icon is displayed on the Windows toolbar (IncEvtIcon) |
| EVENT_ICON_NAME | No | NVARCHAR(255) | No | Event icon file name (EvtIconNm) |
| EVENT_IN_RELEASE_NOTES | No | NUMERIC(1) | No | Indicates if the event notes should be included with release notes (EvtIncRel) |
| ALLOW_MULTIPLE_USERS | No | NUMERIC(1) | No | Indicates if multiple user assignments are allowed (AllowMUAs) |
| REQUIRE_ELECTRONIC_SIG | No | NUMERIC(1) | No | Indicates if electronic signature is required to complete the event (ReqESigs) |
| HIDE_DIALOG | No | NUMERIC(1) | No | Indicates to hide the dialog if there are no fields to display (HideDlg) |
| INCLUDE_NOTES_REQUIREMENT | No | NUMERIC(1) | No | Indicates if event notes should be included in requirement document review mode. Only applies to requirements. (EvVsRwMod) |
| DEPENDENT_ITEM_SUSPECT | No | NUMERIC(1) | No | Indicates if the event should allow marking dependent items as suspect (DnLnkSusp) |
Table: TT_EVENT_RESULT_STATE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| STATE_ID | Yes | NUMERIC(10) | Yes | Event resulting state |
| EVENT_ID | Yes | NUMERIC(10) | Yes | Event the state is related to |
Table: TT_EXTERNAL_PROVIDER
| Comment | Contains external source control provider information (Git, GitHub, etc.) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_PROVIDER_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| PROVIDER_NAME | No | VARCHAR(1024) | Yes | Provider name. Field is required and must be unique. |
| ACTIVE | No | NUMERIC(1) | Yes | Indicates if provider is active |
| PROVIDER_TYPE | No | NUMERIC(10) | No | Provider type - 1: Source control provider |
| PROVIDER_SUBTYPE | No | NUMERIC(10) | No | Provider subtype - 0: Other, 1: Surround SCM, 2: Git, 3: GitHub |
| API_KEY | No | VARCHAR(256) | No | Provider key that uniquely identifies the provider when it connects to the project |
| SERVER_ADDRESS | No | VARCHAR(2048) | No | Surround SCM Server address |
| SERVER_PORT | No | NUMERIC(10) | No | Surround SCM Server port |
| COMMIT_URL | No | VARCHAR(4000) | No | Commit URL |
| FILE_URL | No | VARCHAR(4000) | No | File URL |
| REPO_URL | No | VARCHAR(4000) | No | GitHub repository URL |
Table: TT_FIELD_COMPONENT
| Comment | Contains the Component field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDCOMP) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| COMPONENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up menu item order relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_FIELD_DEFINITION
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FIELD_DEFINITION_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| EVENT_ID | No | NUMERIC(10) | No | References a record of event definition. Value is TT_EVENT if the definition is for an event field. Value is 0 for entity fields. (EntityRID) |
| LINK_DEFINITION_ID | No | NUMERIC(10) | No | References a record for a link definition. Value is TT_LINK_DEFINITION if the definition is for a link. |
| ENTITY_TYPE | No | NUMERIC(10) | No | Foreign key to the TT_ENTITY_TYPE table. Table this field is linked to. (EntityType) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that uniquely identifies a field in an entity type (FieldID) |
| FIELD_POSITION | No | NUMERIC(10) | No | Field position. For custom fields, the field value is the order that the field is displayed on the Custom Field tab. For inherent fields, the value is -1. (Position) |
| FIELD_CODE | No | NVARCHAR(255) | No | Character string used as a replacement field code for email templates (FieldCode) |
| FIELD_TYPE | No | NUMERIC(10) | No | Field type- 1: pop-up menu, 2: string, 3: Boolean, 4: date, 5: version field, 6: component, 7: disposition (FieldType) |
| FIELD_OPTIONS | No | NUMERIC(10) | No | Data allowed for the field- 0: no option specified, 1: integer values, 2: floating point values, 3: include time - only for date fields, 5: memo field, 6: hyperlink (FieldOpts) |
| FIELD_FLAG_OPTIONS | No | NUMERIC(10) | No | Field flag options- 0: no option specified, 1: include global users or customers, 2: include local users or customers, 4: multi-select field (FldFlgOpts) |
| IMP_EXP_OPTION_FLAG | No | NUMERIC(10) | No | Bit flag that indicates the available text import/export options. Options can be combined with an OR operator- 0x0001: field can be imported via text import, 0x0002: field can be exported via text export, 0x0004: field defaults to selected on text export dialog, 0x0008: field defaults to selected on text import dialog (AttFlag) |
| SHORT_NAME | No | NVARCHAR(255) | No | Field name displayed in the entity or event dialog (ShortName) |
| LONG_NAME | No | NVARCHAR(255) | No | Field name displayed in list windows, filters, and reports (LongName) |
| WEB_CODE | No | NVARCHAR(255) | No | Character string used to parse data read-in from Helix ALM Web. Data cannot be modified. (WebCode) |
| MAX_SIZE | No | NUMERIC(10) | No | Maximum field length. Only applies to custom fields for the entity and entity events. All other fields have a value of -1. (MaxSize) |
| NUMBER_OF_ROWS | No | NUMERIC(10) | No | Number of rows for multi-line text fields. Minimum value is 2, maximum is 10. (NumRows) |
| ACTIVE | No | NUMERIC(1) | No | Indicates if the field is in use (Active) |
| EDIT_REQUIRED_DEFAULT | No | NUMERIC(1) | No | Indicates if required fields and default values can be modified (EdtReqDflt) |
| DEFAULT_VALUE | No | NUMERIC(10) | No | Default field value. Stored values are based on field type. For string fields, the only value allowed is -4 (blank record ID). For pop-up menus, the allowed values are 0 (not set record ID) and any valid record ID in corresponding table. For user fields, allowed values are: -2 (current user), 0 (not set record ID). For date fields, allowed values are: 0 (not set record ID), 1 (current date). (DefaultVal) |
| ALLOW_DEFAULT | No | NUMERIC(1) | No | Indicates if the default can be set (AllowDeflt) |
| REQUIRED | No | NUMERIC(1) | No | Indicates if the field is required (Required) |
| POPUP_ID | No | NUMERIC(10) | No | Table ID for inherent fields. Only applies to pop-up menu items. Record in TT_FIELD_POPUP_LIST for custom pop-up menu items. Value is 0 for other field types. (idPUList) |
| DEFAULT_STR | No | NVARCHAR(max) | No | Reserved for future use (DefaultStr) |
Table: TT_FIELD_DISPOSITION
| Comment | Contains the Disposition field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDDISPO) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| DISPOSITION_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up menu item order relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_FIELD_POPUP_LIST
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| POPUP_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row in a project (idRecord)
(0) None
(1) Dropdown
(2) String - not a list
(3) Boolean - not a list
(4) Date - not a list
(5) Version
(6) Component
(7) Disposition
(8) Priority
(9) Product
(10) Reproducible
(11) Severity
(12) Type
(14) TstObjectType
(15) TestRunSet
(16) RequirementPriority
(100) Users
(101) Customers
(102) Users and Customers |
| LIST_NAME | No | NVARCHAR(32) | No | Pop-up menu name (ListName) |
Table: TT_FIELD_PRIORITY
| Comment | Contains the Priority field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDPRIOR) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| PRIORITY_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up menu item order relative to other items (fieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_FIELD_PRODUCT
| Comment | Contains the Product field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDPROD) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| PRODUCT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up menu item order relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_FIELD_REPRODUCED
| Comment | Contains the Reproduced field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDREPRO) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| REPRODUCED_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up menu item order relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_FIELD_REQUIREMENT_PRIORITY
| Comment | Contains the requirement Priority field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDRPRIO) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| PRIORITY_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up menu item order relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_FIELD_SEVERITY
| Comment | Contains the Severity field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDSEVER) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| SEVERITY_ID | Yes | NUMERIC(10) | Yes | Pop-up menu item order relative to other items (FieldOrder) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up item order, relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_FIELD_STYLE
| Comment | Contains field value style information |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FIELD_STYLE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| STYLE_NAME | No | VARCHAR(1020) | Yes | Field value style name |
| STYLE_ORDER | No | NUMERIC(10) | Yes | Order of style in list |
| BOLD | No | NUMERIC(1) | Yes | Indicates if style is bold |
| ITALIC | No | NUMERIC(1) | Yes | Indicates if style is italic |
| UNDERLINE | No | NUMERIC(1) | Yes | Indicates if style is underlined |
| STRIKEOUT | No | NUMERIC(1) | Yes | Indicates if style is strikethrough |
| HIDE_TEXT | No | NUMERIC(1) | Yes | Indicates if text is hidden when style is applied |
| HEX_COLOR | No | VARCHAR(24) | Yes | Text color for style. Hex value |
| HEX_BACKGROUND_COLOR | No | VARCHAR(24) | Yes | Background color for style. Hex value. |
| ICON | No | VARBINARY(max) | No | Binary data that contains icon image file |
Table: TT_FIELD_STYLE_POPUP
| Comment | Contains associations between field value styles and pop-up menu items or workflow states |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FIELD_STYLE_POPUP_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| FIELD_STYLE_ID | No | NUMERIC(10) | Yes | References the TT_FIELD_STYLE table. Record ID of field style applied to item. |
| POPUP_ID | No | NUMERIC(10) | Yes | Record ID of pop-up menu that contains the list value |
| POPUP_FIELD_ID | No | NUMERIC(10) | Yes | Record ID of pop-up menu list value the style is applied to |
Table: TT_FIELD_STYLE_STATE
| Comment | Contains associations between fields and workflow states with field value styles |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FIELD_STYLE_STATE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| ENTITY_TYPE | No | NUMERIC(10) | Yes | Item type for workflow state |
| FIELD_STYLE_ID | No | NUMERIC(10) | Yes | Record ID of the style applied to item |
| STATE_ID | No | NUMERIC(10) | Yes | Record ID of workflow state applied to item |
Table: TT_FIELD_TESTOBJECT_TYPE
| Comment | Contains test object Type field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDTOTP) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from.. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TESTOBJECT_TYPE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up menu item order relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_FIELD_TYPE
| Comment | Contains the Type field pop-up menu values. Each row in this table represents one pop-up menu item. (FLDTYPE) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TYPE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up menu item order relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_FOLDER
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FOLDER_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| OWNER_USER_ID | No | NUMERIC(10) | No | References a record in the TT_USER table (OwnerID) |
| PARENT_FOLDER_ID | No | NUMERIC(10) | No | Parent folder record ID (ParentID) |
| FOLDER_ORDER | No | NUMERIC(5) | No | Folder order relative to other folders (FldrOrder) |
| FOLDER_NAME | No | NVARCHAR(127) | No | Folder name (Name) |
| FOLDER_DESCRIPTION | No | NVARCHAR(255) | No | Folder description (Descrptn) |
| CREATED_DATE | No | DATETIME | No | Date/time the folder was created (dateCreate) |
| CREATED_BY | No | NUMERIC(10) | No | User who created the folder. References a record in the TT_USER table. (idCreateBy) |
| MODIFIED_DATE | No | DATETIME | No | Date/time the folder was last modified (dateModify) |
| MODIFIED_BY | No | NUMERIC(10) | No | User who last modified the folder. References a record in the TT_USER table. (idModifyBy) |
| ADDED_FROM | No | NUMERIC(5) | No | How the folder was added- 0: location unknown, 1: Add window, 2: SoloSubmit page, 3: SoloBug import, 4: email import, 5: text import, 6: duplicated, 7: XML import, 8: SOAP API, 9: help desk - obsolete, 10: QA Wizard Pro, 11: generated test run, 12: Helix ALM Outlook add-in (AddedFrom) |
| MULTI_DESCRIPTION | No | NVARCHAR(max) | No | Reserved for future use (MultiDesc) |
| URL | No | NVARCHAR(max) | No | Reserved for future use (URL) |
Table: TT_FOLDER_DEFECT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FOLDER_DEFECT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FOLDER_ID | No | NUMERIC(10) | No | References a record ID in the TT_FOLDER table (FolderID) |
| DEFECT_ID | No | NUMERIC(10) | No | References a record in the TT_DEFECT table (EntityID) |
| ITEM_RANK | No | NUMERIC(10) | No | Folder rank |
Table: TT_FOLDER_DETAIL
| Comment | Contains the additional folder details for the Folder table (FLDRDTL) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FOLDER_DETAIL_ID | Yes | NUMERIC(10) | Yes | Primary key to the FOLDER_DETAIL_ID table (idRecord) |
| FOLDER_TYPE_ID | No | NUMERIC(10) | No | Folder type (FldrTypID) |
| FOLDER_DETAILS | No | NVARCHAR(max) | No | Folder details WYSIWYG text (FldrDtls) |
| ALLOW_EDIT_DETAILS | No | NUMERIC(1) | No | Indicates if users can edit the folder details from the list window (AllwEdtDtl) |
| WEB_URL | No | NVARCHAR(max) | No | Folder web URL (WebUrl) |
| START_DATE | No | DATETIME | No | Folder release planning start date (StartDate) |
| END_DATE | No | DATETIME | No | Folder release planning end date (EndDate) |
| INCLUDE_WEEKENDS | No | NUMERIC(1) | No | Folder release planning include weekends flag (InclWkEnds) |
| NON_WORK_DAYS | No | NUMERIC(10) | No | Folder release planning non-working days (NonWkDys) |
| WORK_HOURS | No | NUMERIC(20, 2) | No | Folder release planning work hours (WorkHrs) |
| AVAILABLE_USERS | No | NUMERIC(20, 2) | No | Folder release planning available users (AvailUsrs) |
| PTO_HOURS | No | NUMERIC(20, 2) | No | Folder release planning vacation and holiday hours (PtoHrs) |
| STORY_PTS | No | NUMERIC | No | Folder release planning target story points (StoryPts) |
Table: TT_FOLDER_DOCUMENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FOLDER_DOCUMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FOLDER_ID | No | NUMERIC(10) | No | References a record ID in the TT_FOLDER table (FolderID) |
| DOCUMENT_ID | No | NUMERIC(10) | No | References a record in the TT_DOCUMENT table (EntityID) |
| ITEM_RANK | No | NUMERIC(10) | No | Folder rank |
Table: TT_FOLDER_LOG
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FOLDER_LOG_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TT_USER_ID | No | NUMERIC(10) | No | User who made change. Links to a record in the TT_USER table. (idUser) |
| FOLDER_ID | No | NUMERIC(10) | No | References a record in the TT_FOLDER table (ParentID) |
| LOG_DATE | No | DATETIME | No | Date/time the change occurred (dateLog) |
| NOTES | No | NVARCHAR(4000) | No | Change description (Notes) |
Table: TT_FOLDER_REQUIREMENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FOLDER_REQUIREMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FOLDER_ID | No | NUMERIC(10) | No | References a record ID in the TT_FOLDER table (FolderID) |
| REQUIREMENT_ID | No | NUMERIC(10) | No | References a record in the TT_REQUIREMENT table (EntityID) |
| ITEM_RANK | No | NUMERIC(10) | No | Folder rank |
Table: TT_FOLDER_TESTCASE
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FOLDER_TESTCASE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FOLDER_ID | No | NUMERIC(10) | No | References a record ID in the TT_FOLDER table (FolderID) |
| TESTCASE_ID | No | NUMERIC(10) | No | References a record in the TT_TESTCASE table (EntityID) |
| ITEM_RANK | No | NUMERIC(10) | No | Folder rank |
Table: TT_FOLDER_TESTRUN
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FOLDER_TESTRUN_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FOLDER_ID | No | NUMERIC(10) | No | References a record ID in the TT_FOLDER table (FolderID) |
| TESTRUN_ID | No | NUMERIC(10) | No | References a record in the TT_TESTRUN table (EntityID) |
| ITEM_RANK | No | NUMERIC(10) | No | Folder rank |
Table: TT_FOLDER_TYPE
| Comment | Contains folder type information. Each table row represents one type value. (FLDRTYP) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| FOLDER_TYPE_ID | Yes | NUMERIC(10) | Yes | Primary key to the TT_FOLDER_TYPE table (idRecord) |
| FOLDER_NAME | No | NVARCHAR(128) | No | Folder type name (Name) |
| FOLDER_DESCRIPTION | No | NVARCHAR(255) | No | Folder type description (Descrptn) |
| OPEN_ICON | No | IMAGE | No | Open folder icon image (OpenIcon) |
| OPEN_ICON_NAME | No | NVARCHAR(255) | No | Open folder icon name (OpnIconNm) |
| CLOSED_ICON | No | IMAGE | No | Closed folder icon image (ClosedIcon) |
| CLOSED_ICON_NAME | No | NVARCHAR(255) | No | Closed folder icon name (ClsIconNm) |
| IS_ACTIVE | No | NUMERIC(1) | No | Indicates if the folder type is active (IsActive) |
| ALLOW_URL | No | NUMERIC(1) | No | Indicates if the folder type supports URLs (AllowUrl) |
| ALLOW_WYG_TEXT | No | NUMERIC(1) | No | Indicates if the folder type supports WYSIWYG text (AllwWygTxt) |
| ALLOW_TM_TRK | No | NUMERIC(1) | No | Indicates if the folder type supports release planning fields (AllwTmTrk) |
| ORDER_NUMBER | No | NUMERIC(5) | No | Order number of the folder type relative to other folder types (OrderNum) |
| BANNER_COLOR | No | NVARCHAR(24) | No | Banner color for the folder type (BannerClr) |
Table: TT_LINK
| Comment | Contains a list of items added to a link (LINKS) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| LINK_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| LINK_DEFINITION_ID | No | NUMERIC(10) | Yes | References the TT_LINK_DEFINITION table. Link type. (LinkDefID) |
| LINK_STATUS | No | NUMERIC(5) | No | Reserved for future use (LinkStatus) |
| LINK_COMMENT | No | NVARCHAR(255) | No | Comment entered by a user when the link was created (LinkCommnt) |
Table: TT_LINK_DEFINITION
| Comment | Contains a list of user-defined link definitions (LINKDFNTN) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| LINK_DEFINITION_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| LINK_ORDER | No | NUMERIC(10) | No | Order of the row in the list of link definitions (LinkOrder) |
| LINK_NAME | No | NVARCHAR(32) | No | Unique link definition name (LinkName) |
| LINK_COMMENT | No | NVARCHAR(255) | No | Comment associated with the link definition (LinkCommnt) |
| LINK_REQUIRES_PARENT | No | NUMERIC(1) | No | Indicates if the link definition requires a parent (LinkParent) |
| LINK_ACTIVE | No | NUMERIC(1) | No | Indicates if the link definition is active (LinkActive) |
| ALLOWED_ENTITIES | No | NVARCHAR(255) | No | Indicates allowed entities for the link (LinkEnts) |
| COMMENT_REQUIRED | No | NUMERIC(1) | No | Indicates if a link comment is required when creating a new link using this definition (ComntReqd) |
| ALLOWED_PARENTS | No | VARCHAR(255) | No | List of table IDs allowed to be the parent in links using this definition (AllwdPrnts) |
| ALLOWED_CHILDREN_OR_PEERS | No | VARCHAR(255) | No | List of table IDs allowed to be children or peers in links using this definition (AllwdChld) |
| MAX_ITEMS_LINKED | No | NUMERIC(10) | No | Number of items allowed to be linked using this definition (MaxItems) |
| ALLOW_MARK_SUSPECT | No | NUMERIC(1) | No | Indicates if children or peers in links using this definition should be marked as suspect when a suspect event is added to the parent (AllwSuspct) |
Table: TT_LINK_HISTORY
| Comment | Contains a history of changes made to links (LINKHISTRY) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| LINK_HISTORY_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| LINK_ID | No | NUMERIC(10) | Yes | References a parent record in the TT_LINK table (LinkID) |
| HISTORY_ORDER | No | NUMERIC(10) | No | Order events are displayed in the link history (HistOrder) |
| HISTORY_DATE | No | DATETIME | No | Date/time the link was changed (HistDate) |
| CHANGED_FIRST_NAME | No | NVARCHAR(32) | No | First name of the user who made change (FirstName) |
| CHANGED_LAST_NAME | No | NVARCHAR(32) | No | Last name of the user who made change (LastName) |
| HISTORY_INFORMATION | No | NVARCHAR(255) | No | Detailed change description (HistInfo) |
Table: TT_LINK_ITEM
| Comment | Contains information for a single item in a link in the TT_LINK table (LINKITEM) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| LINK_ITEM_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| LINK_ID | No | NUMERIC(10) | Yes | References a parent record in the TT_LINK table (LinkID) |
| ITEM_ORDER | No | NUMERIC(10) | No | Item order in the peer/child list. 0 indicates the parent item in the link. (ItemOrder) |
| ENTITY_TYPE | No | NUMERIC(10) | No | Foreign key to the TT_ENTITY_TYPE table. Table the linked item is associated with. (EntityType) |
| ENTITY_ID | No | NUMERIC(10) | No | Record ID linked to item (EntityID) |
| ITEM_STATUS | No | NUMERIC(5) | No | Reserved for future use (ItemStatus) |
| SUSPECT_STATUS | No | NUMERIC(10) | No | Link is marked as suspect (SuspStat) |
| SUSPECT_BY | No | NUMERIC(10) | No | Record ID of the user who made link suspect (SuspBy) |
| SUSPECT_DATE | No | DATETIME | No | Date/time the link was made suspect (SuspDate) |
| SUSPECT_NOTES | No | NVARCHAR(255) | No | Notes entered by the user when the link was made suspect (SuspNotes) |
| SUSPECT_ENTITY_TYPE | No | NUMERIC(10) | No | Table ID of the item in the link that made this link suspect (SrcType) |
| SUSPECT_ENTITY_ID | No | NUMERIC(10) | No | Record ID of the item in the link that made this link suspect (SrcID) |
| ADDED_DATE | No | DATETIME | No | Date/time the link was added (DateAdded) |
Table: TT_LINK_WORKFLOW
| Comment | Contains the options that describe the workflow behavior for items in the TT_LINK_DEFINITION table (LINKWRKFLW) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| LINK_WORKFLOW_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| LINK_DEFINITION_ID | No | NUMERIC(10) | Yes | References the TT_LINK_DEFINITION table. Identifies link type (LinkDefID) |
| LINK_RELATIONSHIP | No | NUMERIC(5) | No | Indicates the workflow behavior relationship type-1: Parents, 2: Child, 3: Peer (LinkRltn) |
| LINK_OPTION | No | NUMERIC(5) | No | Workflow behavior- 1: Prevent parent from closing if children are open, 2: Prevent child from reopening if parent is closed, 3: Prevent child from closing if parent is open, 4: Prevent parent from reopening if children are closed, 5: Close peers in order, 6: Reopen peers in reverse order (LinkOption) |
Table: TT_LOCATION_TYPE
| Comment | Breaks out the list of Helix ALM location types. This table is not available in Helix ALM. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| ADD_LOCATION_TYPE | Yes | NUMERIC(5) | Yes | Location type unique identifier |
| ADD_LOCATION_DESCRIPTION | No | NVARCHAR(50) | Yes | Description of the method used to add an item (e.g., unknown, Add window, etc.) |
Table: TT_NOTIFY_DEFECT_USER
| Comment | Lists users or customers to notify about defect changes |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users/customers notified when the defect changes. References the TT_USER table. |
| DEFECT_ID | Yes | NUMERIC(10) | Yes | List of defects to notify the user about |
Table: TT_NOTIFY_DOCUMENT_USER
| Comment | Lists users or customers to notify about requirement document changes |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users/customers notified when the document changes. References the TT_USER table. |
| DOCUMENT_ID | Yes | NUMERIC(10) | Yes | List of documents to notify the user about |
Table: TT_NOTIFY_REQUIREMENT_USER
| Comment | Lists users or customers to notify about requirement changes |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users/customers notified when the requirement changes. References the TT_USER table. |
| REQUIREMENT_ID | Yes | NUMERIC(10) | Yes | List of requirements to notify the user about |
Table: TT_NOTIFY_TESTCASE_USER
| Comment | Lists users or customers to notify about test case changes |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table.Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users/customers notified when the test case changes. References the TT_USER table. |
| TESTCASE_ID | Yes | NUMERIC(10) | Yes | List of test cases to notify the user about |
Table: TT_NOTIFY_TESTRUN_USER
| Comment | Lists users or customers to notify about test run changes |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users/customers notified when the test run changes. References the TT_USER table. |
| TESTRUN_ID | Yes | NUMERIC(10) | Yes | List of test runs to notify the user about |
Table: TT_PHONE_TYPE
| Comment | Lists phone number types allowed for Helix ALM users |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| PHONE_TYPE | Yes | NUMERIC(2) | Yes | Phone type unique identifier |
| PHONE_TYPE_DESCRIPTION | No | NVARCHAR(50) | Yes | Phone number type description (e.g., Work, Fax, etc.) |
Table: TT_PROJECT
| Comment | Contains the list of Helix ALM projects stored in the RDBMS database (Helix ALMJECTS) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | Helix ALM project ID. Identifies the parent project for the row. All other project-related tables link to this ID. (ProjectID) |
| TT_PROJECT_NAME | No | NVARCHAR(32) | Yes | Project name. Must be unique in the database. (Helix ALMjName) |
| TT_PROJECT_UUID | No | NVARCHAR(38) | Yes | Universally unique project identifier (Helix ALMjUUID) |
| TT_SERVER_UUID | No | NVARCHAR(38) | No | Universally unique identifier of Helix ALM Server that hosts the project (TTServUUID) |
| TT_PROJECT_VERSION | No | NVARCHAR(10) | No | Project version number (Helix ALMjVers) |
| TT_SERVER_DBID | No | NUMERIC(10) | No | Server database ID (TTServDBID) |
| TT_SERVER_PROJECT_ID | No | NUMERIC(10) | No | Project ID on Helix ALM Server |
| TT_SERVER_PROJECT_NAME | No | NVARCHAR(32) | No | Project name on Helix ALM Server |
Table: TT_REQEVENT_RESULT_STATE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| STATE_ID | Yes | NUMERIC(10) | Yes | Event resulting state |
| REQUIREMENT_EVENT_ID | Yes | NUMERIC(10) | Yes | Requirement event the state is related to |
Table: TT_REQEVENT_SELECT_FIELD
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_REQMENT_EVENT_VAL table. Requirement event and field definition |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Pop-up menu field |
Table: TT_REQEVENT_SELECT_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_REQMENT_EVENT_VAL table. Requirement event and field definition |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer |
Table: TT_REQMENT_EVENT_ATCHMT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| REQUIREMENT_EVENT_ID | No | NUMERIC(10) | No | References the TT_REQUIREMENT_EVENT table. Requirement this event belongs to. (EntityRID) |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type - 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to an entity (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that contains the WYSIWYG inline image (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs to. (SubtypeID) |
Table: TT_REQUIREMENT
| Comment | Contains requirement information. Each table row represents one requirement. (REQMNT) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| REQUIREMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| CREATED_DATE | No | DATETIME | No | Date/time (in GMT) the requirement was added to the database (dateCreate) |
| CREATED_BY | No | NUMERIC(10) | No | User who added the requirement. References a record in the TT_USER table. (idCreateBy) |
| MODIFIED_DATE | No | DATETIME | No | Date/time (in GMT) the requirement was last modified (dateModify) |
| MODIFIED_BY | No | NUMERIC(10) | No | User who last modified the requirement. References a record in the TT_USER table. (idModifyBy) |
| ENTERED_DATE | No | DATETIME | No | Date entered field (in GMT) (dateEnter) |
| ENTERED_BY | No | NUMERIC(10) | No | Entered by field. References a record in the TT_USER table. (idEnterBy) |
| REQUIREMENT_NUMBER | No | NUMERIC(10) | No | Requirement number. Value is zero if a number is not assigned. (ReqNum) |
| TAG_NUMBER | No | NVARCHAR(22) | No | Requirement tag number (Tag) |
| SUMMARY | No | NVARCHAR(255) | No | Summary field (Summary) |
| STATE_ID | No | NUMERIC(10) | No | Current requirement state. References a record in the TT_STATE table. (idStatus) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Requirement type. References a record in the TT_SUBTYPE table. (idType) |
| PRIORITY_ID | No | NUMERIC(10) | No | Importance field. May link to a record in the TT_FIELD_PRIORITY table, but the integrity is not enforced. (idPriority) |
| ADD_LOCATION | No | NUMERIC(5) | No | Method used to add the requirement- 0: unknown, 1: Add Requirement window, 4: Email import, 5: Text file import, 13: Microsoft Word import (AddLocat) |
| VERSION_NUMBER | No | NUMERIC(10) | No | Current requirement version number (Version) |
| REQUIREMENT_DESCRIPTION | No | NVARCHAR(max) | No | Description field (Descrptn) |
| INITIAL_STATE | No | NUMERIC(10) | No | Record ID of the initial state for the requirement |
Table: TT_REQUIREMENT_ATTACHMENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| REQUIREMENT_ID | No | NUMERIC(10) | No | References the TT_REQUIREMENT table. Requirement the attachment is associated with. (EntityRID) |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type - 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to an entity (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in the database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that contains the WYSIWYG inline image (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs to. (SubtypeID) |
Table: TT_REQUIREMENT_CHANGE
| Comment | Contains the original values for fields changed after a requirement version was created. The requirement always stores the current value. (REQCHNGS) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| REQUIREMENT_CHANGE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| REQUIREMENT_VERSION_ID | No | NUMERIC(10) | No | References a record in the TT_REQUIREMENT_VERSION table (ParentID) |
| FIELD_DEFINITION_ID | No | NUMERIC(10) | No | References a record in the TT_FIELD_DEFINITION table. Field (idField) |
| HAS_VALUE | No | NUMERIC(1) | No | Indicates if the OrigValue field represents the original value. If false, the original value was NULL. (HasValue) |
| ORIGINAL_VALUE | No | NVARCHAR(max) | No | Original value for the field stored as a string value (OrigValue) |
Table: TT_REQUIREMENT_EVENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| REQUIREMENT_EVENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_EVENT table (EvtDefID) |
| ORDER_NUMBER | No | NUMERIC(5) | No | Order the requirement event was created relative to other requirement events. Internal counter for a specific requirement. (OrderNum) |
| REQUIREMENT_ID | No | NUMERIC(10) | Yes | References a record in the TT_REQUIREMENT table (ParentID) |
| PARENT_REQUIREMENT_EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_REQUIREMENT_EVENT table. If the event is a response to a multi-user assignment, the field value is the record ID of the parent event. If the event is not a response to a multi-user assignment, the value is -1. (EvtMUParnt) |
| TT_USER_ID | No | NUMERIC(10) | No | References a record in the TT_USER table. If a user entered the event, the field value is the record ID of the user. If the event was generated by Helix ALM, the field contains a record ID of -2. (idUser) |
| EVENT_DATE | No | DATETIME | No | Requirement event date (dateEvent) |
| NOTES | No | NVARCHAR(max) | No | Notes field (Notes) |
| TIME_SPENT | No | NUMERIC(20, 2) | No | If event definition for this event (TT_EVENT table) has the time reporting option selected, field stores the amount of time entered by the user; if event does not record time spent, the value is -1 (TimeSpent) |
| RELEASE_VERSION | No | NVARCHAR(255) | No | Notes field if the event is configured to include release notes information (RelVersion) |
| GENERATED_BY_TYPE | No | NUMERIC(2) | No | Identifies how the event was created - 0: Created by user, 1: Created by multi-user assignment, 2: Created by auto assignment), 3: Created by auto escalation (GenByType) |
| CREATED_BY | No | NUMERIC(10) | No | Reserved for future use (CreatorID) |
| DEFAULT_ASSIGN_EFFECT | No | NUMERIC(2) | No | Assignment for the event when it was run - 1: Event results in new assignment, 2: Event has no effect on assignment, 3: Event clears assignment. Intended to preserve history if the event definition is modified (DefAsgEff) |
| WORKFLOW_OVERRIDE | No | NUMERIC(1) | No | Indicates if the event is a result of a workflow override (OvrWF) |
| WORKFLOW_OVERRIDE_USER_ID | No | NUMERIC(10) | No | References the TT_USER table. If the event is a result of a workflow override, the field value is the record ID of use. Otherwise, the value is 0. (OvrWFUsrID) |
| ITEM_MARK_SUSPECT | No | NUMERIC(1) | No | Indicates if the user selected the option to mark dependent items as suspect (SspLnkItms) |
| REQUIREMENT_VERSION | No | NUMERIC(10) | No | Version number of the requirement that was current when the event was entered (Version) |
Table: TT_REQUIREMENT_EVENT_ASGN_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | List of users requirements are assigned to |
| REQUIREMENT_EVENT_ID | Yes | NUMERIC(10) | Yes | List of requirements assigned to the user |
Table: TT_REQUIREMENT_LOG
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| REQUIREMENT_LOG_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| REQUIREMENT_ID | No | NUMERIC(10) | No | References a record in the TT_REQUIREMENT table (ParentID) |
| TT_USER_ID | No | NUMERIC(10) | No | User who made change. References a record in the TT_USER table. (idUser) |
| LOG_DATE | No | DATETIME | No | Date/time the change occurred (dateLog) |
| NOTES | No | NVARCHAR(4000) | No | Change description (Notes) |
Table: TT_REQUIREMENT_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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_REQUIREMENT_VALUE table. Requirement and field definition |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Custom pop-up menu field. |
Table: TT_REQUIREMENT_SELECT_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_REQUIREMENT_EVENT_VALUE table. Requirement and field definition. |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer. |
Table: TT_REQUIREMENT_VERSION
| Comment | Contains requirement version information. Each table row represents one requirement version. (REQVRSN) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| REQUIREMENT_VERSION_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| REQUIREMENT_ID | No | NUMERIC(10) | Yes | References a record in the TT_REQUIREMENT table (idReqmnt) |
| CREATED_DATE | No | DATETIME | No | Date/time (in GMT) the requirement version was added to the database (dateCreate) |
| CREATED_BY | No | NUMERIC(10) | No | User who created the requirement version. References a record ID in TT_USER table. (idCreateBy) |
| VERSION_NUMBER | No | NUMERIC(10) | No | Requirement version number (Version) |
Table: TT_SCM_CHANGELIST_DEFECT
| Comment | Contains source control changelist information for defects |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_CHANGELIST_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| DEFECT_ID | No | NUMERIC(10) | Yes | DEFECT_ID a changelist is associated with from the TT_DEFECT table |
| SCM_CHANGELIST_ID | No | NUMERIC(10) | Yes | Changelist ID stored in the source control application |
| COMMITTED | No | NUMERIC(1) | Yes | Indicates if the changelist is committed |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured source control provider |
| ATTACH_DATE | No | DATETIME | No | Date/time the changelist was committed to Helix ALM from the source control provider |
| AUTHOR_ID | No | NUMERIC(10) | No | Record ID for author who changed file for commit. Uses Helix ALM user ID if can be determined. Loose relationship only. |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if changelist is in pending state |
| MAINLINE_NAME | No | NVARCHAR(max) | No | Mainline branch name |
| CHANGELIST_NAME | No | NVARCHAR(max) | No | Changelist name |
| BRANCH_NAME | No | NVARCHAR(max) | No | Branch name the change was committed to |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
Table: TT_SCM_CHANGELIST_DOCUMENT
| Comment | Contains source control changelist information for requirement documents |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_CHANGELIST_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| DOCUMENT_ID | No | NUMERIC(10) | Yes | DOCUMENT_ID a changelist is associated with from the TT_DOCUMENT table |
| SCM_CHANGELIST_ID | No | NUMERIC(10) | Yes | Changelist ID stored in the source control application |
| COMMITTED | No | NUMERIC(1) | Yes | Indicates if the changelist is committed |
| MAINLINE_NAME | No | NVARCHAR(max) | No | Mainline branch name |
| CHANGELIST_NAME | No | NVARCHAR(max) | No | Changelist name |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured source control provider |
| ATTACH_DATE | No | DATETIME | No | Date/time the changelist was committed to Helix ALM from the source control provider |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit |
| AUTHOR_ID | No | NUMERIC(10) | No | Record ID for author who changed file for commit. Uses Helix ALM user ID if can be determined. Loose relationship only. |
| BRANCH_NAME | No | NVARCHAR(max) | No | Branch name the change was committed to |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if changelist is in pending state |
Table: TT_SCM_CHANGELIST_REQUIREMENT
| Comment | Contains source control changelist information for requirements |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_CHANGELIST_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| REQUIREMENT_ID | No | NUMERIC(10) | Yes | REQUIREMENT_ID a changelist is associated with from the TT_REQUIREMENT table |
| SCM_CHANGELIST_ID | No | NUMERIC(10) | Yes | Changelist ID stored in the SCM product |
| COMMITTED | No | NUMERIC(1) | Yes | Indicates if the changelist is committed |
| MAINLINE_NAME | No | NVARCHAR(max) | No | Mainline branch name |
| CHANGELIST_NAME | No | NVARCHAR(max) | No | Changelist name |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured source control provider |
| ATTACH_DATE | No | DATETIME | No | Date/time the changelist was committed to Helix ALM from the source control provider |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit |
| AUTHOR_ID | No | NUMERIC(10) | No | Record ID for author who changed file for commit. Uses Helix ALM user ID if can be determined. Loose relationship only. |
| BRANCH_NAME | No | NVARCHAR(max) | No | Branch name the change was committed to |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if changelist is in pending state |
Table: TT_SCM_CHANGELIST_TESTCASE
| Comment | Contains source control changelist information for test cases |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_CHANGELIST_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TESTCASE_ID | No | NUMERIC(10) | Yes | TESTCASE_ID a changelist is associated with from the TT_TESTCASE table |
| SCM_CHANGELIST_ID | No | NUMERIC(10) | Yes | Changelist ID stored in the SCM product |
| COMMITTED | No | NUMERIC(1) | Yes | Indicates if the changelist is committed |
| MAINLINE_NAME | No | NVARCHAR(max) | No | Mainline branch name |
| CHANGELIST_NAME | No | NVARCHAR(max) | No | Changelist name |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured source control provider |
| ATTACH_DATE | No | DATETIME | No | Date/time the changelist was committed to Helix ALM from the source control provider |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit |
| AUTHOR_ID | No | NUMERIC(10) | No | Record ID for author who changed file for commit. Uses Helix ALM user ID if can be determined. Loose relationship only. |
| BRANCH_NAME | No | NVARCHAR(max) | No | Branch name the change was committed to |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if changelist is in pending state |
Table: TT_SCM_CHANGELIST_TESTRUN
| Comment | Contains source control changelist information for test runs |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_CHANGELIST_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TESTRUN_ID | No | NUMERIC(10) | Yes | TESTRUN_ID a changelist is associated with from the TT_TESTRUN table |
| SCM_CHANGELIST_ID | No | NUMERIC(10) | Yes | Changelist ID stored in the SCM product |
| COMMITTED | No | NUMERIC(1) | Yes | Indicates if the changelist is committed |
| MAINLINE_NAME | No | NVARCHAR(max) | No | Mainline branch name |
| CHANGELIST_NAME | No | NVARCHAR(max) | No | Changelist name |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured source control provider |
| ATTACH_DATE | No | DATETIME | No | Date/time the changelist was committed to Helix ALM from the source control provider |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit |
| AUTHOR_ID | No | NUMERIC(10) | No | Record ID for author who changed file for commit. Uses Helix ALM user ID if can be determined. Loose relationship only. |
| BRANCH_NAME | No | NVARCHAR(max) | No | Branch name the change was committed to |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if changelist is in pending state |
Table: TT_SCM_FILE_DEFECT
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_FILE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| DEFECT_ID | No | NUMERIC(10) | Yes | References a DEFECT_ID in the TT_DEFECT table |
| SCM_MAINLINE_NAME | No | NVARCHAR(128) | No | Surround SCM parent mainline branch name. Not explicitly related to the SCM table by foreign key as the mainline can only be inferred. References SCM_MAINLINE.MAINLINE_NAME. (MainlineID) |
| SCM_BRANCH_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch name. Not explicitly related to the SCM table by foreign key as the branch can only be inferred. References SCM_BRANCH.BRANCH_NAME. |
| SCM_BRANCH_REPO_PATH | No | NVARCHAR(4000) | No | Relates to the SCM_BRANCH_REPO_PATH.REPO_PATH by name. Not related by foreign key as the relationship can only be inferred. |
| SCM_BRANCH_FILE_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch file name. Not explicitly related to the SCM table by foreign key as the branch file can only be inferred. References SCM_BRANCH_FILE.FILE_NAME. |
| FILE_NAME | No | NVARCHAR(4000) | No | File name in the source control application |
| FILE_VERSION | No | NVARCHAR(max) | No | Version number of the fix in the source control application |
| FIXED_DATE | No | DATETIME | No | Date/time the fix was made |
| TT_SCM_CHANGELIST_ID | No | NUMERIC(10) | No | Changelist record ID from the SCMCHGLST table |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured source control provider |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
| CHANGE_TYPE | No | NUMERIC(10) | No | Type of file change associated with attachment - 0: Unknown, 1: File added, 2: File edited, 3: File removed |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if file change is in pending state |
Table: TT_SCM_FILE_DOCUMENT
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_FILE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| DOCUMENT_ID | No | NUMERIC(10) | Yes | References DOCUMENT_ID in the TT_DOCUMENT table. |
| SCM_MAINLINE_NAME | No | NVARCHAR(128) | No | Surround SCM parent mainline branch name. Not explicitly related to the SCM table by foreign key as the mainline can only be inferred. References SCM_MAINLINE.MAINLINE_NAME. (MainlineID) |
| SCM_BRANCH_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch name. Not explicitly related to the SCM table by foreign key as the branch can only be inferred. References SCM_BRANCH.BRANCH_NAME. |
| SCM_BRANCH_REPO_PATH | No | NVARCHAR(4000) | No | References the SCM_BRANCH_REPO_PATH.REPO_PATH by name. Not related by foreign key as the relationship can only be inferred. |
| SCM_BRANCH_FILE_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch file name. Not explicitly related to the SCM table by foreign key as the branch file can only be inferred. References SCM_BRANCH_FILE.FILE_NAME. |
| FILE_NAME | No | NVARCHAR(4000) | No | File name in the source control application |
| FILE_VERSION | No | NVARCHAR(max) | No | Version number of the fix in the source control application |
| FIXED_DATE | No | DATETIME | No | Date/time the fix was made |
| TT_SCM_CHANGELIST_ID | No | NUMERIC(10) | No | Changelist record ID from the SCMCHGLST table |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured source control provider |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit. Uses Helix ALM user ID if can be determined. |
| CHANGE_TYPE | No | NUMERIC(10) | No | Type of file change associated with attachment - 0: Unknown, 1: File added, 2: File edited, 3: File removed |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if file change is in pending state |
Table: TT_SCM_FILE_REQUIREMENT
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_FILE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| REQUIREMENT_ID | No | NUMERIC(10) | Yes | References REQUIREMENT_ID in the TT_REQUIREMENT table |
| SCM_MAINLINE_NAME | No | NVARCHAR(128) | No | Surround SCM parent mainline branch name. Not explicitly related to the SCM table by foreign key as the mainline can only be inferred. References SCM_MAINLINE.MAINLINE_NAME. (MainlineID) |
| SCM_BRANCH_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch name. Not explicitly related to the SCM table by foreign key as the branch can only be inferred. References SCM_BRANCH.BRANCH_NAME. |
| SCM_BRANCH_REPO_PATH | No | NVARCHAR(4000) | No | References the SCM_BRANCH_REPO_PATH.REPO_PATH by name. Is not related by foreign key as the relationship can only be inferred. |
| SCM_BRANCH_FILE_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch file name. Not explicitly related to the SCM table by foreign key as the branch file can only be inferred. References SCM_BRANCH_FILE.FILE_NAME. |
| FILE_NAME | No | NVARCHAR(4000) | No | File name in the source control application |
| FILE_VERSION | No | NVARCHAR(max) | No | Version number of the fix in the source control application |
| FIXED_DATE | No | DATETIME | No | Date/time the fix was made |
| TT_SCM_CHANGELIST_ID | No | NUMERIC(10) | No | Changelist record ID from the SCMCHGLST table |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured SCM provider |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit. Uses Helix ALM user ID if can be determined. |
| CHANGE_TYPE | No | NUMERIC(10) | No | Type of file change associated with attachment - 0: Unknown, 1: File added, 2: File edited, 3: File removed |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if file change is in pending state |
Table: TT_SCM_FILE_TESTCASE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_FILE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TESTCASE_ID | No | NUMERIC(10) | Yes | References TESTCASE_ID in the TT_TESTCASE table |
| SCM_MAINLINE_NAME | No | NVARCHAR(128) | No | Surround SCM parent mainline branch name. Not explicitly related to the SCM table by foreign key as the mainline can only be inferred. References SCM_MAINLINE.MAINLINE_NAME. (MainlineID) |
| SCM_BRANCH_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch name. Not explicitly related to the SCM table by foreign key as the branch can only be inferred. References SCM_BRANCH.BRANCH_NAME. |
| SCM_BRANCH_REPO_PATH | No | NVARCHAR(4000) | No | References the SCM_BRANCH_REPO_PATH.REPO_PATH by name. Not related by foreign key as the relationship can only be inferred. |
| SCM_BRANCH_FILE_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch file name. Not explicitly related to the SCM table by foreign key as the branch file can only be inferred. Relates to SCM_BRANCH_FILE.FILE_NAME. |
| FILE_NAME | No | NVARCHAR(4000) | No | File name in the source control application |
| FILE_VERSION | No | NVARCHAR(max) | No | Version number of the fix in the source control application |
| FIXED_DATE | No | DATETIME | No | Date/time the fix was made |
| TT_SCM_CHANGELIST_ID | No | NUMERIC(10) | No | Changelist record ID from the SCMCHGLST table |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured SCM provider |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit. Uses Helix ALM user ID if can be determined. |
| CHANGE_TYPE | No | NUMERIC(10) | No | Type of file change associated with attachment - 0: Unknown, 1: File added, 2: File edited, 3: File removed |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if file change is in pending state |
Table: TT_SCM_FILE_TESTRUN
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_SCM_FILE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TESTRUN_ID | No | NUMERIC(10) | Yes | References TESTRUN_ID in the TT_TESTRUN table |
| SCM_MAINLINE_NAME | No | NVARCHAR(128) | No | Surround SCM parent mainline branch name. Not explicitly related to the SCM table by foreign key as the mainline can only be inferred. References SCM_MAINLINE.MAINLINE_NAME. (MainlineID) |
| SCM_BRANCH_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch name. Not explicitly related to the SCM table by foreign key as the branch can only be inferred. References SCM_BRANCH.BRANCH_NAME. |
| SCM_BRANCH_REPO_PATH | No | NVARCHAR(4000) | No | References the SCM_BRANCH_REPO_PATH.REPO_PATH by name. Not related by foreign key as the relationship can only be inferred. |
| SCM_BRANCH_FILE_NAME | No | NVARCHAR(255) | No | Surround SCM parent branch file name. Not explicitly related to the SCM table by foreign key as the branch file can only be inferred. References SCM_BRANCH_FILE.FILE_NAME. |
| FILE_NAME | No | NVARCHAR(4000) | No | File name in the source control application |
| FILE_VERSION | No | NVARCHAR(max) | No | Version number of the fix in the source control application |
| FIXED_DATE | No | DATETIME | No | Date/time the fix was made |
| TT_SCM_CHANGELIST_ID | No | NUMERIC(10) | No | Changelist record ID from the SCMCHGLST table |
| TT_PROVIDER_ID | No | NUMERIC(10) | No | Provider ID from TT_EXTERNAL_PROVIDER table if file was submitted by configured source control provider |
| AUTHOR | No | NVARCHAR(max) | No | Author who changed file for commit. Uses Helix ALM user ID if can be determined. |
| CHANGE_TYPE | No | NUMERIC(10) | No | Type of file change associated with attachment - 0: Unknown, 1: File added, 2: File edited, 3: File removed |
| HYPER_LINK | No | NVARCHAR(max) | No | Full file URL to view the file generated on XML import if provider is not available |
| HYPER_LINK_DETAIL | No | NVARCHAR(max) | No | JSON submitted by provider if hook includes name/value pairs for field code replacement |
| IS_PENDING | No | NUMERIC(1) | No | Indicates if file change is in pending state |
Table: TT_SNAPSHOT_REQUIREMENT_TREE
| Comment | Contains the requirement relationship tree for a snapshot of the document (SNPSTTRE) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| SNAPSHOT_TREE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| SNAPSHOT_ID | Yes | NUMERIC(10) | Yes | References a record in the TT_DOCUMENT_SNAPSHOT table (idSnapshot) |
| PARENT_SNAPSHOT_TREE_ID | No | NUMERIC(10) | No | References a record in the TT_SNAPSHOT_REQUIREMENT_TREE table. Contains the record of the parent node in the tree. If the node is at the top level, PARENT_SNAPSHOT_TREE_ID contains 0. (ParentID) |
| REQUIREMENT_ID | No | NUMERIC(10) | No | References a record in the TT_REQUIREMENT table (idReqmnt) |
| REQUIREMENT_VERSION | No | NUMERIC(10) | No | Version number of the requirement that was current when the snapshot was created (ReqVersion) |
| SIBLING_ORDER | No | NUMERIC(10) | No | Order of this node relative to its siblings in the parent node (SibOrder) |
Table: TT_STATE
| Comment | Contains information about states that an entity can transition to (STATES) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| STATE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| ENTITY_TYPE | No | NUMERIC(10) | No | Foreign key to the TT_ENTITY_TYPE table. Table the state is linked to (EntityType) |
| STATE_NAME | No | NVARCHAR(32) | No | State name (Name) |
| STATE_DESCRIPTION | No | NVARCHAR(255) | No | State description (StateDesc) |
| ACTIVE | No | NUMERIC(1) | No | Indicates if the state is active in the workflow (Active) |
| STATE_ORDER | No | NUMERIC(10) | No | Order the state is displayed in the workflow configuration dialog boxes (StateOrder) |
| OPEN_CLOSE_ATTRIBUTE | No | NUMERIC(2) | No | Open or closed - 1: open, 2: closed (Attrib) |
| ONLY_ASSIGN | No | NUMERIC(1) | No | Indicates if only assigned users can enter events (OnlyAssign) |
| MULTI_RULE | No | NUMERIC(2) | No | Multi-user assignment rule that determines when a state is complete and the entity can move to the new state - 1: use the first response, 2: wait for all responses - use highest priority response, 3: wait for highest priority response (MultiRule) |
| CAN_GENERATE_TEST_RUN | No | NUMERIC(1) | No | Indicates if the state can generate test runs. Only applies to test cases. (CnGenTstRs) |
| COMPLETION_STATUS | No | NUMERIC(5) | No | Test run results (passed/failed/other). Only applies to test runs. (ComplStat) |
| LOCKED | No | NUMERIC(2) | No | Indicates if the requirement or requirement document is locked in this state (Locked) |
| CAN_GENERATE_TEST_CASE | No | NUMERIC(1) | No | Indicates if the state can generate test cases. Only applies to requirements. (CnGenTstCs) |
Table: TT_STEPDATA
| Comment | Contains the step or expected result in the STEP_DATA field. The results field is only populated when the record is a step. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| STEPDATA_ID | Yes | NUMERIC(10) | Yes | TT_STEPDATA table primary key value. |
| ACTUAL_RESULTS | No | NVARCHAR(max) | No | Text data containing the actual results |
| IS_TESTCASE_NOTE | No | NUMERIC(1) | No | Indicates if the row is a test case note |
| STEP_ORDER | No | NUMERIC(10) | No | Step order list |
| STAMP_TIME | No | DATETIME | No | Stamp date/time |
| STEP_DATA | No | NVARCHAR(max) | No | Step data list |
| STEP_RESULTS | No | NUMERIC(10) | No | Step results |
| STEP_TYPE | No | NUMERIC(10) | No | Step type |
| STAMP_USER_ID | No | NUMERIC(10) | No | User who entered the stamp |
| TESTRUN_ID | No | NUMERIC(10) | No | References the TT_TESTRUN table |
Table: TT_SUBTYPE
| Comment | Contains requirement type information. Each table row represents one type value. (SUBTYPE) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| SUBTYPE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| ENTITY_TYPE | No | NUMERIC(10) | Yes | References the TT_ENTITY_TYPE table. Table the type is linked to. Types are only supported for requirements. (EntityType) |
| DISPLAY_ORDER | No | NUMERIC(3) | Yes | Pop-up menu item order relative to other items (DispOrder) |
| SUBTYPE_NAME | No | NVARCHAR(63) | Yes | Type name (Name) |
| SUBTYPE_DESCRIPTION | No | NVARCHAR(255) | No | Type description (StDesc) |
| SUBTYPE_ICON | No | IMAGE | No | Type icon (StIcon) |
| SUBTYPE_ICON_NAME | No | NVARCHAR(255) | No | Type icon file name (StIconNm) |
| SUBTYPE_PREFIX | No | NVARCHAR(5) | No | Type tag prefix (StPrefix) |
| SUBTYPE_SUFFIX | No | NVARCHAR(5) | No | Type tag suffix (StSuffix) |
| SUM_FORMAT_FONT | No | NUMERIC(2) | No | Reserved for future use (SumFrmtFnt) |
| SUM_FONT_SIZE | No | NUMERIC(5) | No | Reserved for future use (SumFntSz) |
| SUM_FONT_WEIGHT | No | NUMERIC(2) | No | Reserved for future use (SumFntWt) |
| SUB_FONT_COLOR | No | NUMERIC(10) | No | Reserved for future use (SumFntClr) |
| DETAIL_FORMAT_FONT | No | NUMERIC(2) | No | Reserved for future use (DtlFrmtFnt) |
| DETAIL_FONT_SIZE | No | NUMERIC(5) | No | Reserved for future use (DtlFntSz) |
| DETAIL_FONT_WEIGHT | No | NUMERIC(2) | No | Reserved for future use (DtlFntWt) |
| DETAIL_FONT_COLOR | No | NUMERIC(10) | No | Reserved for future use (DtlFntClr) |
| ACTIVE | No | NUMERIC(1) | No | Indicates if the type is active. Can be selected for new items. (Active) |
Table: TT_SYSTEM_CONFIG
| Comment | Contains test configuration information. Each table row represents one system test configuration. (SYSCONF) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| CONFIG_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| CONFIG_TYPE | No | NUMERIC(5) | No | System configuration type - 1: User Test Configuration, 2: Standard Test Configuration (ConfType) |
| SYSTEM_NAME | No | NVARCHAR(32) | No | Name field (SysName) |
| SYSTEM_LOCATION | No | NVARCHAR(255) | No | Reserved for future use (Location) |
| COMPUTER_MODEL | No | NVARCHAR(255) | No | Computer model field (CompModel) |
| COMPUTER_BRAND | No | NVARCHAR(255) | No | Computer brand field (CompBrand) |
| CPU_TYPE | No | NVARCHAR(32) | No | CPU type field (CPUType) |
| CPU_SPEED | No | NVARCHAR(32) | No | CPU speed field (in MHz) (CPUSpeed) |
| HARD_DISK_TYPE | No | NVARCHAR(255) | No | Hard disk type field (HDiskTypt) |
| HARD_DISK_SIZE | No | NVARCHAR(255) | No | Hard disk size field (in MB) (HDiskSize) |
| RAM_SIZE | No | NVARCHAR(32) | No | RAM field (in MB) (RAMSize) |
| ROM_SIZE | No | NVARCHAR(32) | No | ROM field (in MB) (ROMSize) |
| OS_NAME | No | NVARCHAR(63) | No | Operating system field (OSName) |
| OS_VERSION | No | NVARCHAR(32) | No | Operating system version field (OSVersion) |
| VIDEO_NAME | No | NVARCHAR(63) | No | Video controller field (VideoName) |
| HAS_MULTIPLE_MONITOR | No | NUMERIC(1) | No | Has multiple monitors field (HasMultMon) |
| HAS_CDROM | No | NUMERIC(1) | No | Has CD-ROM field (HasCDROM) |
| CDROM_MODEL | No | NVARCHAR(63) | No | CD-ROM model field (CDROMModel) |
| HAS_SCANNER | No | NUMERIC(1) | No | Has scanner field (HasScanr) |
| SCANNER_MODEL | No | NVARCHAR(63) | No | Scanner model field (ScanrModel) |
| HAS_MODEM | No | NUMERIC(1) | No | Has modem field (HasModem) |
| MODEM_MODEL | No | NVARCHAR(63) | No | Modem model field (ModemModel) |
| HAS_PRINTER | No | NUMERIC(1) | No | Has printer field (HasPrint) |
| PRINTER_MODEL | No | NVARCHAR(63) | No | Printer model field (PrintModel) |
| OTHER_HARDWARE_SOFTWARE | No | NVARCHAR(255) | No | Other hardware and software field (OtherHW) |
Table: TT_SYSTEM_CONFIG_TYPE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| CONFIG_TYPE | Yes | NUMERIC(5) | Yes | System configuration type unique identifier |
| CONFIG_DESCRIPTION | No | NVARCHAR(50) | No | System configuration description |
Table: TT_TCEVENT_RESULT_STATE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| STATE_ID | Yes | NUMERIC(10) | Yes | Event resulting state |
| TESTCASE_EVENT_ID | Yes | NUMERIC(10) | Yes | Test case event the state relates to |
Table: TT_TCEVENT_SELECT_FIELD
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_TESTCASE_EVENT_VAL table. Requirement event and field definition |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Pop-up menu field |
Table: TT_TCEVENT_SELECT_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_TESTCASE_EVENT_VAL table. Requirement event and field definition |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer |
Table: TT_TESTCASE
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TESTCASE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| CREATED_DATE | No | DATETIME | No | Date/time (in GMT) test case was added to the database (dateCreate) |
| CREATED_BY | No | NUMERIC(10) | No | User who added the test case. References a record in the TT_USER table. (idCreateBy) |
| MODIFIED_DATE | No | DATETIME | No | Date/time (in GMT) test case was last modified (dateModify) |
| MODIFIED_BY | No | NUMERIC(10) | No | User who last modified the test case. References a record in the TT_USER table. (idModifyBy) |
| TESTCASE_NUMBER | No | NUMERIC(10) | No | Test case number. Value is zero if a number is not assigned. (TstCaseNum) |
| SUMMARY | No | NVARCHAR(255) | No | Summary field (Summary) |
| TESTOBJECT_TYPE_ID | No | NUMERIC(10) | No | Test object type field. References a record in the TT_FIELD_TESTOBJECT_TYPE table. (idType) |
| AUTOMATED_TEST | No | NUMERIC(1) | No | Indicates if the test case is an automated test (isAutoTest) |
| ESTIMATED_EXECUTION_TIME | No | NUMERIC(10) | No | Estimated time to execute the test case (estTime) |
| TESTCASE_STEPS | No | NVARCHAR(max) | No | Test case steps (Steps) |
| ADDED_FROM | No | NUMERIC(6) | No | Method used to add test case- 0: unknown, 1: Add Test Case window, 5: Text file import, 6: Helix ALM user duplicated a test case (AddedFrom) |
| SAVE_GRIDMODE | No | NUMERIC(1) | No | Indicates to save test runs in grid mode or plain text (SaveGrid) (deprecated as of version 2011.0) |
| STATE_ID | No | NUMERIC(10) | No | Record ID of the current state for the test case (Status) |
| SAVE_MODE | No | NUMERIC(10) | No | View used (grid or text) for test runs generated from this test case. Deprecates SAVE_GRIDMODE. |
| INITIAL_STATE | No | NUMERIC(10) | No | Record ID of the initial state for the test case |
Table: TT_TESTCASE_ATTACHMENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTCASE_ID | No | NUMERIC(10) | No | Foreign key to the TT_TESTCASE table. Indicates the test case the file is attached to. (EntityRID) |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type- 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to an entity (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in the database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that contains the WYSIWYG inline image (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs. (SubtypeID) |
Table: TT_TESTCASE_ATTACHMENT_INFO
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACH_INFO_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| ATTACHMENT_TYPE | No | NUMERIC(10) | Yes | Attachment type - 0: Regular attachment, 1: Script, 2: Run Result (AttachType) |
| ATTACHMENT_ID | No | NUMERIC(10) | Yes | Record ID in the TT_TESTCASE_ATTACHMENT table (AttachID) |
| ATTACH_TABLE_TYPE | No | NUMERIC(2) | Yes | Attachment table type (tableID_Attachments or tableID_SCCFiles) (Type) |
| OWNER_TYPE | No | NUMERIC(10) | Yes | Entity type the attachment belongs to (OwnerType) |
| OWNER_ID | No | NUMERIC(10) | Yes | Entity RID the attachment belongs to (OwnerID) |
| SCRIPT_ORDER | No | NUMERIC(10) | No | Script order displayed on the Scripts tab and executed relative to other scripts. Only valid if the attachment type is Script. (ScrptOrder) |
| SCRIPT_STATUS | No | NVARCHAR(255) | No | Script status. Only valid if the attachment type is Script. (ScrptStat) |
Table: TT_TESTCASE_EVENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TESTCASE_EVENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_EVENT table (EvtDefID) |
| ORDER_NUMBER | No | NUMERIC(5) | No | Order the test case event was created relative to other test case events. Internal counter for a specific test case. (OrderNum) |
| TESTCASE_ID | No | NUMERIC(10) | Yes | References a record in the TT_TESTCASE table (ParentID) |
| PARENT_TESTCASE_EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_TESTCASE_EVENT table. If the event is a response to a multi-user assignment, the field value is the record ID of the parent event. If the event is not a response to a multi-user assignment, the value is -1. (EvtMUParnt) |
| TT_USER_ID | No | NUMERIC(10) | No | References a record in the TT_USER table. If a user entered the event, the field value is the record ID of the user. If the event was generated by Helix ALM, the field contains a record ID of -2 (idUser) |
| EVENT_DATE | No | DATETIME | No | Test case event date (dateEvent) |
| NOTES | No | NVARCHAR(max) | No | Notes field (Notes) |
| TIME_SPENT | No | NUMERIC(20, 2) | No | If event definition for this event (TT_EVENT table) has the time reporting option selected, stores the amount of time entered by the user. If the event does not record time spent, the value is -1 (TimeSpent) |
| RELEASE_VERSION | No | NVARCHAR(255) | No | Notes field if the event is configured to include release notes information (RelVersion) |
| GENERATED_BY_TYPE | No | NUMERIC(2) | No | How the event was created - 0: Created by user, 1: Created by multi-user assignment, 2: Created by auto assignment, 3: Created by auto escalation (GenByType) |
| CREATED_BY | No | NUMERIC(10) | No | Reserved for future use (CreatorID) |
| DEFAULT_ASSIGN_EFFECT | No | NUMERIC(2) | No | Assignment for the event when it was run - 1: Event results in new assignment, 2: Event has no effect on assignment, 3: Event clears assignment. Intended to preserve history if the event definition is modified (DefAsgEff) |
| WORKFLOW_OVERRIDE | No | NUMERIC(1) | No | Indicates if the event is a result of a workflow override (OvrWF) |
| WORKFLOW_OVERRIDE_USER_ID | No | NUMERIC(10) | No | References the TT_USER table. If the event is a result of a workflow override, the field value is the record ID of use. Otherwise, the value is 0. (OvrWFUsrID) |
| ITEM_MARK_SUSPECT | No | NUMERIC(1) | No | Indicates if the user selected the option to mark dependent items as suspect (SspLnkItms) |
Table: TT_TESTCASE_EVENT_ASGN_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer. |
| TESTCASE_EVENT_ID | Yes | NUMERIC(10) | Yes | References the TT_TESTCASE_EVENT table. Test case event the user is assigned to. |
Table: TT_TESTCASE_EVENT_ATCHMT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTCASE_EVENT_ID | No | NUMERIC(10) | No | References the TT_TESTCASE_EVENT table. Test case event the file is attached to. (EntityRID) |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type - 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to an entity (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that contains the WYSIWYG inline image (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs. (SubtypeID) |
Table: TT_TESTCASE_LOG
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TESTCASE_LOG_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TT_USER_ID | No | NUMERIC(10) | No | User who made change. References a record in the TT_USER table. (idUser) |
| TESTCASE_ID | No | NUMERIC(10) | No | References a record in the TT_TESTCASE table (ParentID) |
| LOG_DATE | No | DATETIME | No | Date/time the change occurred (dateLog) |
| NOTES | No | NVARCHAR(4000) | No | Change description (Notes) |
Table: TT_TESTCASE_SELECT_FIELD
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_TESTCASE_VALUE table. Test case and field definition. |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Custom pop-up menu field. |
Table: TT_TESTCASE_SELECT_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_TESTCASE_VALUE table. Test case and field definition. |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer. |
Table: TT_TESTRUN
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TESTRUN_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| CREATED_DATE | No | DATETIME | No | Date/time (in GMT) test run was added to the database (dateCreate) |
| CREATED_BY | No | NUMERIC(10) | No | User who added the test run. References a record in the TT_USER table. (idCreateBy) |
| MODIFIED_DATE | No | DATETIME | No | Date/time (in GMT) test run was last modified (dateModify) |
| MODIFIED_BY | No | NUMERIC(10) | No | User who last modified the test run. References a record in the TT_USER table. (idModifyBy) |
| TESTCASE_ID | No | NUMERIC(10) | No | Test case record. Foreign key to the TT_TESTCASE table. (TstCaseRID) |
| SUMMARY | No | NVARCHAR(255) | No | Summary field (Summary) |
| TESTOBJECT_TYPE_ID | No | NUMERIC(10) | No | Test object type field. References a record in the TT_FIELD_TESTOBJECT_TYPE table. (idType) |
| AUTOMATED_TEST | No | NUMERIC(1) | No | Indicates if the test run is an automated test (isAutoTest) |
| ESTIMATED_TIME | No | NUMERIC(10) | No | Estimated time of to execute the test run (EstTime) |
| STEPS | No | NVARCHAR(max) | No | Test case steps (Steps) |
| ADDED_FROM | No | NUMERIC(6) | No | Method used to add the test run - 0: unknown, 1: Add Test Run window, 5: Text file import, 6: Helix ALM user duplicated a test run (AddedFrom) |
| TESTRUN_NUMBER | No | NUMERIC(10) | No | Test run number (auto generated) (TstRunNum) |
| TESTRUNSET_ID | No | NUMERIC(10) | No | Test run set field. References a record in the TT_TESTRUN_SET table. (idTRSet) |
| VIEW_GRID | No | NUMERIC(1) | No | Indicates to view test runs in grid or text mode (ViewGrid) |
| PROBLEM_STATEMENT | No | NVARCHAR(max) | No | Test run problem statement (optional) (PrbState) |
| STATE_ID | No | NUMERIC(10) | No | Record ID of the current state for the test run (Status) |
| VIEW_MODE | No | NUMERIC(10) | No | How the test run was generated. Based on the test case SAVE_MODE value |
| INITIAL_STATE | No | NUMERIC(10) | No | Record ID of the initial state for the test run |
Table: TT_TESTRUN_ATTACHMENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTRUN_ID | No | NUMERIC(10) | No | Foreign key to the TT_TESTRUN table. Test run the attachment is associated with. (EntityRID) |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type- 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to an entity (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in the database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that contains the WYSIWYG inline image (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added inline to a WYSIWYG field (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added inline to a WYSIWYG field (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs to. (SubtypeID) |
Table: TT_TESTRUN_ATTACHMENT_INFO
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACH_INFO_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| ATTACHMENT_TYPE | No | NUMERIC(10) | Yes | Attachment type- 0: Regular attachment, 1: Script, 2: Run Result (AttachType) |
| ATTACHMENT_ID | No | NUMERIC(10) | Yes | Record ID in the TT_TESTRUN_ATTACHMENT table (AttachID) |
| ATTACH_TABLE_TYPE | No | NUMERIC(2) | Yes | Attachment table type (tableID_Attachments or tableID_SCCFiles) (Type) |
| OWNER_TYPE | No | NUMERIC(10) | Yes | Entity type the attachment belongs to (OwnerType) |
| OWNER_ID | No | NUMERIC(10) | Yes | Entity RID the attachment belongs to (OwnerID) |
| SCRIPT_ORDER | No | NUMERIC(10) | No | Script order displayed on the Scripts tab and executed relative to other scripts. Only valid if the attachment type is Script. (ScrptOrder) |
| SCRIPT_STATUS | No | NVARCHAR(255) | No | Script status. Only valid if the attachment type is Script. (ScrptStat) |
Table: TT_TESTRUN_EVENT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TESTRUN_EVENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_EVENT table (EvtDefID) |
| ORDER_NUMBER | No | NUMERIC(5) | No | Order the test run event was created relative to other test run events. Internal counter for a specific test run. (OrderNum) |
| TESTRUN_ID | No | NUMERIC(10) | Yes | References a record in the TT_TESTRUN table (ParentID) |
| PARENT_TESTRUN_EVENT_ID | No | NUMERIC(10) | No | References a record in the TT_TESTRUN_EVENT table. If the event is a response to a multi-user assignment, the field value is the record ID of the parent event. If the event is not a response to a multi-user assignment, the value is -1. (EvtMUParnt) |
| TT_USER_ID | No | NUMERIC(10) | No | References a record in the TT_USER table. If a user entered the event, the field value is the record ID of the user. If the event was generated by Helix ALM, the field contains a record ID of -2 (idUser) |
| EVENT_DATE | No | DATETIME | No | Test run event date (dateEvent) |
| NOTES | No | NVARCHAR(max) | No | Notes field (Notes) |
| TIME_SPENT | No | NUMERIC(20, 2) | No | If event definition for this event (TT_EVENT table) has the time reporting option selected, field stores the amount of time entered by the user; if event does not record time spent, the value is -1 (TimeSpent) |
| RELEASE_VERSION | No | NVARCHAR(255) | No | Notes field if event is configured to include release notes information (RelVersion) |
| GENERATED_BY_TYPE | No | NUMERIC(2) | No | How the event was created - 0: Created by user, 1: Created by multi-user assignment, 2: Created by auto assignment), 3: Created by auto escalation (GenByType) |
| CREATED_BY | No | NUMERIC(10) | No | Reserved for future use (CreatorID) |
| DEFAULT_ASSIGN_EFFECT | No | NUMERIC(2) | No | Assignment for the event when it was run - 1: Event results in new assignment, 2: Event has no effect on assignment, 3: Event clears assignment. Intended to preserve history if the event definition is modified (DefAsgEff) |
| WORKFLOW_OVERRIDE | No | NUMERIC(1) | No | Indicates if the event is a result of a workflow override (OvrWF) |
| WORKFLOW_OVERRIDE_USER_ID | No | NUMERIC(10) | No | References the TT_USER table. If the event is a result of a workflow override, the field value is the record ID of use. Otherwise, the value is 0. (OvrWFUsrID) |
| MARK_ITEM_SUSPECT | No | NUMERIC(1) | No | Indicates if the user selected the option to mark dependent items as suspect (SspLnkItms) |
Table: TT_TESTRUN_EVENT_ASGN_USER
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER_ID. User or customer. |
| TESTRUN_EVENT_ID | Yes | NUMERIC(10) | Yes | References the TT_TESTCASE_EVENT table. Test case event the user is assigned to. |
Table: TT_TESTRUN_EVENT_ATCHMT
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| ATTACHMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTRUN_EVENT_ID | No | NUMERIC(10) | No | References the TT_TESTRUN_EVENT table. Test run event the file is attached to. (EntityRID) |
| ATTACHMENT_TYPE | No | NUMERIC(1) | No | File attachment type - 1: Macintosh binary file, 2: Other file type (AttType) |
| FILE_NAME | No | NVARCHAR(200) | No | Original file name before it was attached to an entity (FileName) |
| MAC_TYPE | No | NUMERIC(10) | No | Macintosh type (valid for Macintosh only) (MacType) |
| MAC_CREATOR | No | NUMERIC(10) | No | Macintosh creator (valid for Macintosh only) (MacCreator) |
| CREATED_DATE | No | DATETIME | No | File creation date (dateCreate) |
| MODIFIED_DATE | No | DATETIME | No | File modification date (dateModify) |
| FILE_SIZE | No | NUMERIC(10) | No | File size (FileSize) |
| ARCHIVE_FILENAME | No | NVARCHAR(24) | No | Archive file name used for storage in the database (ArchvFile) |
| COMPRESSED | No | NUMERIC(1) | No | Reserved for future use (Compressed) |
| ATTACH_IN_DB | No | NUMERIC(1) | No | Indicates if the archive file contents are stored in database (valid for RDBMS only) (AttachInDB) |
| FIELD_ID | No | NUMERIC(10) | No | Field ID that contains the WYSIWYG inline image (FieldID) |
| IMG_WIDTH | No | NUMERIC(5) | No | Original width of image added as inline WYSIWYG image (ImgWidth) |
| IMG_HEIGHT | No | NUMERIC(5) | No | Original height of image added as inline WYSIWYG image (ImgHeight) |
| SUBTYPE_ID | No | NUMERIC(10) | No | Foreign key to the TT_SUBTYPE table. Specifies the subtype field definition the file attachment belongs to. (SubtypeID) |
Table: TT_TESTRUN_LOG
| Comment | 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) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TESTRUN_LOG_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| TESTRUN_ID | No | NUMERIC(10) | No | References a record in the TT_TESTRUN table (ParentID) |
| TT_USER_ID | No | NUMERIC(10) | No | User who made change. References a record in the TT_USER table. (idUser) |
| LOG_DATE | No | DATETIME | No | Date/time the change occurred (dateLog) |
| NOTES | No | NVARCHAR(4000) | No | Change description (Notes) |
Table: TT_TESTRUN_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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_TESTRUN_VALUE table. Test run and field definition. |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Custom pop-up menu field. |
Table: TT_TESTRUN_SELECT_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_TESTRUN_VALUE table. Test case and field definition. |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer. |
Table: TT_TESTRUN_SET
| Comment | Contains test run set pop-up menu values. Each row in this table represents one pop-up menu item. (FLDTRSET) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TESTRUNSET_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| FIELD_ORDER | No | NUMERIC(10) | No | Pop-up menu item order relative to other items (FieldOrder) |
| FIELD_DESCRIPTION | No | NVARCHAR(255) | No | Text displayed for the pop-up menu item (Descriptor) |
Table: TT_TILE
| Comment | Contains information about widgets used on the Home page |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TILE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| ENTITY_TYPE | No | NUMERIC(10) | No | Item type the widget is filtered on |
| TITLE | No | VARCHAR(512) | Yes | Widget name |
| DISPLAY_ORDER | No | NUMERIC(5) | Yes | Widget position relative to other widgets |
| HAS_GRADIENT | No | NUMERIC(1) | Yes | Indicates if widget scales color to show transitions |
| TILE_DESCRIPTION | No | VARCHAR(1020) | No | Widget description |
Table: TT_TILE_COLOR_MAP
| Comment | Contains color settings for Home page widgets |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| COLOR_MAP_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TILE_ID | No | NUMERIC(10) | Yes | Record ID of parent widget |
| VALUE_START | No | NUMERIC(10) | Yes | Number of items that must pass the widget filter to start using specified color |
| COLOR | No | VARCHAR(24) | Yes | Widget color. Hex value. |
Table: TT_TREVENT_RESULT_STATE
| Comment | 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. |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| STATE_ID | Yes | NUMERIC(10) | Yes | Event resulting state |
| TESTRUN_EVENT_ID | Yes | NUMERIC(10) | Yes | Test run event the state is related to |
Table: TT_TREVENT_SELECT_FIELD
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_TESTRUN_VALUE table. Test run and field definition. |
| POPUP_FIELD_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_POPUP_FIELD table. Custom pop-up menu field. |
Table: TT_TREVENT_SELECT_USER
| Comment | 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 |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| EVENT_VALUE_ID | Yes | NUMERIC(10) | Yes | References the TT_CUSTOM_TESTRUN_VALUE table. Test run and field definition. |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | References the TT_USER table. User or customer. |
Table: TT_USER
| Comment | Contains user and customer information. Each table row represents one user or one customer. (USERS) |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| TT_USER_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row (idRecord) |
| ACTIVE | No | NUMERIC(1) | Yes | Indicates if a user is active. If false, the user is inactive. (Active) |
| FIRST_NAME | No | NVARCHAR(32) | No | First name field (FirstName) |
| USER_GROUP_ID | No | NUMERIC(10) | No | User group field. In Helix ALM, links to a security group. In the data warehouse, group information is not carried over and the field is not mapped. Reserved for future use. (idUsrGroup) |
| LAST_NAME | No | NVARCHAR(32) | No | User group field. In Helix ALM, links to a security group. In the data warehouse, group information is not carried over and the field is not mapped. Reserved for future use. (idUsrGroup) |
| LOGIN_NAME | No | NVARCHAR(356) | No | Login name field. For local users, NULL is used. (LoginName) |
| DATE_LOGOUT | No | DATETIME | No | Date/time (in GMT) the user last logged out of Helix ALM (dateLogout) |
| NOTES | No | NVARCHAR(max) | No | Notes field (Notes) |
| PHONE_TYPE_1 | No | NUMERIC(2) | No | Foreign key to the TT_PHONE_TYPE table |
| PHONE_NUM_1 | No | NVARCHAR(32) | No | First phone number field (PhoneNum1) |
| PHONE_TYPE_2 | No | NUMERIC(2) | No | Foreign key to the TT_PHONE_TYPE table |
| PHONE_NUM_2 | No | NVARCHAR(32) | No | Second phone number field (PhoneNum2) |
| BETA_SITE | No | NUMERIC(1) | No | Beta test site field (used for customers only) (BetaSite) |
| COMPANY | No | NVARCHAR(63) | No | Company field (used for customers only) (Company) |
| ADDRESS | No | NVARCHAR(255) | No | Address field (used for customers only) (Address) |
| CONFIG_ID | No | NUMERIC(10) | No | References a record in the TT_SYSTEM_CONFIG table where the system configuration information is stored for the user (idTestConf) |
| EMAIL_TYPE | No | NUMERIC(2) | No | Foreign key to the TT_EMAIL_TYPE table |
| EMAIL_ADDRESS | No | NVARCHAR(63) | No | User email address (EMailAddr) |
| IS_CUSTOMER | No | NUMERIC(1) | No | Indicates if a user is a customer- 0: user, 1: customer. (IsCustomer) |
| IS_GLOBAL | No | NUMERIC(1) | No | Indicates if the user is a global user (IsGlobal) |
| ALLOW_SSO | No | NUMERIC(1) | No | Indicates if single sign-on is supported (AllowSSO) |
| INITIALS | No | NVARCHAR(8) | No | User middle initials (Initials) |
| DIVISION | No | NVARCHAR(63) | No | User division (Division) |
| DEPARTMENT | No | NVARCHAR(63) | No | User department (Department) |
| ADDL_INFO | No | NVARCHAR(max) | No | Additional user information. Reserved for future use. (AddlInfo) |
Table: TT_USER_HIDDEN_TILE
| Comment | Contains a row for each Home page widget hidden by a user |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| HIDDEN_TILE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TT_USER_ID | No | NUMERIC(10) | Yes | Record ID of user with hidden widget |
| TILE_ID | No | NUMERIC(10) | Yes | Record ID of the hidden widget row |
Table: TT_USER_SCM_FILE_DEFECT
| Comment | Contains associations between a parent defect source control file record and one or more user records |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| USER_SCM_FILE_DEFECT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TT_USER_ID | No | NUMERIC(10) | Yes | TT_USER record for file |
| TT_SCM_FILE_ID | No | NUMERIC(10) | Yes | TT_SCM_FILE_DEFECT record user is associated with |
Table: TT_USER_SCM_FILE_DOCUMENT
| Comment | Contains associations between a parent requirement document source control file record and one or more user records |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| USER_SCM_FILE_DOCUMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TT_USER_ID | No | NUMERIC(10) | Yes | TT_USER record for file |
| TT_SCM_FILE_ID | No | NUMERIC(10) | Yes | TT_SCM_FILE_DOCUMENT record user is associated with |
Table: TT_USER_SCM_FILE_REQUIREMENT
| Comment | Contains associations between a parent requirement source control file record and one or more user records |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| USER_SCM_FILE_REQUIREMENT_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TT_USER_ID | No | NUMERIC(10) | Yes | TT_USER record for file |
| TT_SCM_FILE_ID | No | NUMERIC(10) | Yes | TT_SCM_FILE_REQUIREMENT record user is associated with |
Table: TT_USER_SCM_FILE_TESTCASE
| Comment | Contains associations between a parent test case source control file record and one or more user records |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| USER_SCM_FILE_TESTCASE_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TT_USER_ID | No | NUMERIC(10) | Yes | TT_USER record for file |
| TT_SCM_FILE_ID | No | NUMERIC(10) | Yes | TT_SCM_FILE_TESTCASE record user is associated with |
Table: TT_USER_SCM_FILE_TESTRUN
| Comment | Contains associations between a parent test run source control file record and one or more user records |
Columns:
| Column name | Primary key | Data type | Not NULL | Comment |
| TT_SOURCE_ID | Yes | NUMERIC(10) | Yes | References the REP_SOURCE table. System the data originated from. |
| TT_PROJECT_ID | Yes | NUMERIC(10) | Yes | References the TT_PROJECT table. Project the data originated from. (ProjectID) |
| USER_SCM_FILE_TESTRUN_ID | Yes | NUMERIC(10) | Yes | Record ID that uniquely identifies a table row |
| TT_USER_ID | No | NUMERIC(10) | Yes | TT_USER record for file |
| TT_SCM_FILE_ID | No | NUMERIC(10) | Yes | TT_SCM_FILE_TESTRUN record user is associated with |