From ae8a77b4f3959f1381e17de33ecd30a22425b707 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Sun, 6 Mar 2022 20:47:51 +0000 Subject: [PATCH] --- docs/8.0/ayanova/docs/customer-notify-subscriptions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/8.0/ayanova/docs/customer-notify-subscriptions.md b/docs/8.0/ayanova/docs/customer-notify-subscriptions.md index 124ccaca..e45c25a2 100644 --- a/docs/8.0/ayanova/docs/customer-notify-subscriptions.md +++ b/docs/8.0/ayanova/docs/customer-notify-subscriptions.md @@ -135,9 +135,9 @@ In the case of an event that can have a report associated with it, you can selec ### Object Tags -Here you can _filter_ by selecting one or more [Tags](ay-start-form-tags.md) (if the event is related to a taggable object) to include or exclude specific objects. +Here you can _filter_ by selecting one or more [Tags](ay-start-form-tags.md) to include or exclude specific objects. -For example, you could create a subscription to the Object Created event, select the type as Customer and the Tag as "residential". That way any Customer created and saved with the Tag "residential" will trigger a notification to you but if a Customer is created without the tag "residential" you will not be alerted. +For example, a Quote status change event notification can be restricted to only be sent when a quote contains the tag "notify". **All** the tags selected in the subscription are required to be on the object at the moment it is saved / updated / deleted in order to match the subscription requirements and trigger notification. If other tags are on the object besides the ones related to this filter they have no effect on the notification filter.