# Class: CreateRecurringEntryRequest

## tibco.objectapi.service.request.CreateRecurringEntryRequest

#### new CreateRecurringEntryRequest(name, version, description, startDate, duration, recurRule, responseStartDate, responseEndDate)

Object CreateRecurringEntryRequest Usage: `RestApiService.getWorkCalService().createRecurringEntry(request, callback);`

##### Parameters:

Name | Type | Description
--- | --- | ---
`name` | string | Name of the calendar to which the exclusion is being added (within the given namespace).
`version` | number | (Java type: int) The version number used to detect concurrent updates to the same calendar; also known as optimistic locking.
`description` | string | A description of the new exclusion.
`startDate` | string | (optional) The date and time when the new recurring exclusion starts.
`duration` | string | (optional) The length of each occurrence of a recurring exclusion (as defined in RFC-5545.
`recurRule` | string | The recurrence rule. This is the expression used to define a recurring calendar exclusion. The format of the rule is defined as in RFC-5545. See Adding Recurring exclusions for more information on recurring exclusions.
`responseStartDate` | string | The start date-time for which entries should be included in the response.
`responseEndDate` | string | The end date-time for which entries should be included in the response.

Since:
  - 4.0.0

### Members

#### allDay :boolean

Query parameter: 'allday' (optional, default=false) (boolean) Indicates whether this entry lasts the entire day. If false, the start and end time are determined by the given start and end date.

##### Type:

- boolean

Since:
  - 4.0.0
Default Value:
  - = false

#### namespace :string

Query parameter: 'namespace' (optional) The combination of namespace and name uniquely identifies a calendar. Note that the default SYSTEM calendar has no namespace.

##### Type:

- string

Since:
  - 4.0.0