| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004548 | CaseTalk Modeler | Refactoring | public | 2024-04-12 09:02 | 2024-08-20 10:46 |
| Reporter | Lennart van Ham | Assigned To | BCP Software | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | Intel | OS | Windows | OS Version | 11 |
| Product Version | 13.2 | ||||
| Target Version | 14.x | Fixed in Version | 13.5.1 | ||
| Summary | 0004548: Reflecting name changes in expression files | ||||
| Description | It would be nice if name-changes in diagrams were reflected in expression files. For example, 'belangen' (image 1) was formerly called 'belangen betrokken partij' (as it is still in the expression window, in image 2). It is kinda hard keeping the expression-file up-to-date with name changes in the repository/diagrams. | ||||
| Tags | No tags attached. | ||||
| CaseTalk Edition | Education Edition | ||||
 |
This requires an extension of the Expression file to include OTFT IDs since they may be renamed while the EXP file was not open. |
|
|
Workaround: would be to set the expression file to a connected state to indicate which fact expressions are (not) present in the model. |
|
|
Connected expression files will detect an OTFT Rename; and the exp-file will now include the OTFT Synclink to allow detecting renames while the file was not open and connected. |
