Discussion

The purpose of the discussion contributions (notes) is to record internal discussion – both managed and free.

The notes replace internal email communication, in comparison to which they bring advantages:

• Notes are kept and will be used in the future, e.g. in case of problem solving
• They can be read by workers who were not included in the original discussion, e.g. because they were not working at the company at the time
• They remain available even if the recipients and senders have left the company.

How news articles work

News articles are always related to a specific object – a product, an asset, a request, a task, etc. So it is always obvious what they are related to. News articles can be created in the discussion about a given object. You can open the discussion in the detail of the object by clicking . The discussion stays on the system permanently, or until the object it concerns is deleted.

News messages can also be addressed to people from the company. You can indicate to whom they should be addressed and these users will get them on the desktop in the message and discussion tab.

New messages are always automatically notified to the people affected by the object in the case of some objects (e.g. in a discussion about a task, everyone from the task team is informed).

If you respond to a post, both the sender and the recipients of the original post are always informed. You do not have the right to exclude them from the recipients.

Methodological note

Discussion contributions should be used instead of emails or other off-record communication if the workflow requires a revision. By keeping the discussion linked with the discussed subject, it is possible to prove later that the revision and – of course – revise the reason of the decision or any other subject of the discusion.

How discussion posts work

Posts relate to a given record – product, asset, request, task, etc. It is therefore always clear what they relate to. Entries can be created in the discussion of the object. The discussion can be opened in the object details with the button. The discussion remains permanently stored in the system, or until the object it refers to is removed.

(A special case is general discussions in the discussion area on the main dashboard. These discussions are themselves records on their own.)

Discussion posts can also be addressed to people in the company. It is possible to indicate to whom they should be addressed and these users will receive them on their desktops in the messages and discussions tab.

In the case of some objects, the people who are affected by the object are always automatically informed about new messages (e.g. in the discussion of a task, everyone in the task team is informed).

If you respond to a post, both the sender and the recipients of the original post are always notified. You do not have the right to exclude them from the addressees.

How people find out about a new post

They are notified of a post to the discussion:

• Automatically, the people responsible for the subject of the discussion. E.g. for a task, the people in the task team, for a request, the person responsible for the request.
• You can add recipients to the post who will be notified
• If you are responding to a post, those who were involved in the discussion thread will get the notification – either they are the authors or the addressees of previous posts

You can see the post notifications on the main desk under the bell in the New Posts section.

A post in a discussion is not a notification

Notifications of new posts are not forwarded to your email. If you create a notification for an object, the user will also receive it in an email (right away, or if they don't read it by the next day).

Discussion posts, on the other hand, are meant to be substantive discussions that users engage in when they can and should not distract them from other work.

Translated with DeepL.com (free version)

You may need to know

Discussion with people outside your company

News messages can also be used to communicate with people outside your company. However, this feature is not available by default. If you have it active, you can also include people from the company directory among the recipients and the post will be sent to them by email. This allows you to keep email communication with, for example, a customer.

Discussion is not generally public

Discussion is linked with object and users that have access to the object, have also access to the discussion. But it cannot be accessed by anybody else. No one call share the access to the discussion beyond the access rights managed by system rights.

Even when discussion is linked with contribution published on the public dashboard, the discussion is locked and never published.

What makes a discussion different from a reminder

Discussions and reminders are both a form of message; however, there are a number of fundamental differences between them:

• Reminders are not kept long-term; they are removed after a year. They are not intended to keep a long-term discussion.
• You address reminder exclusively to a single person, whereas a discussion post may have multiple readers. Discussion cannot be private, but reminder could
• Reminders cannot respond to each other; they are not intended to record and support a discussion.
• Reminders pop up on the recipient mobile (if they use an app), whereas a new discussion post does not. Discussion is not used for notifications and users notice them when they are working, or when they want to.