Skip to content

Building an Instance Tree Detail View

Info

New in Atfinity 17.

The detail view of an instance tree page is what a user gets when they pick an instance from the list. It is a grid of widgets, it can be split into several tabs, and widgets are placed, sized and named as they are on an insights page. The widget types are different ones: charts, metrics and tables are not available here, and the three below exist only here.

Settle the branches first, since a list of cards is built on one.

Add an info list

An info list shows information of the page ontology, read from the instance the user opened, and users cannot change it there. A file field is offered as a download rather than as a value. Alongside the fields, an info list can hold buttons that start a case or run a manual instance action on the instance.

Everything has to fit. The room an info list has is its width times its height minus two rows, and a list holding more items than that is rejected when you put the configuration live, so make the widget bigger or split the list in two. An info list with no items is not shown to users at all, while an empty list of cards and an empty interaction log still are.

Add a list of cards

A list of cards shows one card per record its source resolves to. Pick the source first, either one of the branches or Cases, because it decides what a card can show and there is no way to reach past it:

  • A role or relationship branch offers the information of the ontologies that can appear at the end of it, plus the ID of the instance.
  • A structure branch offers the name of the occurrence and the fields inside that structure.
  • Cases offers the attributes of a case, such as its process, workflow state and assignee, and no information.

Filters follow the same split. A role or relationship branch can be filtered by the fields of the ontologies at the end of the branch and by six standard attributes: creation date, ID, name, owner, owner user groups and last update. Nothing else is offered, so the filters of a case list are not available. A structure branch offers no filters at all.

Changing the source later deletes the fields and the filters you configured, so treat the source as the first decision rather than something to try out.

Add an interaction log

An interaction log is the one widget users write to. They record an interaction with a type (call, meeting or email), a time and a description. It has no source, no fields and no filters, only a name and a description, and it always shows every interaction on the instance, so a second one on the same page repeats the first.

Everyone who can open the page sees every interaction on that instance, and only the author of an interaction can change or delete it. Adding, changing and deleting one is recorded in the history of the instance, so it stays visible who logged what.

Put values in the title line

Next to the name of the instance, the detail view can carry up to three further values, which you switch on and select per page. Choose what a user needs at a glance, for example a client number and a risk rating. Only information a single line can carry is offered, so files, rich text, JSON and structures are not.

Before you put it live

Four things are worth a last look:

  • The page needs columns for its list, like any other page that lists instances.
  • A title line that is switched on has to hold between one and three pieces of information.
  • No info list holds more items than it has room to show.
  • A page you copied keeps the fields of every list of cards but not its source, which falls back to Cases, so point each of them at a branch again.