Version : 90.1
Released : 2026-09-09
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
5278 |
Bug |
Checks generated against a checkbox field now compare it to 1 or 0, and a comparison against any other value is rejected before the check can be saved. |
|
5279 |
Bug |
The Edit Check Agent no longer asks which field to use on a form that a check adds, since Add Form and Add Matrix actions operate on the whole form. |
|
5280 |
Bug |
Agents now resolve field references written as FORM.FIELD or FOLDER.FORM.FIELD directly, without asking which form or field was meant and without losing the folder. |
|
5281 |
Bug |
Choosing 'None of these' on an agent's field clarification no longer removes the option to generate; you can now type a correction or generate with the objects already found. |
|
5282 |
Bug |
Clarifying an agent's discovered objects now keeps the check's specification and can move a form to a named folder, instead of being ignored and replacing the specification with your correction. |
|
5283 |
Bug |
When an agent picks a coded value your request did not name, the warning now shows both values with their labels and keeps the value you asked for visible in the list. |
|
5284 |
Feature |
Checks can now compare a form's field across two folders, with each reference scoped to the folder the specification names. |
|
5285 |
Bug |
Agents can now build checks that test the value as entered, so an unknown date component named in the specification no longer forces a custom function. |
|
5286 |
Bug |
The Custom Function Agent now builds from an Edit Check's or Custom Object's specification when started from its metadata, instead of reporting that no forms or fields could be found. |
|
5287 |
Bug |
When the Edit Check Agent asks you to type a field name for a form with too many fields to list, your answer is now resolved against that form instead of being ignored. |
|
5288 |
Bug |
An agent no longer binds a form to a folder the form does not belong to, and says so when the folders a specification names do not match where the form lives. |
|
5291 |
Bug |
Clicking an agent option that is no longer available now says so and keeps the check's specification, instead of being read as a new description. |
|
5298 |
Bug |
An agent no longer asks which field to use on a form that a check only adds, rather than reads. |
|
5299 |
Bug |
A generated check is no longer flagged as not matching its specification because a form was named in words rather than by its OID. |
|
5300 |
Bug |
Re-wording a clarification the agent did not understand no longer discards the specification it was building from. |
|
5301 |
Bug |
When a clarification cannot be applied, the agent now shows examples using the objects it found. |
|
5302 |
Bug |
A clarification the agent cannot use now keeps the objects it found on screen instead of reporting a problem reading the specification. |
|
5303 |
Bug |
After a clarification that could not be applied, the agent asks for a rephrase rather than re-offering the confirm buttons. |
|
5306 |
Bug |
Putting a form in a folder no longer removes another form already assigned to that folder. |
|
5307 |
Bug |
Removing a field or a folder in a clarification now affects only the form named, not every form. |
|
5308 |
Bug |
A correction typed while the agent is asking which field to use is now applied instead of being searched for as a field name. |
|
5309 |
Bug |
The message box is disabled while the agent is waiting for a confirm choice, so a typed reply cannot discard the loaded specification. |
|
5310 |
Bug |
Naming a folder in a clarification no longer also adds a form of the same name to the check. |
|
5311 |
Bug |
A clarification that does not name a form now applies to every form found, and a follow-up such as "for both" is understood as continuing the previous correction. |
|
5313 |
Bug |
A folder you name yourself is now flagged for review rather than blocking the save, and the note no longer claims the specification named a different one. |
|
5314 |
Bug |
When an edit cannot be applied the agent now says the check is unchanged, and explains why where it can. |
|
5315 |
Bug |
Naming a folder that does not exist no longer removes the folder a form already had, and the agent says the folder was not found. |
|
5316 |
Bug |
A generated custom function can now be changed by describing the change, as an edit check already could. |
|
5317 |
Bug |
Answers about a generated custom function now read the query flag correctly, instead of describing a guard clause that closes a query as one that opens it. |
|
5318 |
Bug |
Generated custom functions keep a consistent shape when edited, rather than alternating between two structures. |
|
5304 |
Feature |
A clarification saying a form must not be wildcarded is now understood; the agent asks which folder it belongs to instead of using any folder. |
|
5322 |
Bug |
Asking the Edit Check agent for a check on a different form after a specification has been loaded now starts that check on its own, instead of offering it under the name of the check the specification described with overwrite pre-selected. |
|
5340 |
Bug |
A note explaining that something named in a clarification could not be found in the draft is now shown only on the turn that produced it, instead of standing above later summaries that had nothing to do with it. |
|
5176 |
Bug |
When an AI usage limit is reached part way through generating test cases, generation now stops and reports the limit once, leaving the remaining objects ungenerated instead of failing each of them individually. |
|
5325 |
Bug |
Test Case Advisor scenario generation for a Custom Function edit check no longer fails when the AI returns an incomplete datapoint. The scenario is still generated and the missing detail is reported as an issue to resolve. |
|
5326 |
Bug |
Generating Test Case Advisor scenarios for a Custom Function edit check now makes far fewer AI calls. A generation that needed correcting used to restart its whole scenario run on each of three attempts; retries are now limited to correcting the previous attempt, and a generation has an overall cap on the AI calls it may make. |
|
5339 |
Bug |
Form visibility steps no longer report a form the preceding save removed as still present, which failed the step and restarted the test case |
|
5326 |
Bug |
Generating Test Case Advisor scenarios for a Custom Function edit check now makes far fewer AI calls. A generation that needed correcting used to restart its whole scenario run on each of three attempts; retries are now limited to correcting the previous attempt, and a generation has an overall cap on the AI calls it may make. |