Next Analyst release candidate

The job

When you ask where one truck is, what an address is, or to send the same report later, you want that answer in the conversation, so you do not open every record or retype the question.

What changed

• A map for one placeWhen an answer is about a single address, the Analyst shows one location card with the address, a copy action, and a map. Lists, tables, and charts keep addresses as ordinary result fields.
• A truck's last reported positionAsking where a named truck is pins that vehicle's last reported GPS position, not the ticket destination, plant, or jobsite. A stale ping is labeled as last known. A question about many trucks stays a table.
• More warehouse fieldsThe Analyst can use delivery and destination addresses, product availability by plant, list prices, user attribution, billable status, void reasons, and shipping method. Price, cost, tax, freight, and accounts-receivable fields remain protected by pricing permission.
• Analyst and Assistant modesNew chats start in Analyst mode, where write tools stay off. Assistant mode is controlled by an entity feature flag. The mode is recorded on the run, so the restriction holds when a run resumes.
• Approval cards are checked firstBefore an action card appears, the proposed change is resolved against the live order, line, product, and customer. When a record is missing or invalid, the reply explains the problem instead of showing a card that cannot be confirmed. A quantity update sends the full set of line items with only the target quantity changed. If the other lines cannot be preserved, the update is refused.
• Fewer blocking questionsWhen a question already carries usable scope, the Analyst answers it and states the assumption it made, including the time period it used. Alternative readings become follow-up questions you can click.
• Brief Me on the Optimization AnalystAsking for a plan overview returns a fixed set of sections built from the attached plan snapshot. Diagnostic questions about why something happened keep their existing format.
• Oversized screenshotsFiles in the composer already shipped on 20 August. This cut downscales an oversized screenshot before upload instead of failing after the upload finishes. Limits stay 3.75 MB per image, 4.5 MB per document, 20 images and 5 documents per message.
• Saved promptsA question can be saved and reused from the message box.
• A schedule confirmed in the chatAsking to be sent a report on a schedule shows a pre-filled card. The schedule is created when the user confirms, not when the assistant first understands the request.
• Command Center profile labelsProfile label lookup no longer calls an endpoint restricted to platform support, which was showing an error alert to tenant users.

Why

An address or a truck position was another row in a table. A question that already had enough scope still stopped to ask again. A report you wanted later had no confirm step in the conversation.

Impact

This is the next release. It is not in production. When it is, you can ask for one place or one truck and see a map, save a question, and confirm a schedule in the chat. New chats stay read-only until Assistant is turned on for your company. A schedule is created only after you confirm it.

Try it on develop

From an order

• What is the delivery address on this order?
• Which plants carry this product, and what is its list price?

From a ticket or dispatch view

• What is the destination address for this ticket?
• Where is truck TN_VEHICLE right now?
• Why was this ticket voided, and who voided it?

From the message box

• Save this question so I can ask it again.
• Send me a summary of today's orders at 5:00 PM.

From an optimization plan

• Brief me on this plan.

Left out of this note

These merges are on develop and are not customer-visible Analyst changes, so they wait for their own note or for no note:

• Agent Streams, the debugger, triage export, and conversation replay.
• Cloud Agent install, CI, the engine folder move, and dependency bumps other than the SDK pin above.
• Command Router and its classifier (CXAI-290), Conductor planning that reuses it (CXAI-301), compare-verdict scoring (CXAI-320, merged 28 September), quote-to-cash lineage, and the weather test agent. None of these choose an agent for a customer in the Dispatch panel yet.
• Teaching query_data about cai.view_rules.

Still in review

These pull requests are open and are not part of this candidate. They stay off the production note until they merge and a later promotion carries them:

• Plant material usage for the Dispatch Analyst (CXAI-298, #315).
• Standalone Command Intelligence chat (CXAI-261, #297).
• Weekly Warehouse Analyst review email (CXAI-256, #269).
• Feedback resolution note and submitter persistence (CXAI-211, #325). The notice back to the person is the rest of that story.
• Release-note draft generation and translation (CXAI-243, #330).
• Product-doc knowledge search (CXAI-295, #334, draft).
• Automatic agent selection in the side chat (CXAI-299). The router itself is already on develop.
• Listing, pausing, and deleting your own schedules (draft #335).

Release checks

• Promote the current develop build to UAT and test maps, warehouse fields, attachments, and pricing permission.
• Confirm which entities will receive the Assistant feature flag.
• Confirm the Dispatch host is on a connex-cds that includes the map, mode control, saved prompts, and schedule card.
• Confirm the approval path end to end: a valid change still shows a card and confirms, and an invalid one explains instead.
• Replace this candidate with a dated file under site/content/updates/ after the production promotion. Do not label this page as a production release before then.