Skip to content

QortexOS Entering Public Beta Q3. 25 Spots Available. 50% off MSRP, for life. Apply ->

QortexOS release

0.7.0-alpha

QortexOS v0.7.0-alpha

Released

Added
  • The labor analytics gain loaded-cost, capacity and coverage figures (loaded labor cost and margin, employer benefit and statutory cost totals, measured capacity and its utilization, attendance and absence hours, the unresolved and unclassified hours), with the vocabularies and the US federal employer tax rates behind them; the rates apply to US-based tenants only.
  • GDPR Compliance now shows your tenant's real retention schedules: a summary of schedules, legal holds, expired and pending-anonymization records, a view of schedules past their retention end, and placing or releasing a legal hold for administrators.
Changed
  • Contract intake now extracts the renewal date alongside the effective and expiration dates, and the contract prompt registry (document classification, field extraction, clause segmentation and the other contract tasks) is delivered to every environment by the regular database deployment instead of only to freshly built databases.
  • GDPR Compliance now shows your tenant's configured data-policy settings (retention period, encryption at rest, data auditing and export approval) instead of illustrative values.
Fixed
  • Database deployments no longer report every table as a failed security-policy deployment when the policies are already in place; a table that is genuinely left without its access policies is now reported as a critical issue instead of hiding inside that noise. The retention outreach task queue, which had been left without those policies, is now reachable by the application under a service-account context.
  • Budget Setup's mapping and line steps now say when the account list could not be loaded and let you retry it, announce a failed read to assistive technology, and never claim a page cap over rows they are not showing.
  • Budget Setup now says when the coverage figures or the KPI rows could not be loaded and lets you retry that read, instead of showing a loading line, a dash or the refresh instruction.
  • The Validation Workbench queue lists an Open, Flagged or Skipped pill's checks up to the page cap, including those past the run's first page, and its retry now covers a count or a page that failed to refresh.
  • Evaluating an A/B experiment now applies only to a running experiment or one analyzing its results; a paused, completed, aborted or failed experiment is refused with the reason instead of being silently reopened.
  • A renewal date read from a contract document now reaches the contract and the Renewal Console once the document extractor learns the field (its companion seed change, L0915-33b).
  • Descending lists no longer open with the rows that have no value in the sorted column: a top-spend, top-score or most-recent sort now puts those rows last.
  • Strategic benchmark computations no longer fail on their last dimension when the privacy budget is split evenly across many dimensions.
  • Importing a plan of record now replaces the budget's lines all or nothing: a failure part-way through leaves the previous lines untouched instead of a half-replaced budget.
  • The database migration builder no longer mistakes a comment that mentions its processed marker for the marker itself, so an unprocessed schema change whose header explains the marker is picked up instead of being skipped on every run.
  • The Renewals KPI cards now say that they are what failed to load, with a line on what that means and their own retry, instead of borrowing the renewal registry's error title.
  • Minting a discount sign-up invite works again: the request no longer fails with a database policy error.
  • Budget Setup's Budget master card on the review step now announces to assistive technology when its POR-lines count or COA coverage could not be loaded, including when the failure happens after the page is already showing.
  • Budget Setup now announces to assistive technology when a retried read fails again, and when a step opens with a read that has already failed.
  • Permission checks that name a screen, or any permission code with a hyphen or a digit in it, are now recorded in the system account audit trail; the audit table refused those rows before and the checks went unrecorded. A permission check whose audit row the database refuses now fails instead of proceeding unrecorded.
  • GDPR Compliance now tells you which sections your role cannot view instead of showing a loading error you cannot retry.
  • Clause bank, clause mapping, template, template version and tenant association actions in the Contracts API now answer with the response shapes their contract declares.
  • Retry buttons on the Data Platform home, the Connectors screens and the partial KPI notice now say what they reload, and the Pipeline Console's KPI strip names its own figures when they fail to load.