View Issue Details

IDProjectCategoryView StatusLast Update
0005848CaseTalk ModelerUser Interfacepublic2026-08-04 16:01
ReporterMarco Wobben Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Target Version15.0Fixed in Version15.0 
Summary0005848: Expression input does not offer an existing object type expression when qualifying a repeated part
Description

When a new sentence is entered in the expression input dialog and part of that sentence repeats wording that already exists in the model, the dialog gives no hint of it.

Example: 'city Utrecht' has already been entered as an object type expression. Entering 'city Utrecht contains 360000 citizens' afterwards does not point out that 'city' already exists. The name field stays empty while the selected part is highlighted.

Confirming the selection with an empty name then creates a new, unnamed value type rather than reusing the existing object type. The button quietly changes to 'No Name', which is easy to overlook when one expects it to apply a name. The result only becomes visible later, as a stray unnamed element in the model.

The Pre-Find option under Options that would surface the already existing expression is switched off out of the box, so in practice users never benefit from it.

TagsNo tags attached.
CaseTalk EditionCorporate

Activities

Marco Wobben

Marco Wobben

2026-08-04 15:59

administrator   ~0008758

Pre-Find is now switched on out of the box. While qualifying a part of a new sentence, any object type whose existing expression matches the selected text is moved to the top of the name list, so a repeated part such as 'city Utrecht' now shows 'city' as the first suggestion instead of leaving the field empty.

The setting remains under Options, Expressions, Pre-Find, with the three choices None, List matches and Select first match. 'List matches' is the new default: the suggestion is offered but never applied on its own, so nothing is chosen on the user's behalf.

Note that the matching itself is still governed by the neighbouring Match setting, which is Exact by default. A difference in capitalisation between the earlier expression and the newly typed one will therefore not be recognised; choose Similar there if that is wanted.

Existing installations keep whatever Pre-Find value they already have stored; the new default applies to new installations and to settings that predate the option.

Marco Wobben

Marco Wobben

2026-08-04 16:01

administrator   ~0008759

Pre-Find is now switched on out of the box. While qualifying a part of a new sentence, any object type whose existing expression matches the selected text is moved to the top of the name list, so a repeated part such as 'city Utrecht' now shows 'city' as the first suggestion instead of leaving the field empty.

The setting remains under Options, Expressions, Pre-Find, with the three choices None, List matches and Select first match. 'List matches' is the new default: the suggestion is offered but never applied on its own, so nothing is chosen on the user's behalf.

Note that the matching itself is still governed by the neighbouring Match setting, which is Exact by default. A difference in capitalisation between the earlier expression and the newly typed one will therefore not be recognised; choose Similar there if that is wanted.

Existing installations keep whatever Pre-Find value they already have stored; the new default applies to new installations and to settings that predate the option.

Issue History

Date Modified Username Field Change
2026-08-04 15:59 Marco Wobben New Issue
2026-08-04 15:59 Marco Wobben Note Added: 0008758
2026-08-04 16:01 Marco Wobben Note Added: 0008759
2026-08-04 16:01 Marco Wobben Status new => resolved
2026-08-04 16:01 Marco Wobben Resolution open => fixed
2026-08-04 16:01 Marco Wobben Fixed in Version => 15.0