View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003723 | CaseTalk Modeler | Repository | public | 2022-11-25 15:03 | 2023-10-04 12:33 |
Reporter | BCP Software | Assigned To | BCP Software | ||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Target Version | 13.0.1 | Fixed in Version | 13.0.1 | ||
Summary | 0003723: Allow entering Rule as a seperate OTFT | ||||
Description | Business Rule texts are not entered anywhere, except when defined as a custom annotation. It might be convenient to enter a Rule as a separate OTFT and allow for custom metadata. | ||||
Tags | No tags attached. | ||||
CaseTalk Edition | unknown | ||||
Note: A business rule is not necessarily an engineering constraint. It could be a simple text note, and in the future it might contain more formal rules and formulas. | |
This solution would still require unique names for all OTFTs within a schema. Would it be practival to name rules, and have those named uniquely? | |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-11-25 15:03 | BCP Software | New Issue | |
2022-11-25 15:03 | BCP Software | Status | new => assigned |
2022-11-25 15:03 | BCP Software | Assigned To | => BCP Software |
2022-11-25 15:03 | BCP Software | Issue generated from: 0003722 | |
2022-11-25 15:05 | BCP Software | Note Added: 0004686 | |
2022-11-25 15:06 | BCP Software | Note Added: 0004687 | |
2023-10-04 12:33 | BCP Software | Status | assigned => resolved |
2023-10-04 12:33 | BCP Software | Resolution | open => fixed |
2023-10-04 12:33 | BCP Software | Fixed in Version | => 13.0.1 |