...

preburstMessagesByDataGroup (Map of String to String List) Messages we send to each user the day before the study burst begins, keyed by data group. Each entry is a list of possible messages, and the worker picks one of those messages at random. This doesn't count against the notification limit. Example: {"gr_BR_AD", ["Time to complete the burst. If you log, it could possibly provide you with new insights about your health. Please do it right now or get into the habit of taking it after you taking your medications.", "Time to complete the burst. What you are doing right now is directly helping future parkinson's patients. Please do it right now or get into the habit of taking it after you taking your medications."], "gr_BR_II":["Time to complete the  burst. If you log, it could possibly provide you with new insights about your health. Remember that you thought the best time to this was", "Time to complete the burst.  What you are doing right now is directly helping future parkinson's patients. Remember that you thought the best time to this was"]}

requiredSubpopulationGuidSet (String Set) Set of subpopulations that the user needs to be a part of and consented to in order to receive notifications. This is useful if notifications is a separate consent. Otherwise, this is most likely just the study ID (default subpopulation). Example: "sage-mpower-2"

Example

In mPower 2.0, we currently set the following configuration values (to match the study burst schedule defined in Bridge server):

• burstDurationDays = 14
• burstStartEventIdSet = enrollment, custom:activityBurst2Start, custom:activityBurst3Start, ... , custom:activityBurst9Start
• burstTaskId = "study-burst-task"requiredSubpopulationGuidSet = "sage-mpower-2" (The default subpopulation, assuming every participant is eligible to receive notifications.)

Suppose we numMissedConsecutiveDaysToNotify=2 and numMissedDaysToNotify=3. Consider the following scenarios:

...