Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
As a System Admin I want to be notified via email about consecutive failures of SMS or e-mail messages.
Table of Contents |
---|
Lesson Outcomes
After this lesson you should:
- Have basic knowlegde of the
__sms_result_update__
and__scheduled_function_result_update__
built-in functionsobjects - Know how to use the
@OnSmsResultUpdate
and@OnScheduledFunctionResultUpdate
functions to create callback functions for scheduled function and SMS result updates
Modified or Added App Files
./model/objects/ScheduledFunctionFailureCounter.mez
./model/objects/SmsFailureCounter.mez
./services/ScheduledFunctionResultCallbacks.mez
./services/SmsResultCallbacks.mez
./web-app/lang/en.lang
App Use Case Scenario
A typical feature for many Helium apps is to have scheduled functions or to send outbound SMS messages. These operations are processed asynchronously on the Helium backend. For various reasons, however, scheduled functions and SMS messages might fail. For this reason Helium provides developers with a mechanism to keep track of the status of scheduled functions and SMS messages. This is achieved by providing two built-in objects, meaning they are inherently available in each app without developers needing to include them in the app data model, and two annotations for callback functions. The feature described in this lesson includes functionality where these callbacks are used to record consecutive failures of scheduled functions and SMS messages and to then generate a notification by e-mail for the attention of system admin users.
Built-In Objects
The following built-in objects will be referenced in this lesson:
__sms_result_update__
__scheduled_function_result_update__
These objects are discussed in more detail in Lesson 19. For this lesson we will simply refer to the success
attribute in both of these objects and the doneProcessing
attribute which is exclusive to the __sms_result_update__
function.
Annotations for Scheduled Function and SMS Result Update Callbacks
Firstly we need to add the following objects to our data model:
Code Block | ||||
---|---|---|---|---|
| ||||
persistent object SmsFailureCounter { int consecutiveFailures; int totalFailures; int totalSuccesses; datetime lastUpdate; } |
Code Block | ||||
---|---|---|---|---|
| ||||
persistent object ScheduledFunctionFailureCounter { int consecutiveFailures; int totalFailures; int totalSuccesses; datetime lastUpdate; } |
These objects will be used to record the total failures and consecutive failures of SMS messages and scheduled functions.
We now add two new units in presenter files under the services folder namely SmsResultCallbacks.mez
and ScheduledFunctionResultCallbacks.mez
respectively. We can now add our callback functions to these units:
Code Block | ||||
---|---|---|---|---|
| ||||
unit SmsResultCallbacks; @OnSmsResultUpdate void smsResultCallback(__sms_result__ smsResult) { // Get or create the counter even if we don't know whether there has been a failure yet SmsFailureCounter failureCounter = getOrCreateSmsFailureCounter(); // If a failure has occurred, record it if(smsResult.success == false && smsResult.doneProcessing == true) { failureCounter.consecutiveFailures = failureCounter.consecutiveFailures + 1; failureCounter.totalFailures = failureCounter.totalFailures + 1; failureCounter.lastUpdate = Mez:now(); } // Reset the consecutive failure count else if(smsResult.success == true && smsResult.doneProcessing == true) { failureCounter.consecutiveFailures = 0; failureCounter.totalSuccesses = failureCounter.totalSuccesses + 1; failureCounter.lastUpdate = Mez:now(); } // Alert all system admins of consecutive failures if(failureCounter.consecutiveFailures >= 5) { notifySystemAdminsOfConsecutiveFailures(failureCounter.consecutiveFailures); } } |
Code Block | ||||
---|---|---|---|---|
| ||||
unit ScheduledFunctionResultCallbacks; @OnScheduledFunctionResultUpdate void scheduledFunctionResultCallback(__scheduled_function_result__ scheduledFunctionResult) { // Get or create the counter even if we don't know whether there has been a failure yet ScheduledFunctionFailureCounter failureCounter = getOrCreateScheduledFunctionFailureCounter(); // If a failure has occurred, record it if(scheduledFunctionResult.success == false) { failureCounter.consecutiveFailures = failureCounter.consecutiveFailures + 1; failureCounter.totalFailures = failureCounter.totalFailures + 1; failureCounter.lastUpdate = Mez:now(); } // Reset the consecutive failure count else { failureCounter.consecutiveFailures = 0; failureCounter.totalSuccesses = failureCounter.totalSuccesses + 1; failureCounter.lastUpdate = Mez:now(); } // Alert all system admins of consecutive failures if(failureCounter.consecutiveFailures >= 5) { notifySystemAdminsOfConsecutiveFailures(failureCounter.consecutiveFailures); } } |
Note the use of the following:
@OnSmsResultUpdate
and@OnScheduledFunctionResultUpdate
annotations__sms_result__
and__scheduled_function_result__
functions parameterssuccess
anddoneProcessing
attributes
Info |
---|
Be sure to use the correct function signatures for your callback functions. |
Info |
---|
Keep in mind that only one callback function for SMS results updates is allowed. Similarly only one scheduled function result update callback function is allowed. |
Info |
---|
Helium performs multiple attempts to try and send SMS messages. If an SMS result update has a value for the |