This chapter contains the guidelines you must comply with if your application uses periodic execution for its SpotPass tasks. If your application performs periodic execution, you must comply with this chapter as well as with chapter 6.14 BOSS: Common Items.
If your application performs both periodic and immediate execution with the same NADL task, you must also comply with 6.16.3 Displaying Errors during Immediate Execution.
6.15.1 NADL Task Settings for Periodic Execution
Use the following NADL task settings for periodically-executed tasks.
Item |
Value to set |
---|---|
Execution interval |
Set a value between 1 and 168 hours (approximately one week). |
Execution count |
Set a value between 1 and 100. |
Execution priority |
Use the default value of PRIORITY_MEDIUM. Contact Nintendo at support@noa.com before setting any other value. |
Access point information |
Do not provide this information. Contact Nintendo at support@noa.com before using NADL tasks that provide access point information. |
Task permissions |
Set a value of TASK_PERMISSION_IN_PARENTAL_CONTROL. Although this is the default value, set it explicitly using the SetProperty function of the nn::boss::TaskPolicy class. |
Task ID |
Use the task ID that you used on your application to Nintendo. |
6.15.1.1 Compliance with NADL Task Settings for Periodic Execution
Guideline Item |
NADL task settings must follow the standards established by Nintendo. |
---|---|
Software to Be Tested |
Applications that register NADL tasks for periodic execution. |
Test Method |
After an NADL task has been registered with the application, use BossLotcheckTool to check the value of each setting. |
Pass/Fail Determination |
Passes if all of the following conditions are met.
|
6.15.2 Distribution Intervals for Periodic Execution
Abusing the ability to distribute content via NADL tasks raises a number of concerns, such as that overuse would weaken user interest in such content, degrade the value of the distribution feature, and fill up users’ storage space too quickly. The Notifications applet in particular can only display up to 100 messages. Consequently, we request that you don't distribute more than one notification per week. When an application registers multiple NADL tasks and some of those distribute notifications, limit notifications to one per week for the whole application, not just for individual NADL tasks. If you plan to distribute notifications in excess of one per week, contact Nintendo at support@noa.com in advance, and also indicate that you plan to exceed this limit when applying for use of the feature on OMAS.
There are no specific restrictions for data distribution, but abuse of data distribution would lead to the same concerns as for notifications. Consequently, configure your application to distribute data at appropriate intervals in accordance with section 6.15.1 NADL Task Settings for Periodic Execution.
Configure the execution interval and execution count based on two criteria: how long you want to provide a service, and how long you want NADL tasks to persist. The execution interval serves as a standard for the maximum amount of time that it will take the user to get data after it has been updated. However, this is not necessarily true when the user is not connected to the network.
For example, with an execution interval of 1 hour and an execution count of 100, most users will have been notified by 1 hour after data is updated. However, because the NADL task only runs for approximately four days (once an hour for 100 hours), it becomes difficult to send information to users who have not played your game for some time. On the other hand, you could set a long execution interval but this would be problematic because it would prevent data from being distributed in a timely fashion.
To send data in a timely manner (to some extent) while still allowing NADL tasks to run for a long time, set the execution interval equal to 4 hours and the execution count equal to 100. By doing so, you can configure NADL tasks to run for two weeks.
No required guideline items.