project Table (11)
Projects
Fields
| Name | Description | Type | Null |
|---|---|---|---|
| project_id | Primary key | PK | |
| name | Project name | String(219) | ● |
| project_number | Automatically generated number | String(49) | ● |
| type_idx | Link to ProjType list | FK ProjType | |
| status_idx | Link to ProjStatus list | FK ProjStatus | ● |
| associate_id | Project manager/owner | FK associate | |
| text_id | Description field | FK text | ● |
| registered | Registered date | UtcDateTime | |
| registered_associate_id | Registered by whom | FK associate | |
| updated | Last updated date | UtcDateTime | |
| updated_associate_id | Last updated by whom | FK associate | |
| userdef_id | Pointer to userdef small table | FK udprojectSmall | ● |
| soundEx | What the name sounds like, for duplicate detection | String(9) | ● |
| source | How did we get this project? For future integration needs | UShort | ● |
| userdef2_id | User defined table record 2 | FK udprojectLarge | ● |
| postitText_id | Paperclip text | FK text | ● |
| updatedCount | Number of updates made to this record | UShort | |
| group_id | Group id of original owning associate, semantics like appnt.grp_id | FK UserGroup | ● |
| tzLocationId | Default timezone location for this project | FK TZLocation | ● |
| activeLinks | Number of active links to documents, other appointments, and such | UInt | ● |
| done | Done (0=false, 1=true). Status implies changes in which fields are shown in GUI, as well as which fields can be updated | Bool | ● |
| endDate | Planned end date for project, inhertied from type and later editable | DateTime | ● |
| nextMilestoneDate | Calculated date, reflects date of closest non-complete future milestone activity | DateTime | ● |
| nmdAppointment_id | ID of appointment that “caused” the nextMilestoneDate, can be 0 | FK appointment | ● |
| activeErpLinks | The number of Erp Sync connections this record is synced with; count of the ErpExternalKey+ErpInternalKey relations | Int | ● |
Indexes
| Fields | Types | Description |
|---|---|---|
| project_id | PK | Clustered, Unique |
| name | String(219) | Index |
| project_number | String(49) | Index |
| soundEx | String(9) | Index |
| source | UShort | Index |
| userdef2_id | FK | Index |
| done | Bool | Index |
Relationships
| Table | Description |
|---|---|
| appointment | Tasks, appointments, followups, phone calls; and documents (document_id != 0). An appointment always has a corresponding record in VisibleFor specifying who may see this. |
| associate | Employees, resources and other users - except for External persons |
| chat_session | This table contains chat sessions. |
| CounterValue | Visible for rights |
| Email addresses for contacts, projects and persons | |
| projectmember | Project members. Link-table between person and project |
| ProjStatus | ProjStatus list table. Project status |
| ProjType | ProjType list table. List of valid Project types. |
| s_link | Links in messages to measure success rate of a campaign. |
| s_shipment | Contains info about one shipment. The addresses are stored in s_shipment_addr |
| sale | Sales For every Sale record edited through the SuperOffice GUI, a copy of the current version of the record will be saved in the SaleHist table. This also applies to editing done through the SaleModel COM interface, but not to editing done through the OLE DB Provider or other channels. |
| SaleHist | Mirror image of the Sale table, providing a full transaction history. Every time you edit a sale, the current record of the sale is also saved here. |
| StatusValue | Values for statuses |
| text | Long text fields from all over the system |
| ticket | This table contains the tickets (requests) of the system. Its purpose should be evident. |
| TZLocation | Time zone location |
| udprojectLarge | User-defined fields. During conversion of user defined fields the data is stored in this table. |
| udprojectSmall | User-defined fields |
| URL | Unified Resource Locators, URL to contacts, persons or projects. |
| UserGroup | Secondary user groups |
Replication Flags
- Area Management controlled table. Contents replicated to satellites and traveller databases.
- Replicate changes UP from satellites and travellers back to central.
- Copy to satellite and travel prototypes.
- Cache table during filtering.
Security Flags
- Sentry controls access to items in this table using user’s Role and data rights matrix.