Skip to main content
← All updates
Changelog

Coupa, Contracts List Revamp & More Reliable Chat


This week brings the Coupa procurement integration, a structural overhaul of the contracts list, and chat that cancels cleanly across backend instances.

Product Improvements
  • Coupa Integration: Connect Coupa to sync requisitions into June, with commodity-based filtering you configure before the first sync, attachment ingestion, and AI extraction of contract fields like dates, payment frequency, auto-renewal, and notice periods directly into your software contracts.
  • Contracts List Revamp: The contracts page now uses lifecycle tabs (Active, Expired, Expiring Soon, Future) plus virtual tabs for Ignored and Needs Attention, with composable filters for app linking and review status, issue badges on each row, and a cleaner row layout.
  • Clickable Contract Metrics: Metric cards on the contracts page now include explainer tooltips, and clicking Total Spend, Active Contracts, or Expiring Soon jumps to the matching tab while Next Renewal links straight to the contract.
  • Reliable Chat Stop: Stopping a chat now reliably cancels what June is doing, even when the work is being handled by a different backend server. No more chats that keep generating after you’ve hit Stop.
  • Persisted Survey Responses in Chat: When a survey response comes back during a chat, the approval record is now stored on the execution so the response renders correctly when you reload the conversation.
  • Sharper Automation Tool Execution: Automations now run faster and more predictably — when a tool’s inputs are already known, June uses them directly instead of looking them up again.
  • Dynamic Integration Settings: Integration connection forms now support multi-select and provider-driven dynamic multi-select fields, so you can pick from values fetched live from the connected system.
Bug Fixes
  • Contract Breadcrumbs: Editing a contract from the policy Contracts tab now shows the full Software › App › Edit Contract chain instead of collapsing to a default.
  • Contract Validation Errors: Cross-field validation failures (such as end date before start date) now revert the write cleanly and surface a readable error rather than an internal one.
  • Active Contract Status: Contract status in the policy Contracts tab now only shows Active when the contract is truly within its active period, falling back to Unknown otherwise.

Ready to put IT on autopilot?

Talk to an expert