RecurrenceRule Table (207)

The recurrency pattern for a recurring event. Each recurring event has an appointment.recurrenceRuleId pointing to its pattern.

Fields

NameDescriptionTypeNull
RecurrenceRule_idPrimary keyPK
patternRecurrence pattern (daily, weekly etc)Enum RecurrencePattern
subPatternSubpattern (workday, everyday, weekday etc)Enum RecurrenceSubPattern
weekdaysWeekdays used, bitmask based on ERecurrenceWeekDays enumerationUShort
startDateStart date for repetition patternDateTime
endDateEnd date for repetition patternDateTime
cyclicDayEvery nth day, in cyclic patternsUShort
cyclicWeekEvery nth week, in cyclic patternsUShort
cyclicMonthEvery nth month, in cyclic patternsUShort
registeredRegistered whenUtcDateTime
registered_associate_idRegistered by whomFK associate
updatedLast updated whenUtcDateTime
updated_associate_idLast updated by whomFK associate
updatedCountNumber of updates made to this recordUShort

RecurrenceRule table relationship diagram

Indexes

FieldsTypesDescription
RecurrenceRule_idPKClustered, Unique

Relationships

TableDescription
appointmentTasks, appointments, followups, phone calls; and documents (document_id != 0). An appointment always has a corresponding record in VisibleFor specifying who may see this.
associateEmployees, resources and other users - except for External persons

Replication Flags

  • Area Management controlled table. Contents replicated to satellites and traveller databases.
  • Replicate changes UP from satellites and travellers back to central.
  • Copy to satellite and travel prototypes.

Security Flags

  • No access control via user’s Role.