...

Interval, possible values:

Interval is coded as a string. These values are shown to the user:

None - I will backup manually
12:00AM - 12:29AM
12:30AM - 12:59AM
1:00AM - 1:29AM
1:30AM - 1:59AM
2:00AM - 2:29AM
2:30AM - 2:59AM
3:00AM - 3:29AM
3:30AM - 3:59AM
4:00AM - 4:29AM
4:30AM - 4:59AM
5:00AM - 5:29AM
5:30AM - 5:59AM
6:00AM - 6:29AM
6:30AM - 6:59AM
7:00AM - 7:29AM
7:30AM - 7:59AM
8:00AM - 8:29AM
8:30AM - 8:59AM
9:00AM - 9:29AM
9:30AM - 9:59AM
10:00AM - 10:29AM
10:30AM - 10:59AM
11:00AM - 11:29AM
11:30AM - 11:59AM

We will encode these for passing back and forth as zero-padded, military time, first four characters of the string to the api:

None
0000
0030
0100
0130
0200
0230
0300
0330
0400
0430
0500
0530
0600
0630
0700
0730
0800
0830
0900
0930
1000
1030
1100
1200
1230
1300
1330
1400
1430
1500
1530
1600
1630
1700
1730
1800
1830
1900
1930
2000
2030
2100
2130
2200
2230
2300
2330

delete()

Arguments for delete:
netid of owner
nodename (needs to be unique, and exist)
datestamp for date to delete, formatted as Oracle date (31-JAN-13). This is awkward for ServiceNow, but native for NetBill. Furthermore, ServiceNow already has a method that does this for previous Oracle interactions.

...