stock_rescheduling_popover

When a chain of operations feeds a delivery, a delay upstream silently endangers the promise downstream. Odoo surfaces that with this widget: a small colored icon next to the scheduled date that appears only when the record's json_popover field carries data, and a popover that explains the problem when clicked.

The popover is titled Planning Issue and lists the late preceding operations by name, each rendered as a link carrying the document's model and id; clicking one opens that document's form view. The delay alert date follows in the same sentence, so a planner sees at a glance which upstream document moved and to when.

Technically it is a thin subclass of the stock module's generic popover_widget: it swaps in a component that can open records, changes the default icon and color to warning red, and refuses to open the popup when there are no late_elements in the JSON.

This is the widget that lets a warehouse supervisor answer "why is this delivery flagged" in two clicks instead of a phone call. The alternative workflow, digging through chained transfers or the manufacturing order tree to find the late link, is exactly the kind of investigation that eats planner time daily.

Two operational notes from implementations. First, the triangle only tells you a preceding operation is late; it does not reschedule anything. Treat it as a to-do marker: someone decides to expedite, split, or push the customer date. Second, because the data behind it is computed server-side into a JSON field, the same mechanism is reusable for your own warning popovers: compute a JSON with a message and links on any model, drop the base popover_widget or a subclass on a char field, and you have consistent, clickable alerts in any list view without inventing UI.

How core wires it (transfer list)

<field name="json_popover"
       widget="stock_rescheduling_popover"
       nolabel="1"/>

The field is a char; its value is JSON computed by the server. No options, no attributes beyond layout.

The JSON contract the widget reads

{
    "late_elements": [
        {"id": 42, "name": "WH/MO/00012", "model": "mrp.production"}
    ],
    "delay_alert_date": "08/21/2026 14:00:00",
    "color": "text-danger",
    "icon": "fa-exclamation-triangle",
    "popoverTemplate": "stock.PopoverStockRescheduling"
}

Empty or missing late_elements means the click does nothing; an empty field value means no icon logic beyond the base render. Color and icon are optional overrides on top of the widget's red-triangle defaults.

Reusing the base widget for your own alerts

<field name="my_alert_json" widget="popover_widget"/>

With a computed char writing {"msg": "...", "icon": "fa-info-circle"}, the generic base renders the same pattern with an info style and plain text content.

The division of labor is worth understanding before customizing.

The server decides everything about content. Which operations count as late, what date to show, even which Owl template renders the popover body (popoverTemplate): all of it arrives in the JSON. The widget contributes only defaults (red triangle, top position) and the record-opening click handler.

The click handler reads attributes, not state. Each link in the popover carries element-model and element-id attributes, and the component builds an ir.actions.act_window from them at click time. Adding your own elements to a custom template works as long as those two attributes are present.

The gate is late_elements. The subclass overrides showPopup to return early when the parsed JSON has no late_elements. If you feed it JSON with only a msg, the icon renders but clicks are inert; that content shape belongs to the base popover_widget instead.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable until release, and we re-verify this page against the shipped version.

One visible change so far: the default icons move off FontAwesome. The rescheduling widget's fallback becomes warning instead of fa-exclamation-triangle, and the base popover widget's fallback becomes info instead of fa-info-circle, part of the broader icon set migration we have tracked across other widgets. If your server-side computes pass explicit fa-* icon names in the JSON, plan to update them after the release; JSON that omits icon picks up the new defaults automatically.