Dashboard
The Dashboard is your client's start page. It appears after every sign-in and is reachable at any time through the Dashboard navigation entry. It shows no data but the state of the client: what its license covers, who has access to it, which further clients your account reaches, and what most recently failed.
The page at a glance
The page has no buttons. Everything on it is text or a link, there is neither a list nor a detail view and nothing that could be changed here.
Four blocks sit below one another, each preceded by its label in bold: Current Client, Features included in license, User Access and More Clients. Below them follows the Error Log, and finally a line with our contact address.
Three of these blocks appear only under conditions, and that is not a defect: More Clients is only there if your account reaches more than one client, Features included in license only if your license carries at least one entry, and the Error Log only if there is something to report. An empty dashboard is therefore the good news.
Client and license
The page's first two blocks sit below one another and name the client you are working in and the scope of its license.
Current Client names the client you are currently working in. The same name sits at the top left below the product name and version, and the two together are the quickest check before you change anything: whoever runs several clients otherwise has two nearly identical interfaces in front of them.
Features included in license lists what your contract covers. The entries are grouped by system, for instance Shopware: Channel, Sales Channels. If your license covers everything, a single entry All Features stands there instead.
A channel of a type your license does not include cannot be saved, and the validation message names exactly the missing entry from this list. Comparing the text of that message with this enumeration tells you at a glance whether an extension is needed or whether something is misconfigured.
During an upgrade, license, user access and error log stay out. The page then shows only the client's name, because its data is not queried during that time. That is the normal state of a running update and lasts as long as the update does.
An account without a client sees a single line with our contact address instead of all this. A client is created by us, see access and client.
User access
The block carries one line per email address that has something to do with your client. Every line consists of up to four parts, separated by bullets.
| Part | Meaning | Note |
|---|---|---|
| Name and email address | Who is meant | The name comes from the user profile and is missing where none is stored there. The address is a link and opens a new email |
| Zugang or Kein Zugang | Whether this address may sign in to your client | Zugang (access) shows green, Kein Zugang (no access) red. Red is carried by an address that only receives notifications, the newsletter recipient in your company for instance |
| Ist Besitzer | Who owns the client | Set in bold and usually assigned only once |
| Benachrichtigung | Which emails this address receives from TRADElube: Newsletter, Wartung (maintenance), Status | Missing where the address receives none |
Sorting follows weight: the owner first, then everyone with access, then the rest, and within a group by email address.
The FFE-Tech support address is always in this list. We need the access to be able to look into your client when something goes wrong, so we show it rather than keeping it quiet. Who else stands there is your decision: we set up further users on request, see access and client.
The Benachrichtigung entry is the counter-check to the Error Log below. Whoever carries Status there receives the log's messages by email as well and does not have to open the dashboard for them.
More clients
If your account reaches more than one client, the others sit here as links, sorted by name. A click switches to one of them. There is no toggle, and the data of the clients stays strictly separated. Why one account can carry several clients is described under access and client.
Error log
The Error Log appears only if something has failed. It sits in a box of its own with lines above and below it and can be scrolled inside that box once it grows longer than the space on screen.
It shows two kinds of failure, and they differ in how far they reach:
| Heading | What failed | Reach |
|---|---|---|
| Currently n failed tasks | The task itself is disrupted, so it never got as far as the data | Operation in this area may be entirely at a standstill. That is exactly what the red note below the heading says |
| Currently n failed transfers | The task ran, but individual records did not get through | The rest of the execution is done. What is affected is what the list shows |
Both headings carry the line Status at below them, with the time at which the page read the state.
Why an execution can partly succeed and partly fail instead of aborting altogether is described under traces: the state hangs off the individual record and not off the execution, and whatever did not get through stays open and is picked up again on the next one.
How an entry is built
The failed transfers are not listed one by one but grouped, otherwise a larger execution would put hundreds of identical lines below one another. The staging runs from top to bottom:
- The task it happened on, as the group's heading.
- The short message below it, red and underlined. It is the kind of failure, Doppelte Produktnummer (duplicate product number) for instance. Error messages are rendered in German whatever language the interface is set to.
- The line State since, or State since … to … where there are several points in time, that is the period in which this kind of failure occurred.
- The message in plain words, with the actual value that caused it.
- The note below it, set smaller: what you can do about it.
- Last, in gray, the affected records, each with its number and, where the source delivered one, its designation.
Where one message affects more than one record, the count is added as … Items.
Two limits are built in so that the page still loads with a large failure picture: at most 500 transfers are evaluated in total, and where there are more, a red line says so explicitly. At most 100 records are enumerated per task, after which the link More n sits there and leads into the traces.
The list shows the current state, not the past. As soon as a transfer gets through, its entry disappears by itself. Whoever wants to know what failed earlier finds it in the traces.
Storage consumption
Below the log sits a line with the client's current storage consumption in megabytes and the share the media account for. The split is the interesting figure: in almost every client the images are the largest item, and whoever wants to save storage starts in the media area and not with the product data.
The line belongs to the error log and appears only together with it.
Further reading
- Traces (reference): where every single transfer sits with its history
- Channels and tasks (reference): where a disrupted task is inspected and restarted
- Traces (concepts): why the state hangs off the record and not off the execution
- The user interface: the navigation bar and how the other pages are built
- Access and client: how a client is created, who gets access, and how several clients relate