View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005958 | CaseTalk Modeler | Customization | public | 2026-09-02 22:42 | 2026-09-02 22:42 |
| Reporter | Marco Wobben | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Summary | 0005958: Connecting external agents should be a commercial capability, without limiting the built-in assistant | ||||
| Description | CaseTalk can expose its model over an endpoint so an outside agent - a coding assistant, an automation - can read and change it. That is a capability for commercial use, and it should not be part of the Community and Evaluation editions. The built-in assistant inside CaseTalk is a different matter: it is part of what makes the product worth using while learning it, and it must keep full access to the model in every edition. Wanted: the endpoint for external agents available in the commercial editions only, stated plainly in the options rather than silently doing nothing, and the built-in assistant unaffected wherever CaseTalk runs. | ||||
| Tags | No tags attached. | ||||
| CaseTalk Edition | Corporate | ||||
|
Implemented in 15.0.0.57607. Connecting external agents is now a capability of the commercial editions. In Community and Evaluation the switch is shown but not operable, with a hint saying why, and the page prints the reason where the connection command would otherwise be - rather than offering a command line that could never connect. The built-in assistant is untouched: it keeps full access to the model in every edition, including Community and Evaluation. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-09-02 22:42 | Marco Wobben | New Issue | |
| 2026-09-02 22:42 | Marco Wobben | Note Added: 0009250 | |
| 2026-09-02 22:42 | Marco Wobben | Status | new => resolved |
| 2026-09-02 22:42 | Marco Wobben | Resolution | open => fixed |