⚔  (cal.ConflictingEvents)

Shows events conflicting with this one (the master). (more)

Inherits from lino_xl.lib.cal.Events

Every row of this data table is a Calendar entry.

User guide: The cal plugin.

Columns

  • Start date (start_date) : The starting date of this calendar entry. May not be empty.

  • Start time (start_time) : The starting time. If this is empty, the entry is considered an all-day entry.

  • End Time (end_time) : The ending time. If this is before the starting time, and no ending date is given, Lino considers the entry to end the day after.

  • Room (room) : See Room.

  • Author (user) : The responsible user.

Detail layout

      • Calendar entry type (event_type) : The type of this calendar entry.

      • Short description (summary) : A one-line descriptive text.

      • ID (id) : See ID.

        • Notify before (notify_before) : The multiples of a time unit (notify_unit) before which to send a notification to the corresponding user.

        • Unit (notify_unit) : The unit of time to compute before sending a notification. Example values are: minute, hour, day, week et cetera.

        • Start date (start_date) : The starting date of this calendar entry. May not be empty.

        • Start time (start_time) : The starting time. If this is empty, the entry is considered an all-day entry.

        • End Date (end_date) : The ending date of this calendar entry. Leave empty for same-day entries.

        • End Time (end_time) : The ending time. If this is before the starting time, and no ending date is given, Lino considers the entry to end the day after.

      • Controlled by (owner) : The event generator that generated and controls this calendar entry.

      • Workflow (workflow_buttons) : Shows the current workflow state of this database row and a list of available workflow actions.

    • Description (description) : A longer descriptive text.

      • Author (user) : The responsible user.

      • Assigned to (assigned_to) : Another user who is expected to take responsibility for this entry.

    • Presences (cal.GuestsByEvent)

Toolbar actions

  • Table (landscape) (as_pdf) : See (unformatted: <lino_xl.lib.appypod.mixins.PrintTableAction as_pdf ('Table (landscape)')>).

  • Table (portrait) (as_pdf_p) : See (unformatted: <lino_xl.lib.appypod.mixins.PortraitPrintTableAction as_pdf_p ('Table (portrait)')>).

  • Export to .xls (export_excel) : Export this table as an .xls document

  • None (grid_post) : See (unformatted: <lino.core.actions.CreateRow grid_post>).

  • None (grid_put) : See (unformatted: <lino.core.actions.SaveGridCell grid_put>).

  • New (insert) : Insert a new Calendar entry.

  • Create (submit_insert) : Submit this form, i.e. send your data to the server.

  • Duplicate (clone_row) : Insert a new Calendar entry as a copy of this.

  • Delete (delete_selected) : Delete this record

  • Print (do_print) : Print this database row.

  • Clear cache (do_clear_cache) : See (unformatted: <lino.modlib.printing.actions.ClearCache do_clear_cache ('Clear cache')>).

  • ⚔ (show_conflicting) : A ShowSlaveTable button which opens the ConflictingEvents table for this event.

  • Show data problems (show_problems) : See (unformatted: <lino.core.actions.ShowSlaveTable show_problems ('Show data problems')>).

  • Today (show_today) : Show all calendar entries today.

  • Upload files (show_uploads) : Opens a data window with the uploaded files associated to this database object.

  • Check data (check_data) : Update data problem messages for this database object, also removing messages that no longer exist. This action does not change anything else in the database.

  • Create email (create_mail) : Create an email from this

  • Fix data problems (fix_problems) : Update data problem messages and repair those which are automatically fixable.

  • None (grid) : Shows events conflicting with this one (the master).

  • None (open_help) : Open Help Window

  • Update calendar (update_events) : Create or update all other automatic calendar entries of this series.

  • Update presences (update_guests) : Populate or update the list of participants for this calendar entry according to the suggestions.

  • None (validate) : See (unformatted: <lino.core.actions.ValidateForm validate>).

  • Save (submit_detail) : Save changes in this form

Filter parameters

  • Date range from (start_date) : Start date of observed date range.

  • until (end_date) : End date of observed date range.

  • Observed event (observed_event) : See observed_event.

  • Appointments (show_appointments) : Whether only appointments should be shown. “Yes” means only appointments, “No” means no appointments and leaving it to blank shows both types of events.

  • Guest (presence_guest) : Show only entries that have a presence for the specified guest.

  • Calendar entry repeater (cal_entryrepeater) : See cal_entryrepeater.

  • Recurring event (cal_recurrentevent) : See cal_recurrentevent.

  • Controlled by (type) (owner_type) : See Controlled by (type).

  • Controlled by (object) (owner_id) : See Controlled by (object).

  • None (project) : Show only entries assigned to this project, where project is defined by lino.core.site.Site.project_model.

  • Author (user) : Show only entries having this user as author.

  • Assigned to (assigned_to) : Show only entries assigned to this user.

  • State (state) : Show only entries having this state.

  • Room (room) : See Room.

  • Calendar entry type (event_type) : Show only entries having this type.

Hidden columns

  • ID (id) : See ID.

  • End Date (end_date) : The ending date of this calendar entry. Leave empty for same-day entries.

  • Modified (modified) : The time when this database object was last modified.

  • Created (created) : The time when this database row was created.

  • build time (build_time) : Timestamp of the built target file. Contains None if no build hasn’t been called yet.

  • Print method (build_method) : See Print method.

  • Assigned to (assigned_to) : Another user who is expected to take responsibility for this entry.

  • Contact person (contact_person) : Pointer to Person.

  • Represented as (contact_role) : The optional Role of the contact_person within company.

  • Organizer (company) : Pointer to Company.

  • Controlled by (type) (owner_type) : See Controlled by (type).

  • Controlled by (object) (owner_id) : See Controlled by (object).

  • Short description (summary) : A one-line descriptive text.

  • Description (description) : A longer descriptive text.

  • No. (auto_type) : Contains the sequence number if this is an automatically generated calendar entry. Otherwise this field is empty.

  • Priority (priority) : See Priority.

  • Calendar entry type (event_type) : The type of this calendar entry.

  • Transparent (transparent) : Whether this entry should allow other entries at the same time.

  • guests edited (guests_edited) : Whether the guests list of this event has been modified by an end user.

  • State (state) : The state of this entry. The state can change according to rules defined by the workflow.

  • Notify before (notify_before) : The multiples of a time unit (notify_unit) before which to send a notification to the corresponding user.

  • Unit (notify_unit) : The unit of time to compute before sending a notification. Example values are: minute, hour, day, week et cetera.

  • Notifed (notified) : Stores a boolean value as an indication of whether the user has been notified or NOT.

  • Select multiple rows (rowselect) : See Select multiple rows.

  • Controlled by (owner) : The event generator that generated and controls this calendar entry.