Entity relationship diagram

Objects in Workfront (and, therefore, in your Data Connect data lake) are defined not only by their individual values, but by their relationships with other objects. The entity relationship diagram below provides a high-level mapping of object relationships in Data Connect. The diagram can be viewed and downloaded using the following link:

Data Connect entity relationship diagram

IMPORTANT
The entity relationship diagram is a work in progress—as such, it is for reference purposes only and is subject to change.

Date types

There are a number of date objects that provide information about when specific events occur.

  • DL_LOAD_TIMESTAMP: This date is used for internal reference, and reflects when the data was loaded into the Current, Event, or Daily History table. This date should not be used for data analysis, and planned to be removed during the beta phase of Workfront data lake.
  • CALENDAR_DATE: This date is present only in the Daily History table. This table provides a record of what the data looked like at 11:59 UTC for each date specified in CALENDAR_DATE.
  • BEGIN_EFFECTIVE_TIMESTAMP: This date is present in both Event and Daily History tables, and records exactly when a record changed to the value it has in the current row.
  • END_EFFECTIVE_TIMESTAMP: This date is present in both Event and Daily History tables, and records exactly when a record changed from the value in the current row to a value in a different row. To allow for between queries on BEGIN_EFFECTIVE_TIMESTAMP and END_EFFECTIVE_TIMESTAMP this is value is never null, even if there is no new value. In the event a record is still valid (i.e., the value has not changed), END_EFFECTIVE_TIMESTAMP will have a value of 2300-01-01.