REST API create schedule

Hi

i play a bit with the REST API and tried to create a schedule.

I noticed that for /dp-gui/dp-scheduler-gui/restws/schedule the example shows the following:

{
  "id": "string",
  "disabled": true,
  "jobId": "string",
  "dpName": "string",
  "dpType": "full",
  "dpProtection": "None",
  "dpProtectionParam": "string",
  "dpKeepCatalog": "string",
  "dpKeepCatalogParam": "string",
  "dpLoad": "high",
  "dpPriority": 0,
  "pauseLowerPriorityJobDisabled": true,
  "timeZone": "string",
  "startDate": "2017-10-26T00:00:00",
  "endDate": "2017-11-15T01:23:34",
  "recurrenceType": "ONCE",
  "everyNth": "string",
  "fromTimeOfDay": "string",
  "toTimeOfDay": "string",
  "dayOfMonth": "string",
  "month": "JAN",
  "daysOfWeek": [
    "MON"
  ],
  "nthDayOfWeekInMonth": "FIRST",
  "expectedDurationMillis": 0,
  "cronString": "string",
  "state": "ACTIVE",
  "overlappingIds": [
    "string"
  ],
  "holidaysEnabled": true,
  "debug": {
    "enabled": true,
    "filename": "string",
    "startRange": 0,
    "endRange": 0
  },
  "rest": [
    {
      "rel": "string",
      "href": "string",
      "type": "string",
      "hreflang": "string",
      "title": "string",
      "length": "string"
    }
  ]
}

Do i really have to set all the "string" fields? Like the ID and JobID and all the other obtions?

Can someone post an example of the creation process of a scheudle via REST?

Via omnidbutil a schedule is creates just with:

omnidbutil	-create_schedule	-spectype Backup 	-apptype Filesystem	-specname �talistname%	-dpName �talistname%	-dpType full	-recurrenceType WEEKLY	-startDate YYYY-MM-DD	-startTime HH:MM	-everyNth 1	-month MAY	-daysOfWeek MON