-
Notifications
You must be signed in to change notification settings - Fork 806
new tutorial #22895
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
Merged
+79
−0
Merged
new tutorial #22895
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
61896c9
new tutorial
christiansavchev 6d4d2cf
New tutorial publishing
christiansavchev 8530d25
revised
christiansavchev 4c47f9d
revised
christiansavchev 306985b
revised
christiansavchev d284817
revised
christiansavchev e614874
fixed title and description
christiansavchev 26c6799
new tutorial
christiansavchev c435499
revised
christiansavchev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
41 changes: 41 additions & 0 deletions
41
tutorials/create-condition-all-notifications/create-condition-all-notifications.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
author_name: Christian Savchev | ||
author_profile: https://github.com/christiansavchev | ||
title: Create a Condition to Catch All Notifications | ||
description: This tutorial will teach you how to create a condition | ||
keywords: tutorial | ||
auto_validation: true | ||
time: 10 | ||
tags: [ tutorial>beginner, software-product-function>sap-btp-cockpit ] | ||
primary_tag: software-product>sap-btp--cloud-foundry-environment | ||
parser: v2 | ||
--- | ||
|
||
# Create a Condition to Catch All Notifications. | ||
<!-- description --> The condition is an entity in Alert Notification that represents under what condition one event is matched for delivery. | ||
jmmargo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
## Prerequisites | ||
- Tutorial: You have activated **Alert Notification** in a trial account as described in [Set Up SAP Alert Notification service for SAP BTP for Initial Use](set-up-alert-notification) | ||
|
||
## You will learn | ||
- How to create a condition with an event property **Category**, predicate **Is Equal To** and value **NOTIFICATION**. SAP Alert Notification service for SAP BTP uses this condition to filter all relevant events regarding notifications | ||
|
||
## Intro | ||
> If you want to use other conditions, see the SAP Alert Notification Service for SAP BTP documentation at [Managing Conditions](https://help.sap.com/docs/ALERT_NOTIFICATION/5967a369d4b74f7a9c2b91f5df8e6ab6/35ca5de101fc4d5791cdbb2df15e9d9b.html?locale=en-US). | ||
|
||
### Create a condition | ||
|
||
1. Open the **Conditions** menu on the Alert Notification cockpit page and click on the **Create** button. | ||
|
||
 | ||
|
||
2. Once the **Create Conditions** dialog opens, enter the following: | ||
* A unique name for your condition in the **Name** field. | ||
* [Optional] You can add additional details about the condition in the **Description** field and assign one or more labels to your condition in the **Labels** field. | ||
* In the **Condition** field choose the **Category** option in the first box, **Is Equal To** in the second box, and in the third box set the value to **NOTIFICATION**. | ||
|
||
 | ||
|
||
3. Click on the **Create** button. Your newly created condition is now available in the **Conditions** menu. | ||
|
||
 |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
38 changes: 38 additions & 0 deletions
38
tutorials/create-condition-notifications/create-condition-notifications.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
--- | ||
author_name: Christian Savchev | ||
author_profile: https://github.com/christiansavchev | ||
title: Create a Condition to Catch All Notifications | ||
description: The condition is an entity in Alert Notification that represents under what condition one event is matched for delivery | ||
keywords: tutorial | ||
auto_validation: true | ||
time: 10 | ||
tags: [ tutorial>beginner, software-product-function>sap-btp-cockpit ] | ||
primary_tag: software-product>sap-btp--cloud-foundry-environment | ||
parser: v2 | ||
--- | ||
|
||
## Prerequisites | ||
- Tutorial: You have activated **Alert Notification** in a trial account as described in [Set Up SAP Alert Notification service for SAP BTP for Initial Use](set-up-alert-notification) | ||
|
||
## You will learn | ||
- How to create a condition with an event property **Category**, predicate **Is Equal To** and value **NOTIFICATION**. SAP Alert Notification service for SAP BTP uses this condition to filter all relevant events regarding notifications | ||
|
||
## Intro | ||
> If you want to use other conditions, see the SAP Alert Notification Service for SAP BTP documentation at [Managing Conditions](https://help.sap.com/docs/ALERT_NOTIFICATION/5967a369d4b74f7a9c2b91f5df8e6ab6/35ca5de101fc4d5791cdbb2df15e9d9b.html?locale=en-US). | ||
|
||
### Create a condition | ||
|
||
1. Open the **Conditions** menu on the Alert Notification cockpit page and click on the **Create** button. | ||
|
||
 | ||
|
||
2. Once the **Create Conditions** dialog opens, enter the following: | ||
* A unique name for your condition in the **Name** field. | ||
* [Optional] You can add additional details about the condition in the **Description** field and assign one or more labels to your condition in the **Labels** field. | ||
* In the **Condition** field choose the **Category** option in the first box, **Is Equal To** in the second box, and in the third box set the value to **NOTIFICATION**. | ||
|
||
 | ||
|
||
3. Click on the **Create** button. Your newly created condition is now available in the **Conditions** menu. | ||
|
||
 |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.