Deliverables database table
From TaskDepender
(→Description) |
|||
| Line 5: | Line 5: | ||
The deliverable element is described in the [[Task_Management_Method#Deliverable|"Task Management Method"]]. The deliverables in the project are stored in a table in the project database. The name does not have to be unique. Therefore, a deliverable also has to have a unique id. Since a deliverable represents a graphical element, it has a position, a width and a height. When using a true-type font, the width and height will be determined when the task is displayed. | The deliverable element is described in the [[Task_Management_Method#Deliverable|"Task Management Method"]]. The deliverables in the project are stored in a table in the project database. The name does not have to be unique. Therefore, a deliverable also has to have a unique id. Since a deliverable represents a graphical element, it has a position, a width and a height. When using a true-type font, the width and height will be determined when the task is displayed. | ||
| − | The following constraint | + | The following constraint apply: |
* When the Deliverable is contained in a container task and that task is deleted, the Deliverable needs to be deleted as well. | * When the Deliverable is contained in a container task and that task is deleted, the Deliverable needs to be deleted as well. | ||
* When the Deliverable is a [[Clone|clone]] of a Deliverable at a higher level and that Deliverable is deleted, then its clone needs to be deleted as well. | * When the Deliverable is a [[Clone|clone]] of a Deliverable at a higher level and that Deliverable is deleted, then its clone needs to be deleted as well. | ||
