To simplify the first steps in Woost, we added a basic tutorial. You
can find it by navigating to the entry page of Woost
(app.woost.space), e.g. by clicking the logo in tho top-left corner.
By clicking the “Show me the basics” button, the tutorial leads
you through your first steps. We hope you enjoy it :-)

Use the profile image feature to add a more personal touch to your collaboration. It also eases identification for your colleagues, e.g. when assigning tasks.

You can access your profile by clicking your name in the top bar. With another click on the paper clip next to your username you can select a profile picture via your file browser.

Woost offers the ability to export a table using the CSV format. This exported table can then be imported into Excel to use its expressiveness, calculation power or to get business insights.

To export the table, just scroll to the very right of the table view and hit the export button.

We noticed that our notification view can be improved. People consume information differently – and a notification system should keep that in mined. Therefore, we added a notification stream and improved the previous notification tree view.

Self Experiment: Our experiments with this new system let us again realize that Woost combines communication and collaboration. For us, the notification view worked best with messages while the notification stream satisfied the needs with task and notes.

By using HTML and CSS you can build complex notes, description and Wiki articles. One example is to set up a nice description of a Coaching. By combining them with template automations and variables, you can build pretty designed automation notes.

Hint: The code will be sanitized, so Javescript is not possible.

We are getting serious with our flexibility and expressiveness of automations by introducing template references. In its current version, the interface might be a bit confusing due to its complexity, but once you are familiar with it, you will love the gained flexibility.
In a template, you have the possibility to reference a node in another template. This may be a subtask, a chat message or a project that is generated in a previous automation. Hence, you are able make statements like: "This automation should be applied on result X of a previous automation".

To do so, you have to rebuild the hierarchy of the card in the template. Then, you can choose a reference of e.g. a subtask to a subtask of another template and automate it. You can delete tasks or mark them as done.

For the explorer: Are you able to find out how to move a node within the hierarchy?

Whenever you work with data or properties, you will likely use the new placeholder capabilities of Woost. Using placeholders, you can define your structure and necessary properties in a card. This makes adding properties charmingly simple.

We are introducing template variables allowing you to use properties of cards in automations. This allows the automatic generation of forms, chats or notes that reference these properties.

Up to now, the syntax is very raw. The reference has to be embedded into ${woost.X} , where X is the relative path from the template. As a first example: To reference a property Department in a chat message of the same card, you can use ${woost.parent.field.Department}. You can understand it the following way: The parent of the chat message is the card. The same is true for the property. Therefore, you reference the card (the parent) and then choose a field of the card with the name Department.

For the wild: Using $@{woost.parent.field.Department} you can automate mentions ;-)

If you have a suggestion for a new feature, you can tell us by clicking Feedback/Support > Vote on Features. You can also vote on features suggested by others, so we know what our users want the most.

If you have a question, a problem, want to give feedback or just want to chat with us, you can use our integrated support chat. You can open it at the top under Feedback/Support.