Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #6609

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions 10/umbraco-cms/reference/notifications/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -275,6 +275,17 @@ Useful for manipulating the model before it is sent to an editor in the backoffi

Umbraco uses notifications to allow people to hook into different workflow processes. This notification pattern is extensible, allowing you to create and publish custom notifications, and other people to observe and hook into your custom processes. This approach can be useful when creating Umbraco packages. For more information on how you create and publish your own notifications, see the [creating and publishing notifications](creating-and-publishing-notifications.md) article.

##Showing messages in the CMS
sofietoft marked this conversation as resolved.
Show resolved Hide resolved

You can inform the Umbraco user of the status of your notification by adding messages to the ```notification.Messages``` property.
sofietoft marked this conversation as resolved.
Show resolved Hide resolved

For example:
sofietoft marked this conversation as resolved.
Show resolved Hide resolved
```
notification.Messages.Add(new EventMessage("An Error occoured",
"Detail about the error",
EventMessageType.Error));
```

## Samples

Below you can find some articles with some examples using Notifications.
Expand Down
Loading