What the AI can't do yet

Divvent builds applications from a set of building blocks, and some things you might ask for aren't among them yet. This page lists the gaps we know about, and explains what happens to a change that needs one of them.

When a proposal says what it can't do

A proposal is in three parts, in the change's conversation:

• What this change builds: what approving it does;
• What Divvent cannot do yet: anything you asked for that Divvent can't build, each with a one-line reason;
• What you would do yourself: anything outside the application, such as buying label sheets or telling your staff.

So a request Divvent can only half do still gets the half it can do, and the rest is said plainly rather than left for you to find out later. Each missing piece is also recorded for our team. We see how many businesses have asked for the same thing, and that helps decide what we build next.

What "Waiting on Divvent" means

Sometimes a change can't be proposed properly until Divvent can build the missing piece. Our team can then mark it Waiting on Divvent. When that happens:

• the change stops waiting on anybody's approval, and nothing is built;
• its page says Waiting on Divvent since a date, and for how many days;
• each missing piece is listed with where it has got to: not built yet, not something we will build, or built and on its way. It also says how many other businesses have asked for the same thing. It never says which businesses, and never shows their words.

While it waits, you can still add to it. Write in Add to this request while it waits and press Keep this for when it comes back. Nothing is proposed and nothing is spent. What you add is kept and read when the change comes back.

When everything it was waiting for is built, the change comes back by itself. It is proposed again, from your own words, against what Divvent can now build. Proposing it again counts against your AI budget, like any other answer. It then appears on Changes for you to read and approve as usual.

If you no longer want it, you can decline it at any time. See Read a change and approve it.

Things Divvent can't do yet

These are the gaps we know about, as you would run into them.

Flows

• A flow can't start on a date held on a record yet. For example, "remind the customer three days before their boiler service is due" isn't possible yet. In the Flows editor, When a date arrives is shown but can't be chosen, and the ready-made Remind someone before a date flow is marked as not possible yet. For now, a flow can run on a schedule instead. See Flows: what happens on its own.

Documents and signatures

• You can't add a document to your application yet. Neither the AI nor the editors can add an invoice, a receipt or a job sheet as a document, or change how one is laid out.
• When documents arrive, only one person will sign each one, and a flow won't issue one by itself. Signing by several people in order, and issuing a document from a flow, aren't planned for the first version. See Documents and signatures.

How your application looks and speaks

• You can't change your application's colours or fonts by asking yet. The AI can change pages, menus and what is on them, but not the overall look.
• Your application speaks one language. It uses the language, currency and time zone you chose when you created it. It can't offer its words in several languages yet.

Trying a change before you approve it

• You can't try a change in a test copy before approving it. The change's page shows how your pages will look with made-up records, but a test copy runs a version, and a version is made by approving. Approving doesn't release anything, so you can approve, try the new version in a test copy, and only then release it to production. See Try a version in a test copy.

Working on a change together

• You can't leave comments for a colleague on a change. A change's conversation is with the AI. To discuss a change with someone, send them its page.
• You can't see who else is looking at a change.

Devices

• You can't connect trackers or sensors yet. For example, a van tracker or a temperature sensor can't feed readings into your application or start a flow when a van arrives somewhere.

Things the AI will never do

Some things aren't gaps. They are kept for a person on purpose:

• approving a change, or releasing a version;
• choosing what your application keeps about people;
• turning off the second sign-in step for a role;
• lowering how sensitive a kind of record is marked, or recording less about changes to it.

See The AI and your data.

Asking for something that isn't here

Ask for it on Changes in your own words, as you would anything else. If Divvent can't build it yet, the proposal says so, and your request is counted. That is how the list on this page gets shorter.