View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004478 | CaseTalk Modeler | Repository | public | 2024-03-21 11:56 | 2025-03-28 16:18 |
Reporter | Marco Wobben | Assigned To | Marco Wobben | ||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Platform | Intel | OS | Windows | OS Version | 11 |
Target Version | 14.x | Fixed in Version | 14.2 | ||
Summary | 0004478: State Modeling | ||||
Description | According to a LinkedIn discussion state is derived from other facts. But the detection of state change, and preventing state change (preventing facts to be updated) needs to be supported by information modeling as a more dynamic rule. | ||||
Additional Information | The stateless Invoice can be subtyped into an Unpaid Invoice and a Paid Invoice. The Paid Invoice should not revert back into a Unpaid Invoice. That should be prevented, and needs to prevent deletion of the payment registration fact. So, how to implement/support the actions and constraints of states? | ||||
Tags | No tags attached. | ||||
CaseTalk Edition | unknown | ||||
https://www.linkedin.com/feed/update/urn:li:activity:7176312747943464960/ | |
Being able to list from-to state pairs, and optionally describing the states themselves could provide some appealing visual feedback like: https://www.plantuml.com/plantuml/png/DK_12i8m3BtdAyAEmdx0WsmdyQIWD_7GjT56N3hQRB2_jwqE2k_n-lBoqYKrKUVn0vuT8OsJhkWesSYJSX2uxnxOjWSyab1a2t-isfL48GSeOLCudcG9RAb1a-edxh77y_0cgtXR9y8q3remFBV0RGOkXbtsg-U4-Ha9wYbYqiZoWfgMLnRNpreAzD5wNiZ1HggQAqD7ul9LNm00 |
|
|
|
A simple FromState=[ToState]* can be depicted using plantuml. The Label Type could be marked as a 'state type', creating a special VC and the list of possible states may be stored in the VCValues. The VC would need an annotation describing the graph. The UI only has to present a simple matrix containing the fromState in rows, and possible toStates in the columns, with a checkbox in the cells to indicate possible state changes. |
|
The Value Constraint Values can now contain lines similar to: oldState->newState1;newState2 newState1->Done=Finished Note: The Experimental Features needs to be turned on first in Tools\Preferences\Advanced. Note2: A graphical output is visible in the UML Class Diagram. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2024-03-21 11:56 | Marco Wobben | New Issue | |
2024-03-21 11:56 | Marco Wobben | Status | new => assigned |
2024-03-21 11:56 | Marco Wobben | Assigned To | => Marco Wobben |
2024-03-21 14:33 | Marco Wobben | Note Added: 0005123 | |
2024-03-25 22:44 | Marco Wobben | Note Added: 0005125 | |
2024-03-25 22:45 | Marco Wobben | Note Edited: 0005125 | |
2024-03-25 22:47 | Marco Wobben | Note Edited: 0005125 | |
2024-03-25 22:47 | Marco Wobben | Note Added: 0005126 | |
2025-03-27 12:03 | Marco Wobben | Note Added: 0005521 | |
2025-03-27 12:04 | Marco Wobben | Note Edited: 0005521 | |
2025-03-27 12:06 | Marco Wobben | Note Edited: 0005521 | |
2025-03-28 16:18 | Marco Wobben | Status | assigned => resolved |
2025-03-28 16:18 | Marco Wobben | Resolution | open => fixed |
2025-03-28 16:18 | Marco Wobben | Fixed in Version | => 14.2 |
2025-03-28 16:18 | Marco Wobben | Note Added: 0005522 |