Flow: the object card

SENSEVER

The official Sensever channel: guides and API documentation for Chat, Requests, Flow, Studio, bots and messaging channels.

12 min read

Flow: the object card

The card is the page of a single object: a task, a deal, a ticket, or an object of your own type. In it you change fields and the assignee, write the description, manage subtasks and checklists, move the object through statuses, add files, discuss it in chat, track time and see what has happened to it. This article covers the card and creating an object. How types and fields work is explained in Flow: object types and fields, and statuses in Flow: statuses and the process editor.

Creating an object

The "Create" button is in the header of a type's table, board and calendar, and on the workspace home page it sits next to the object list (with several types, each one has its own "Add" link). In the calendar, clicking a day opens the creation form with that date. In "All workspaces" mode, Flow first asks which workspace and which type to create the object in.

The "New object: …" form contains:

  • the title;

  • a date right below the title: the "Deadline" field, or, if there is none, the first "Date" field (when creating from the calendar, the calendar's field and day);

  • the type's other fields according to the published schema, with required ones marked with an asterisk; checklist items and tags can be entered right away;

  • relation fields with a "Select" button that searches for an object of the right type;

  • "Assignee" — you by default.

The "Create" button saves the object, and "Cancel" returns you to the list. If the server rejects the data, the error appears next to the field it belongs to.

An object with just a title is quicker to create right in the table or in a board column — with the "Add" row or the N key; see Flow: table, board, calendar and filters.

How the card is laid out

Part

What's in it

Header

The path back (to the type's list, to the workspace's "All objects" or to "All workspaces" — wherever you came from), the object's status, and the "Archive" or "Restore" button

"Change status · Actions"

An expandable row with transitions to other statuses and the object's actions

Main form

The title; on the left, people and dates — "Assignee", "Watchers", "Author", "Workspace", "Created", "Updated"; on the right, the date under the title, the recurrence row and short fields; below, long fields (the description), "More fields · N", and the "Undo" and "Save" buttons

"Subtasks"

The object's subtasks — if the type has them

Checklists

A separate block for each "Checklist" field

"Files"

The object's attachments

"Comments"

Discussion of the object in Sensever chat

Right column

"Processes", "Relations", "Time", "Deadlines (SLA)", "Statuses", "History"

Next to the name of the assignee, the author and people in the history you see their Sensever profile photo, or their initials if there is no photo. The workspace shows its icon.

An administrator sets which fields are shown right away: type settings → the "Card" tab. There you choose the "Date under the title" field and up to 20 "Card fields". The remaining fields stay in the card under the "More fields" button. Instead of a date under the title you can choose "Date created" — then there is no separate date at the top. Short fields (string, number, date, select, tags) sit in the properties column, and long ones (text, JSON) span the full width below them. The "Start date" field (start_date) in templates is a regular card field; together with the deadline it defines the bar in the calendar and on the timeline.

Editing fields

Change the values and click "Save"; "Undo" brings back the saved values. Only the changed fields are saved.

  • The type's published schema decides which fields are required and which values are allowed. Errors appear next to the field.

  • If another person or a process changed the object in the meantime, the card shows: "The object was changed by another user or a process. The latest version is shown — check the data and try again." Your edits never overwrite someone else's.

  • You can't change a field your role has no write permission for; a field without read permission isn't shown in the card.

  • At the bottom of the right column you see the object's "Version" and the version of its schema. An object stays on the schema version it was created with until an administrator moves it to a new one.

Description

"Text" fields — such as a task description — use the same editor as messages in Sensever chat. Text is shown formatted as you type: a formatting toolbar appears above selected text, and chat shortcuts work — Ctrl+B (bold), Ctrl+I (italic), Ctrl+K (link) and others. Unlike chat, Enter inserts a line break, and there are no attachments or sending — the description is saved with the "Save" button along with the other fields. In tables and the history, the description is shown as plain text.

Type @ in the description to mention someone who can see the object — they get a notification. Learn more in Flow: mentions.

Subtasks, checklists and tags

  • "Subtasks" is a block under the form if the type has subtasks. It lists subtasks with their statuses and a "closed/total" counter; the "New subtask and Enter" row creates a subtask of the same type. A subtask itself has a "Parent task:" link at the top.

  • Checklists — a block for each "Checklist" field: items are checked off with a checkbox, the "New item and Enter" row adds an item, and the item menu has "Rename", "Move up", "Move down", "Make a subtask" (if the type has subtasks) and "Delete". A checked item remembers who checked it and when. A checklist holds up to 100 items. Items are saved immediately, without the "Save" button.

  • Tags — a field with colored chips: Enter or a comma adds a tag, and suggestions are tags already used in the type. Up to 20 tags of 50 characters each.

Details are in Flow: subtasks, checklists and tags.

Recurrence

Under the date in the fields column is the recurrence row. Without recurrence it is a "Repeat" button; a recurring task shows the rule in words, the date of the next task, "Edit" and "Stop repeating". How to set up recurrence is described in Flow: recurring tasks.

Time

The "Time" block in the right column shows how much time has been spent on the object (and on linked child objects), "Planned / actual" against the estimate field, the timer and entries; you can also add time manually. The block is visible if you can log time or entries already exist. Learn more in Flow: time tracking.

Assignee

The "Assignee" is the person responsible for the object. On creation, the author becomes the assignee unless someone else is chosen. In the card, anyone with permission to change the object can change the assignee: choose a person and click "Save". Without permission the card replies: "You don't have permission to change this object's assignee." The "Viewer" role has no choice here.

A change of assignee is recorded in the history. In workspaces created from templates, the new assignee gets a "You were assigned" notification — if someone else assigned them, not they themselves. Learn more in Flow: notifications and reminders.

If a member's role only allows changing their own objects, after handing a task over to a colleague they can no longer change it — except for tasks they created themselves.

Watchers

"Watchers" are people who follow an object without being responsible for it. In the card, this field sits next to the assignee. Watchers receive notifications from rules that list them as recipients: for example, in the "Tasks" template — when a task is done and when it is unblocked, and in the "CRM" template — when a deal is won.

The field exists on tasks and deals in workspaces created from the "Tasks" and "CRM" templates and on tasks in the Main workspace. You can add it to your own type yourself: a field with the key watchers and the "Members" type. Watchers are free: they aren't counted as staff in Flow billing.

Statuses and actions

The "Change status · Actions" row expands into buttons:

  • transitions — "transition name → new status";

  • object actions — buttons the administrator set up in the type (for example, filling in a form of fields or starting a process).

An unavailable button is marked with a lock. Click it and Flow explains why: no permission, the transition doesn't run from the current status, a required field is empty, or a rule condition isn't met. If a transition has a form (fields to fill in during the transition) or rejection reasons, a window opens with a "Move" button and a "Comment" field; the comment goes into the history.

Before a transition, save or discard your field edits — otherwise Flow asks you to: "Save or discard your field changes first." You can't change the status by simply editing a field: only through a transition.

Files

The "Files" block holds the object's attachments. "Add" uploads one or more files, clicking a name downloads the file, and the trash icon deletes it after confirmation.

  • Anyone who can see the object can see and download its files. Anyone who can change the object can add and delete them.

  • A download link is issued for 5 minutes and only after a permission check every time: a person who has lost access to the object won't get a new link.

  • An object can have no more than 100 files. A single file can be up to 2 GB (the Sensever Storage limit).

  • Files are kept in Sensever Storage and count toward the workspace owner: their Storage space and their quota, no matter who uploaded the file. If space runs out, the upload stops with an explanation. When the workspace owner changes, the whole volume moves to the new owner.

  • For an archived object, files are hidden ("The object is archived: files are hidden."), and they become visible again after it is restored. Deleting a workspace also deletes its files.

Files are scanned by Storage, so after upload a file may show "Verifying…" for a few seconds.

Discussion in chat

The "Comments" block is the discussion of the object. It is a private conversation in Sensever chat tied to the object: each object has its own. The input field and the send button are the same as in chat.

  • Anyone who can see the object can read and write.

  • Whoever writes in the discussion becomes a member of that chat conversation: it shows up in their Sensever and they get notifications about new messages. The "Open in chat" link in the block header opens it in chat; it appears once the discussion has started.

  • Type @ to name someone who can see the object: the mentioned person is added to the conversation and gets a notification, even though the discussion is private. Learn more in Flow: mentions.

  • Losing access ends participation. When a person is removed from the workspace, loses their role or has their permissions changed so they can no longer see the object, Flow removes them from the conversation within seconds (in the worst case, about a minute). If access returns, simply open the discussion again.

Relations

The "Relations" block is shown if the type has relation types (the "subtask — parent" relation is shown in the "Subtasks" block, not here). Each relation is visible from both sides, and each side has its own name: for example, in the "Tasks" template the relation is called "Blocked by" on one task and "Blocks" on the other.

  • "Add" opens a search for an object of the right type.

  • The cross next to an object removes the relation.

  • An archived object is marked "archived".

The server checks how many relations are allowed, whether cycles are forbidden and who can change relations; if it refuses, you see the reason ("The allowed number of relations is exceeded.", "The relation creates a cycle.").

Processes

The "Processes" block appears once processes have been run on the object. For each one you see the process key and version, its status ("running", "completed", "error", "cancelled"), and the start and end times. A running process shows its current steps, the external events it is waiting for, approvals with the participants' decisions, and a "Cancel" button. Cancelling removes steps, waits and approvals, but doesn't roll back actions already performed. Learn more in Flow: processes and approvals.

Deadlines and statuses

  • "Deadlines (SLA)" — running deadlines with a countdown ("until …", with a "business time" mark on deadlines counted in business time) and breached deadlines marked "breached". The block is visible only when such deadlines exist.

  • "Statuses" — which statuses the object has been in and how long it spent in each, with the current one marked "now". "Totals by status" sums up the time and the number of entries into each status. If the beginning of the history wasn't preserved, a note under the list says so.

How to set deadlines and business hours is described in Flow: reports, SLA and business calendar.

History

The "History" block lists all changes to the object, newest first: creation, field changes (before → after), assignee changes, transitions with comments, adding and removing relations, archiving and restoring, and moving to a new schema version. Each entry shows who (with a photo or initials) and when. The "Earlier" button loads older entries. Changes made by rules are labeled "automation" or "process" along with the name they acted on behalf of.

Archive and restore

"Archive" removes an object from regular lists without deleting it. For an archived object:

  • fields, status, relations and files can't be changed ("The object is archived: changes are unavailable.");

  • running processes are cancelled, and reminders and SLA deadlines are removed;

  • the history and the discussion are kept.

"Restore" brings the object back. Cancelled processes don't resume, and reminders are set again only for future deadlines. If a relation rule requires archiving linked objects together and there are many of them, archiving continues in the background. If a relation rule forbids archiving an object while it has linked objects, Flow tells you so.

What's next

Comments

Authors