August 2024

2024.08.26 through 2024.08.30

Feature Launch: Released model improvements, an updated config template, and updated blueprint for Navigator Fine Tuning. It is now the default model recommended in the console as part of the General Availability launch.
Bugfix: project admins should not see the option to update other project admin permissions
Bugfix: invalid date in the org member table wasn't rendered properly
Remove Text/SQL toggle from playground
Bugfix: When using the Navigator FT model in workflows, we previously weren't setting the default num_records field (for gretel_model actions) or the default num_records_multiplier field (for gretel_tabular actions).

Update how Console decides whether to use gretel_model or gretel_tabular when helping the user build a Workflow Config via the Blueprints flow. This change fixes some potential for bugs in the final config, and better aligns with current backend capabilities.
Bugfix: Improve handling of models that could have data privacy metrics, but the options were disabled by the user.

Improve flexibility around what connection types are allowed to be used when creating a workflow. We previously constrained the allowed connection types (e.g., S3, Azure, BigQuery) when creating a workflow based on the type of model selected. This is no longer necessary, and so we've removed these constraints.
Bugfix: Don't attempt to render new data privacy metrics for models that don't support this metric.
Minor UX improvement for score displays in Models List.

Last updated 8 months ago

Was this helpful?

Feature Launch: Released model improvements, an updated config template, and updated blueprint for Navigator Fine Tuning. It is now the default model recommended in the console as part of the General Availability launch.
Bugfix: project admins should not see the option to update other project admin permissions
Bugfix: invalid date in the org member table wasn't rendered properly
Remove Text/SQL toggle from playground
Bugfix: When using the Navigator FT model in workflows, we previously weren't setting the default num_records field (for gretel_model actions) or the default num_records_multiplier field (for gretel_tabular actions).

Update how Console decides whether to use gretel_model or gretel_tabular when helping the user build a Workflow Config via the Blueprints flow. This change fixes some potential for bugs in the final config, and better aligns with current backend capabilities.
Bugfix: Improve handling of models that could have data privacy metrics, but the options were disabled by the user.

Improve flexibility around what connection types are allowed to be used when creating a workflow. We previously constrained the allowed connection types (e.g., S3, Azure, BigQuery) when creating a workflow based on the type of model selected. This is no longer necessary, and so we've removed these constraints.
Bugfix: Don't attempt to render new data privacy metrics for models that don't support this metric.
Minor UX improvement for score displays in Models List.

Last updated 8 months ago

Was this helpful?