Task: Concept: Activity Log

[enrico-kaack-comp]

Understand the Task

While discussing #145 we basically identified different problems that were part of one ticket, so we split it up.

Description
As a user, I want:

1. not miss any notifications for errors, warnings etc and if i accidently closed those, want to be able to look them up
2. want to have a log of activities i performed in the UI.

The idea would be an Activity Log, that contains all the error messages, success messages etc. that we show over all the places, consolidated into one place. Additionally, we would also define how we want to show different events/messages to the user (e.g. disappearing notification, sticky notification, dialog etc).

This needs some concept work that should be outlined here and then discussed in refinement.
I would say we need a clear structure of different types of events we have to the user, what level of importance they have.
We want to define how we show those to the user depending of these types, creating different categories.

With this concept in place, we can than move on, discuss and implement this approach.
Additionally, we feed this information into sentry as it will help us in error debugging.

Any further valuable resources.

• Fiori Message Strip: https://www.sap.com/design-system/fiori-design-web/ui-elements/message-strip/?external
• Fiori Message Handling: https://www.sap.com/design-system/fiori-design-web/foundations/best-practices/global-patterns/messaging/messaging?external
• Fiori Notification: https://www.sap.com/design-system/fiori-design-web/ui-elements/notification-center/?external

What is required to accept the Task as done.

Done Criteria

• List all possible events (e.g. errors, creation events, deletion events, all editing events, informational events...)
• Clear categorization of those that also includes how we show those to the user (e.g. error as dialog, information in activity log only, other types maybe as notification/messages that needs to be closed manually)
• Find a place in the ui to put the Activity Log
• What information to show in the activity log

[andreaskienle]

Before we start discussing solutions, could we compile a brief list of messages that we would like to capture? Not a complete list, just a few representative examples?

From what I can see: We show (automatically disappearing) toast messages when:

• copying something to clipboard
• an asynchronous action was triggered, e.g. creating or deleting entities ("Project creation triggered. The list will refresh automatically once completed.")

We also have error messages that appear in dialogs, e.g. when something went wrong trying to create a new project (we just show the error from the backend). Here, for example, when I tried to create two MCPs with the same name:

Do we have use cases where we show error or warning messages that users could potentially miss?

[enrico-kaack-comp]

We dont really see a need for this right now. As this issue was originally brought up by @GenosseOtt for the urgency/importance.

We already increased the toast time.