RIA's proposals
Run, apply, approve or set aside what RIA proposes from the console: what-ifs, model edits, change orders and workspace layouts.
Where: RIA diamond→a proposal card above the message box
When RIA suggests a change, it doesn't make it. It puts a card between the conversation and the message box, and nothing happens until you click the card's button. One card shows at a time.
Decide one proposal at a time
The newest proposal is the one you see. When more are waiting, a line under it counts them: +<n>
more proposals waiting — decide or hide this one to see the next. Model edits and workspace layouts
come first, then what-ifs, then change orders.
Proposals are scoped to what's on screen. A card for a different model stays hidden until you open that model; a card for the workspace on screen always shows; with no model open, every card shows.
Every card has an X in its corner (Hide this card). On a what-if, a model edit or a layout it drops the proposal, the same as Discard. On a change order it only hides the card: the change order stays on the model's backlog.
Undecided what-if, model-edit and layout cards live in the page. Reload and they're gone; ask RIA again. Change orders are kept on the backlog.
Run a proposed what-if
The card shows the what-if's name and RIA's reason, then What changes: one row per change, with the
value it sets. Compared against Base at $<n>. names the number it will
be judged against. There are no before-and-after numbers until it runs.
Click Run it (Starting…). eode creates the scenario, starts its solve, and puts a receipt in the
conversation — Created the what-if “<name>”, with Undo, which deletes it again. The card
then reads Running “<name>”. with Open scenarios.
The note runs one at a time is a reminder that solves queue. Discard drops it. Running and reading what-ifs is on What-ifs.
Apply a model edit
A model edit changes the model itself. The card is tagged model edit and shows its proof before you decide:
| Row | Shows |
|---|---|
| Base cost or Base objective | The Base number today, or not solved yet |
| Proposed | The number with the change, its signed difference and the percentage |
| feasible / infeasible | Whether the changed model still has an answer |
| validation passed | The edit passed the model's checks |
What changes (<n>) | Open it for each change, from → to |
Apply rebuilds the model with the change and saves a new version: Applied as version <n>.
Revert any time from the model's version history. See Versions and history.
Discard drops it.
If the edit didn't pass, the card reads That change needs a tweak first instead, with What was
proposed (<n>), what went wrong with each change, and try this with a way round it. Dismiss
closes it.
Work a change order
When RIA files a change on the model's backlog, it arrives as one line: Change filed: <title> with
Open ⌄. Click to open the card. It reads Filed on <model>’s backlog · <group>, with RIA's detail
and your words quoted.
- Click Preview. eode runs a trial solve and shows What this does (proven on a trial solve) with the Base and proposed numbers, or infeasible.
- Click Apply. It appears only after a successful preview. The card reads Applied as version
<n>. A larger change rebuilds the model, which will pause at its Model Design first for your sign-off (Review the design). - Or click Set aside, type why (Why set this aside? (e.g. this doesn't apply to us)), and click Set aside with this reason. Cancel backs out.
Open in Develop opens the model's backlog, where the same item has its full controls. See Change a model.
On a model with no Model Design, the card says This model has no Model Design to change, so this can't be previewed. On a model you built from a description, Add to my description opens your description with the change added; saving it rebuilds the model.
When a change order can't go through, the card says why and what to do:
| The card says | Do |
|---|---|
| This change is no longer on the model's backlog. Open Develop to see what is. | Open Develop. |
| This is a what-if, so it runs as a scenario instead of changing the model. Open it in Develop to run it. | Run it from Develop. |
| This one needs to be described as a specific change before it can be previewed. Open it in Develop to work on it. | Use Ask RIA to draft it in Develop. |
| The tool can't build this capability yet, so it stays on the backlog as demand, not a to-do. Set it aside if you don't need it. | Set it aside, or leave it. |
| This change is already part of the model. Revert it from the version history if you need to. | Nothing to do. |
| The model already works this way, so there is nothing to change. Set it aside. | Set it aside. |
| This change doesn't fit the model as drafted. Ask RIA to describe it again, or open it in Develop. | Ask RIA again. |
| This model's structure can't be changed here. Open it in Develop to see what it can take. | Open Develop. |
| The change didn't build cleanly, so the model is unchanged. Open it in Develop to see why. | Open Develop. |
| This model no longer exists. Hide this card. | Hide it. |
| You can see this model but not change it. Ask its owner for edit access. | Ask the owner. |
| The engine isn't available right now. Try again in a moment. | Try again. |
| That took too long to come back; the engine may still be working on it. Try again. | Try again. |
| That didn't reach the server. Try again. | Try again. |
Approve a workspace layout
On an open workspace, RIA can propose a layout. The card is tagged workspace
and counts <n> widgets in the refined layout. Adjusted to fit your data lists widgets RIA
changed to fit; Couldn't be added lists ones it dropped.
Approve saves RIA's widgets and layout to the workspace. If the save fails, the card stays with the reason, such as Couldn't save the layout. Discard drops it.
Who can decide what
RIA proposes to anyone who can see the model. What you can click depends on your role on the model (Share and govern):
| Your role on the model | Can |
|---|---|
| Owner, contributor | Everything: Run it, Apply, Approve, Preview, Set aside |
| Viewer, approver, promoter | Read every card and Preview a change order. Every other button is refused. |
| Org admin | Everything, on every model |
A refused Apply shows the reason in the card: a missing edit permission, the name of whoever has the model locked, or a model whose structure isn't editable yet (imported models and older builds). Your persona doesn't change any of this.
Limits
- Up to 8 undecided proposals of each kind, newest first.
- The stack takes at most 40% of the console's height and scrolls.
- What-ifs run one at a time.
Related
- The RIA console
- Change a model: the backlog, Develop, Preview and Apply in full
- Versions and history: revert an applied change