Keep Answers and Standing Requests
Description
Section titled “Description”An answer from Weave doesn’t have to end with the conversation. Under an answer in the Weave dock, Keep ▾ lists the ways to keep it. Each one prepares a card or a window for you to confirm. Nothing is kept until you do.
| Keep ▾ | What you get | Offered |
|---|---|---|
| As a standing request | A report Weave runs every week and sends you. See Standing Requests. | Under an answer that read a metric. |
| As a metric | A new metric with the answer’s filters, which anyone in the project can ask for. See Keep an Answer as a Metric. | To project Architects, under a metric answer with a filter. |
| As a scenario | A saved what-if. See Keep an Estimate as a Scenario. | Under a what-if estimate, to members who can edit the project. |
| As a recipe | The question, saved for your team to run again. See Team Recipes. | Under any answer. |
| As a pinned answer | The answer, shared with the project and re-run for each reader. See Pinned Answers. | Under an answer Weave can re-run for someone else. |
Keep ▾ is offered under an answer for 30 days after Weave gives it.
Standing Requests
Section titled “Standing Requests”A standing request is a report or an alert that Weave runs for you, on a schedule or after a workflow runs, and sends you the result. Ask for one in the dock in your own words:
- Every Monday send me margin by region.
- After Month-End Close runs, tell me which carriers’ freight moved more than 10%.
- Tell me when freight passes 2,000,000 this month.
Weave answers with a card that says what it will run and when, such as After Month-End Close runs: Freight by Carrier for the month just closed, against the month before. Weave tells you which carriers moved more than 10%. First check: after the next run of Month-End Close. Click Save to start it, Change… to ask again, or Not now.
Keep ▾ → As a standing request under a metric answer prepares the same card in one step: a weekly report of that answer, on Mondays at 08:00 in your Weave time zone. A period you asked about, such as this month, moves on with each report.
Reports and Alerts
Section titled “Reports and Alerts”- A report sends its result every time it runs. A scheduled report whose figures haven’t changed says No change since and the day.
- An alert needs a condition: which figure, and what it has to pass, fall below or move by. It tells you only when the condition is met. An alert that runs after a workflow also checks when its tables are written outside a run.
- A report or alert that runs after a workflow does nothing when the tables it reads haven’t changed.
Results read like 2 carriers moved more than 10%: Atlas +14.2%, Summit −11.0%. 9 others moved less.
How You’re Told
Section titled “How You’re Told”When a result is ready, Weave tells you in PlaidCloud, in the dock’s jobs, and on your phone if you use the mobile app, such as Weave has your Freight by Carrier report. Open the figures in PlaidCloud. If you have Weave email on and your workspace allows it, you also get an email titled Weave: and the request’s name, with a link to open it. Emails never contain figures. During your workspace’s quiet hours, the email isn’t sent and the result waits for you in PlaidCloud.
If a request can’t run, Weave tells you once, such as Weave couldn’t run your request Freight by Carrier. Open Requests to see why.
Your Requests Run as You
Section titled “Your Requests Run as You”A standing request runs as the person who saved it, with that person’s access. If you can no longer open the project’s figures, the request stops and says so. Requests are personal: only you see, run, change, pause or remove yours.
The Requests Page
Section titled “The Requests Page”Open the project’s Weave tab and click Requests in the Monitor rail. The page lists Reports, alerts and recipes you asked Weave to run, on a schedule or after a workflow runs.
Each request shows its name and its state (Working, Needs you or Paused), Weave’s sentence about what it runs, when it runs, with the time zone, and its last result, or No result yet.
- Run now runs it straight away.
- Pause stops it running until you click Resume.
- ⋯ → Change opens the dock with your request filled in, for you to say what to change.
- ⋯ → Remove stops it for good, after you confirm.
Click New request to open the dock and ask for one.
Keep an Answer as a Metric
Section titled “Keep an Answer as a Metric”When Weave answers from a metric with a filter, such as revenue for the Retail channel, a project Architect can keep that filtered figure as a metric of its own.
- Under the answer, choose Keep ▾ → As a metric.
- In the New metric window, check the Name, such as Revenue — Retail, and the Definition: the measure and the filters.
- Click Save.
The metric is live as soon as it’s saved: anyone in the project who can ask for metrics can ask Weave for it by name. It’s saved without the period you asked about, so it can be asked for any period. To stop Weave answering from it, click Retire.
- A name that’s already taken gets a number, such as Revenue — Retail (2).
- An answer with no filter other than a period is the metric itself, so there’s nothing new to keep. Weave says so.
- A metric built from other metrics can’t be kept with a filter.
Open the dashboard editor in the window opens Dashboards in a new tab, for charting the new metric.
Keep an Estimate as a Scenario
Section titled “Keep an Estimate as a Scenario”When you ask Weave a what-if about an allocation’s output, such as what if freight rises 8%, it answers with an estimate. See Ask a What-If.
To keep it, choose Keep ▾ → As a scenario. The What if window opens with the change filled in and a name such as Freight +8%. Click Save…, then Save, to keep it. Closing the window without saving discards it.
Saved scenarios change nothing in the project, and everyone in the project sees them. A saved scenario is worked out again on the current data each time it’s opened. A project keeps up to 100 saved scenarios. See Try a Driver What-If.