Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
In an upcoming video tutorial that I'm putting together this month, I'll be continuing the theme of extensibility and customization in Telerik Sitefinity.
The Sitefinity forms module allows users to subscribe to be notified when a visitor submits a response. It's a great feature, but if the forms your users subscribe to are frequently filled out, the notifications will start filling up their inbox faster than they can look through them. Even worse, if only a fraction of the responses are actually relevant, the frequent notifications quickly become a nuisance and will drown-out the important ones.
In the upcoming tutorial, I'm going to show you how it is possible to reduce (or completely eliminate) unwanted form notifications by customizing the way they are sent. Taking it a step further, we are going to use the Sitefinity GeoLocation API to give the notifications more relevance by identifying which Sitefinity users should receive them in the first place.
I'll be talking through (and building) a solution to the following list of requirements.
"When a visitor submits an entry through a specified form, a notification should be sent to a custom list of recipients."
"The notifications should be sent regardless of whether the selected users have subscribed to be notified about submissions from that form or not."
"If a user is already subscribed to receive notifications about the specified form, duplicate notifications should not be sent."
"The list that is used should be the one that is geographically closest to the visitor who submitted the form response (based on zip code)."
Even if this isn't something you are working through right now, you’ll be introduced to some pretty powerful customization techniques that can be used and expanded upon in future projects. You won’t want to miss it.
UPDATE: The video thing didn't quite work out as planned but there's good news! The code for this has been released to the public and is available on GitHub. Make sure to check out the README near the bottom of the page.
View all posts from Tim Williamson on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.