The assistant in your workspace works within a few fixed limits. When it meets one, you see it in the answer, with the ways round it. It never cuts your work short, or sends a request to our team, without asking you first.
The limits
| Limit | While you build | Once published |
|---|---|---|
| Rows in each level of a screen | The preview shows the first 500 | Up to 50,000 |
| Time for one query | 60 seconds | 60 seconds |
| Queries on one screen | 6 | 6 |
| Rows in a dashboard block | 50 | 50 |
The 500 rows are the preview's only. A list longer than that, such as every sub-category for every franchisee, is built all the same: the published report reads up to 50,000 rows a level and shows them all. While you build, the preview's totals cover only the rows it shows.
When the assistant meets a limit
A card with a warning mark appears in the answer. It names the limit, says what met it (for example Sub-category: the preview stopped at 500 rows, and there may be more), gives the rule with its number, and lists the ways round it, such as:
- choosing a month or a store at the top of the screen, so it reads one at a time;
- opening the detail when you click a row, so each row reads only its own detail;
- using a shorter period;
- splitting the work into two screens.
When only the preview is cut, the assistant carries on building and the card tells you how to see every row in the preview. When the limit stops a step, the assistant does not decide for you: it asks in a Decision needed card, with the ways round as the answers. You can also type your own.
Asking our team for something new
Sometimes what you want needs something the product does not offer yet, such as a new display option or a kind of screen we do not have. The assistant then proposes a request to PrymeLedger's product team. Nothing is sent at this point.
A card marked Not filed yet shows what the request is, why, the limit behind it when there is one, what happens once it is filed, and what you could do instead. Below it, a Decision needed card asks whether to file it. Only the answer File it with PrymeLedger's product team sends the request. Choosing a way round, or answering in your own words, sends nothing, and the assistant carries on with your choice.
Once filed, the card reads Filed with PrymeLedger's product team. The team reads it to decide what to build next.
What the team sees
The team sees a description of the request, not your conversation: what was asked, in product terms, the kind of screen, the limit it met, the part of PrymeLedger you were in when you asked (such as Ledger or Payroll and people), and the shape of the work, such as how many columns and rows each level has. Your figures, the names in your data and what you typed are never part of it.
If you would like the team to read your own words, the filed card shows your question with a Share my question with PrymeLedger button. Your words are sent only if you press it.
Hearing back
You and your administrator get a note in your inbox when the request is filed, and again when the team plans it, builds it or decides not to build it, with their reason. The same note may also come by email. Your administrator's note opens the piece of work the request came from, where, while the request is open, they can hand the work to a partner, as described in Work in your own workspace. While our team is taking on work, the note also offers it, with its price for the piece of work and how long its access lasts.