• Share
    • Twitter
    • LinkedIn
    • Facebook
    • Email
  • Feedback
  • Edit
Show / Hide Table of Contents

RecurrenceRule Table (207)

Some tooltip text!
• 2 minutes to read
 • 2 minutes to read

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

Fields

Name Description Type Null
RecurrenceRule_id Primary key PK
pattern Recurrence pattern (daily, weekly etc) Enum RecurrencePattern
subPattern Subpattern (workday, everyday, weekday etc) Enum RecurrenceSubPattern
weekdays Weekdays used, bitmask based on ERecurrenceWeekDays enumeration UShort
startDate Start date for repetition pattern DateTime
endDate End date for repetition pattern DateTime
cyclicDay Every nth day, in cyclic patterns UShort
cyclicWeek Every nth week, in cyclic patterns UShort
cyclicMonth Every nth month, in cyclic patterns UShort
registered Registered when UtcDateTime
registered_associate_id Registered by whom FK associate
updated Last updated when UtcDateTime
updated_associate_id Last updated by whom FK associate
updatedCount Number of updates made to this record UShort

RecurrenceRule table relationship diagram

Indexes

Fields Types Description
RecurrenceRule_id PK Clustered, Unique

Relationships

Table Description
appointment Tasks, appointments, followups, phone calls; and documents (document_id != 0). An appointment always has a corresponding record in VisibleFor specifying who may see this.
associate Employees, 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.
© SuperOffice. All rights reserved.
SuperOffice |  Community |  Release Notes |  Privacy |  Site feedback |  Search Docs |  About Docs |  Contribute |  Back to top