How do I configure a "Notify by Answer Value" Action within a Rule?

Created by Mark Eves, Modified on Fri, 6 Jan, 2023 at 5:05 PM by Alfie Jennings

Notify by Answer




Using the ‘Notify by Answer Value’ Action within a Report Rule enables notifications to be sent to a value e.g. an email address, derived from a question/answer value in a Form. This could enable non-registered customers to receive notifications from the platform for instance. It is recommended the use of this feature is considered before implementing for each Form to reduce any unnecessary duplication of notifications to customers. For further advice please contact the Abavus support team.



Key Objectives:-


  1. Define Item to capture Notification 
  2. Define Rule



Pre-Requisites:-


  • Basics
  • Forms
  • Rules


 

1. Defining an item to capture notification details



In the appropriate Form two items are required:-



1. Name - typically a Textfield item. This can be populated using Dynamic Fields.


2. Email or Phone Number - typically a Textfield item. This can be populated using Dynamic Fields. Apply the appropriate access levels to each item.


 



 


2. Define Rule


 


Within an appropriate report rule, add the Action ‘Notify Person’:-


1. SELECT NOTIFICATION TYPE.


2. SELECT ‘NOTIFY BY ANSWER VALUE’.


3. SELECT FIRST NAME ITEM (FROM NAME ITEM CONFIGURED IN FORM)


4. SELECT NOTIFICATION EMAIL OR NUMBER FROM ITEM CONFIGURED IN FORM CONTENT TYPE


5. SELECT APPROPRIATE CONTENT TYPE 


 


It is recommended that the Content Type ‘Free Text’ is used. If Report Content is specified the email will be visible with the Customer ‘Mr Anonymous Citizen’.


 


From within the History section of a Service Request details of the Report Rule and notification will be visible:-



 


 







Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article