View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003572 | CaseTalk Modeler | Repository | public | 2022-08-18 16:33 | 2022-08-19 10:58 |
Reporter | BCP Software | Assigned To | BCP Software | ||
Priority | normal | Severity | major | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Target Version | 12.5 | Fixed in Version | 12.5 | ||
Summary | 0003572: Role subtype optional failure | ||||
Description | Roles in subtypes cannot be optional, and roles in single OTE, do not turn to optional either. Behaviour seems inconsistent. | ||||
Tags | No tags attached. | ||||
CaseTalk Edition | unknown | ||||
When an OTFT is posted the routines are triggered to determine if roles are optional or not. We assume the roles are non optional, until we find an expression which lacks that role in it. Additionally the NOT NULL flag should overrule this optionality. |
|
Drawing of OP for optional roles remains the same, though is determined by the role being in the expression or not. Additionally the NOT NULL flag on roles overrules the optional role state. And the diagram drawing of OP/NN is made consistent. | |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-08-18 16:33 | BCP Software | New Issue | |
2022-08-18 16:33 | BCP Software | Status | new => assigned |
2022-08-18 16:33 | BCP Software | Assigned To | => BCP Software |
2022-08-19 09:32 | BCP Software | Note Added: 0004589 | |
2022-08-19 10:14 | BCP Software | Note Edited: 0004589 | |
2022-08-19 10:58 | BCP Software | Status | assigned => resolved |
2022-08-19 10:58 | BCP Software | Resolution | open => fixed |
2022-08-19 10:58 | BCP Software | Fixed in Version | => 12.5 |
2022-08-19 10:58 | BCP Software | Note Added: 0004590 |