v0.8.0

• @lowdefy/modules-mongodb-plugins: ### Minor Changes

• #79 afa3f13 Thanks @Saiby100! - SmartDescriptions: render plain objects and arrays of objects instead of crashing (React error #31).

  • New generic object field type in the registry (priority 99, after the specific object shapes): renders unknown objects as label/value rows, each value recursing through its own detected field type via a renderNested callback now injected into all registry renderers. Reference-style objects (name / label / title) display their label field only.
  • processFields now skips fields with visible: false, matching Lowdefy block semantics.
  • Empty state keeps rendering the Descriptions header (title / extra) with a muted "No data to display" item, instead of dropping the title.
  • Auto-discovery (data mode) behavior change: single unrecognized objects now render as one row of nested label/value rows instead of flattening into dotted-key rows.

• @lowdefy/modules-mongodb-activities: ### Minor Changes

• #79 2e9c67c Thanks @Saiby100! - Activities: built-in meeting agenda topics, stored as tasks in the actions collection.

  • New built-in Agenda Topics section on the activity form (meeting only): topic, details, action, person responsible (options from the activity's attendees), and due date, with an info alert explaining that agenda changes create/update tasks. Previously this lived in consumer fields.attributes config writing to attributes.agenda_topics.
  • Topics are no longer stored on the activity doc. create-activity and update-activity accept a new agenda_topics payload array and persist each topic as a task document in the actions collection — kind: task, title = topic, description = details, attributes.action, assignees = [person responsible], due_date, app-keyed {app_name}.message, initial stage action-required — linked back via activity_ids and stamped with the activity's company_ids + references payload (e.g. deal_ids) so they surface in host-app task lists.
  • update-activity diffs incoming topics against the activity's existing tasks by _id: new rows insert (upsert), existing rows get field edits only (status untouched), and removed rows get a not-required status entry pushed — never deleted. delete-activity marks the activity's open (action-required) tasks not-required.
  • No per-task events: the existing create-activity / update-activity / delete-activity events carry affected task ids in references.action_ids, and task status entries reference that event's id.
  • get_activity gains a lookup_agenda_tasks stage (_id → activity_ids, excluding not-required) feeding a new read-only Agenda Topics section on the view page and the edit form's seeded rows (hidden task _id per row round-trips through the ControlledList).
  • New actions-collection connection (default collection actions, write enabled) and lookup_collections.actions var (default actions) — consumers mapping the actions collection to another name must set both.
  • Activity docs now also store the create references payload verbatim under a references field, so tasks added later from the edit page inherit the same references.

• #79 f2d1386 Thanks @Saiby100! - Activities: built-in file upload on the activity form.

  • The activity form (new page, edit page, and quick-capture modal) now renders an Attachments section with the files module's file-manager, so users can attach files while logging an activity. Files bind to entity_type: activity, entity_id: activity_id, file_category: activity-attachment — the same keys the detail view's file sidebar reads.
  • To give uploads a stable id before the activity exists, activity_id is minted (_uuid) on form open — capture-modal onOpen and new-page onInit — and reused as the create payload's _id instead of minting a fresh id at submit. The modal's onClose reset clears it; the edit page seeds it from the loaded _id so the file-manager resolves identically on new, edit, and capture. This also gives consumer attachment-style fields.attributes blocks a stable _state: activity_id to bind against.
  • The form embeds the file-manager unconditionally, so hosts must wire the module's files dependency (previously only needed for the optional detail-page file sidebar).

• #68 b7f8ca8 Thanks @Yianni99! - Activities: add basic/complex type gating, clean up the detail view, and fix runtime + warning issues surfaced by demo testing.

  Activities

  • New type: basic | complex field on each activity_types entry. Basic activities (built-in: call, email) are created in default_stage and have no transition UI; complex activities (built-in: meeting) keep the full Mark done / Reopen / Cancel lifecycle. Existing consumer-defined types without an explicit type default to complex (full UI).
  • Type gating enforced at three layers: table action-column cell renderers (em-dash for basic), CallAPI skip conditions (defence in depth for empty-cell clicks), and view-page button visibility. Stage chip on the detail view header is also hidden for basic activities.
  • Breaking: linked contacts are now stored as reference objects. Activity docs store a contacts array of { contact_id, name, email, verified } reference objects (written by the contacts module's contact-selector) instead of the old contact_ids plain-id array. create-activity / update-activity accept a contacts payload in place of contact_ids, and the activities-timeline component's reference_field var takes contacts (matched internally on contacts.contact_id) instead of contact_ids. Emitted events still flatten the references to plain ids under references.contact_ids, so event reverse-lookups are unchanged. Existing data written with contact_ids needs a migration to the new shape.
  • Read pipelines join contact docs into a separate contacts_enriched field (lookup_contacts now matches on contacts.contact_id), keeping the stored reference objects intact for the edit form to round-trip back into the selector. The list table's Contacts column, detail-page contact chips, and view pages all read the enriched docs.
  • New lookup_collections var configures the real Mongo collection names used by the read-pipeline $lookup stages: lookup_collections.contacts (default user-contacts) and lookup_collections.companies (default companies). Override when an app points its connections at differently-named collections ($lookup from takes a collection name, not a connectionId).
  • New components.contact_card_extra_fields / components.company_card_extra_fields vars: extra { label, value } rows rendered under each linked contact's name/email and each linked company's name on the activity-detail chips. value is a top-level key on the projected doc — extend the lookup stage's $project to surface nested source fields.
  • Form rework: the type picker is now a SegmentedSelector (was a dropdown Selector), and the linked-contacts selector relabels per type — Attendees (meeting), CC (email), Participants (otherwise). The "Additional Details" divider above consumer fields.attributes is removed; attribute fields now render directly after the built-in fields.
  • View detail page main column: removed the Status History section (duplicates the events timeline in the History card) and the inline Linked Contacts / Linked Companies sections (duplicates the dedicated sidebar cards).
  • View detail header: collapsed the separate type-chip / title / description blocks into a single header (title + rich-text description) with refined typography, and moved the type + current-stage pills into the wrapping card's extra slot. Captured date, duration (call / meeting), and direction (email) now render via a field-driven SmartDescriptions block whose fields config is the form's meta-row field defs, extracted to the shared components/activity_meta_fields.yaml so the form and the read-only view stay in sync.
  • Description rendering reads description.html instead of the whole TiptapInput value object (fixes [object Object] in the view). Excel export reads description.text for plain output.
  • get_activities.yaml now runs lookup_contacts + lookup_companies stages so the list table's Contacts/Companies columns populate. Dropped returnStoredSource: true so post-write refetches return the live doc immediately instead of waiting on Atlas Search index replication.
  • updated_at / created_at date formatting moved into the shared add_derived_fields.yaml stage — every consumer (detail, list, tile, options) now gets the formatted strings, not just the list page.
  • New optional references payload on create-activity and update-activity: any keys passed in this object are _object.assign'd onto both the inserted/updated doc and the emitted event's references: block. Lets consumers link activities to entities the module doesn't know about (e.g. deal_ids from a CRM app) without forking the module — existing callers passing only contacts / company_ids are unaffected.
  • capture_activity now forwards prefill.references through onOpen state seeding and into the create payload, and seeds cycle_check_self_id / cycle_check_ids so the embedded company-selector's get_companies_for_selector request doesn't ConfigWarning on hosts that don't otherwise declare those state keys. pages/new.yaml mirrors the same references state init and payload pass-through.
  • Fix event display app_name keying. Activities was writing per-event display titles under a hard-coded display.default.title instead of display.{app_name}.title, so the events module's display_key could never read them back (blank timeline titles). The module now declares a required app_name var and follows the same pattern as companies / contacts: defaults/event_display.yaml ships bare event-type keys, and the four write APIs wrap them under app_name via _build.if_none (override fully replaces — no merge) instead of the old _build.object.assign. Breaking: consumers must now pass app_name to the activities module entry.
  • get_activities.yaml stage filter targets status.stage instead of status.0.stage — Atlas Search can't address array elements by position, so the old path never matched and a stage filter returned zero rows.
  • Edit page fetches the activity in onInit instead of onMount, so block-level mount fetches (e.g. the file-manager's files request) see activity_id seeded before they fire.
  • View page mirrors the loaded activity's type into _state: type (init null in onInit, set on hydrate). Consumer fields.attributes visible conditions are written against _state: type (e.g. meeting-only fields); the key existed on the form pages via the type input block but was never set on the view page, so those conditions always evaluated false once SmartDescriptions started honoring visible: false.
  • cycle_check_self_id / cycle_check_ids initialised in onInit on every activity page that uses company-selector — silences the build-time ConfigWarning from companies' implicit _state references in get_companies_for_selector.yaml. Runtime unchanged (request _if_none defaults already covered it).

  Companies / contacts

  • cycle_check_self_id / cycle_check_ids initialised in onInit on the view pages. Any sidebar slot that hosts a company-selector (e.g. via the activities tile_activities slot-wired from the app) triggers companies' get_companies_for_selector request, which reads those _state keys. The build's _state validator warns when keys are referenced but undeclared on the page; the init silences the warning. Runtime unchanged (_if_none defaults take over).

• #79 a56d14a Thanks @Saiby100! - Lock linked-company edits on the activity edit page.

  • Companies: company-selector accepts a new disabled var (default false) that renders the selector read-only.
  • Activities: new disable_company_edit var (default false). When true, the edit page renders the linked-companies selector disabled, so linked companies stay visible but can't be changed after creation. The new page and quick-capture prefill still set companies; detail-page chips and list-table tags are unaffected.

Patch Changes

• #79 0f2f9a3 Thanks @Saiby100! - Activities: make the linked-company display field configurable instead of hardcoding trading_name.

  The lookup_companies read stage and the company_list_items / table_activities templates hardcoded trading_name, which matched neither the companies module's name_field default (name) nor any consumer that left that default in place — linked-company chips and list-table tags rendered blank (table fell back to _id).

  • New company_name_field var (default name) mirrors the companies module's name_field. Set both to the same value when an app stores its company display name under a non-default field (e.g. trading_name).
  • lookup_companies.yaml now projects the configured field under the stable alias name via $getField, so company_list_items and table_activities read company.name regardless of the source field.

  No action needed for consumers on the name default. Apps that store the company display name under another field should set company_name_field to match their companies name_field.

• #79 f2d1386 Thanks @Saiby100! - Activities: restyle the activities-timeline rows for scannability.

  Rows are restructured into a column layout: the activity title leads, with a smaller type-label pill on its right (the pill previously sat left of the title). The activity description renders as muted two-line-clamped text under the title (Tiptap HTML stripped, empty <p></p> docs hidden). The stage pill is replaced by plain stage-coloured text bottom-left, and the date bottom-right now shows the activity's scheduled date (attributes.date) instead of updated.timestamp. Rows get horizontal padding, rounded corners, and a hover background (theme-token based, works in light and dark).

• @lowdefy/modules-mongodb-companies: ### Minor Changes

• #79 a56d14a Thanks @Saiby100! - Lock linked-company edits on the activity edit page.

  • Companies: company-selector accepts a new disabled var (default false) that renders the selector read-only.
  • Activities: new disable_company_edit var (default false). When true, the edit page renders the linked-companies selector disabled, so linked companies stay visible but can't be changed after creation. The new page and quick-capture prefill still set companies; detail-page chips and list-table tags are unaffected.

Patch Changes

• #68 b7f8ca8 Thanks @Yianni99! - Activities: add basic/complex type gating, clean up the detail view, and fix runtime + warning issues surfaced by demo testing.

  Activities

  • New type: basic | complex field on each activity_types entry. Basic activities (built-in: call, email) are created in default_stage and have no transition UI; complex activities (built-in: meeting) keep the full Mark done / Reopen / Cancel lifecycle. Existing consumer-defined types without an explicit type default to complex (full UI).
  • Type gating enforced at three layers: table action-column cell renderers (em-dash for basic), CallAPI skip conditions (defence in depth for empty-cell clicks), and view-page button visibility. Stage chip on the detail view header is also hidden for basic activities.
  • Breaking: linked contacts are now stored as reference objects. Activity docs store a contacts array of { contact_id, name, email, verified } reference objects (written by the contacts module's contact-selector) instead of the old contact_ids plain-id array. create-activity / update-activity accept a contacts payload in place of contact_ids, and the activities-timeline component's reference_field var takes contacts (matched internally on contacts.contact_id) instead of contact_ids. Emitted events still flatten the references to plain ids under references.contact_ids, so event reverse-lookups are unchanged. Existing data written with contact_ids needs a migration to the new shape.
  • Read pipelines join contact docs into a separate contacts_enriched field (lookup_contacts now matches on contacts.contact_id), keeping the stored reference objects intact for the edit form to round-trip back into the selector. The list table's Contacts column, detail-page contact chips, and view pages all read the enriched docs.
  • New lookup_collections var configures the real Mongo collection names used by the read-pipeline $lookup stages: lookup_collections.contacts (default user-contacts) and lookup_collections.companies (default companies). Override when an app points its connections at differently-named collections ($lookup from takes a collection name, not a connectionId).
  • New components.contact_card_extra_fields / components.company_card_extra_fields vars: extra { label, value } rows rendered under each linked contact's name/email and each linked company's name on the activity-detail chips. value is a top-level key on the projected doc — extend the lookup stage's $project to surface nested source fields.
  • Form rework: the type picker is now a SegmentedSelector (was a dropdown Selector), and the linked-contacts selector relabels per type — Attendees (meeting), CC (email), Participants (otherwise). The "Additional Details" divider above consumer fields.attributes is removed; attribute fields now render directly after the built-in fields.
  • View detail page main column: removed the Status History section (duplicates the events timeline in the History card) and the inline Linked Contacts / Linked Companies sections (duplicates the dedicated sidebar cards).
  • View detail header: collapsed the separate type-chip / title / description blocks into a single header (title + rich-text description) with refined typography, and moved the type + current-stage pills into the wrapping card's extra slot. Captured date, duration (call / meeting), and direction (email) now render via a field-driven SmartDescriptions block whose fields config is the form's meta-row field defs, extracted to the shared components/activity_meta_fields.yaml so the form and the read-only view stay in sync.
  • Description rendering reads description.html instead of the whole TiptapInput value object (fixes [object Object] in the view). Excel export reads description.text for plain output.
  • get_activities.yaml now runs lookup_contacts + lookup_companies stages so the list table's Contacts/Companies columns populate. Dropped returnStoredSource: true so post-write refetches return the live doc immediately instead of waiting on Atlas Search index replication.
  • updated_at / created_at date formatting moved into the shared add_derived_fields.yaml stage — every consumer (detail, list, tile, options) now gets the formatted strings, not just the list page.
  • New optional references payload on create-activity and update-activity: any keys passed in this object are _object.assign'd onto both the inserted/updated doc and the emitted event's references: block. Lets consumers link activities to entities the module doesn't know about (e.g. deal_ids from a CRM app) without forking the module — existing callers passing only contacts / company_ids are unaffected.
  • capture_activity now forwards prefill.references through onOpen state seeding and into the create payload, and seeds cycle_check_self_id / cycle_check_ids so the embedded company-selector's get_companies_for_selector request doesn't ConfigWarning on hosts that don't otherwise declare those state keys. pages/new.yaml mirrors the same references state init and payload pass-through.
  • Fix event display app_name keying. Activities was writing per-event display titles under a hard-coded display.default.title instead of display.{app_name}.title, so the events module's display_key could never read them back (blank timeline titles). The module now declares a required app_name var and follows the same pattern as companies / contacts: defaults/event_display.yaml ships bare event-type keys, and the four write APIs wrap them under app_name via _build.if_none (override fully replaces — no merge) instead of the old _build.object.assign. Breaking: consumers must now pass app_name to the activities module entry.
  • get_activities.yaml stage filter targets status.stage instead of status.0.stage — Atlas Search can't address array elements by position, so the old path never matched and a stage filter returned zero rows.
  • Edit page fetches the activity in onInit instead of onMount, so block-level mount fetches (e.g. the file-manager's files request) see activity_id seeded before they fire.
  • View page mirrors the loaded activity's type into _state: type (init null in onInit, set on hydrate). Consumer fields.attributes visible conditions are written against _state: type (e.g. meeting-only fields); the key existed on the form pages via the type input block but was never set on the view page, so those conditions always evaluated false once SmartDescriptions started honoring visible: false.
  • cycle_check_self_id / cycle_check_ids initialised in onInit on every activity page that uses company-selector — silences the build-time ConfigWarning from companies' implicit _state references in get_companies_for_selector.yaml. Runtime unchanged (request _if_none defaults already covered it).

  Companies / contacts

  • cycle_check_self_id / cycle_check_ids initialised in onInit on the view pages. Any sidebar slot that hosts a company-selector (e.g. via the activities tile_activities slot-wired from the app) triggers companies' get_companies_for_selector request, which reads those _state keys. The build's _state validator warns when keys are referenced but undeclared on the page; the init silences the warning. Runtime unchanged (_if_none defaults take over).

• @lowdefy/modules-mongodb-contacts: ### Patch Changes

• #68 b7f8ca8 Thanks @Yianni99! - Activities: add basic/complex type gating, clean up the detail view, and fix runtime + warning issues surfaced by demo testing.

  Activities

  • New type: basic | complex field on each activity_types entry. Basic activities (built-in: call, email) are created in default_stage and have no transition UI; complex activities (built-in: meeting) keep the full Mark done / Reopen / Cancel lifecycle. Existing consumer-defined types without an explicit type default to complex (full UI).
  • Type gating enforced at three layers: table action-column cell renderers (em-dash for basic), CallAPI skip conditions (defence in depth for empty-cell clicks), and view-page button visibility. Stage chip on the detail view header is also hidden for basic activities.
  • Breaking: linked contacts are now stored as reference objects. Activity docs store a contacts array of { contact_id, name, email, verified } reference objects (written by the contacts module's contact-selector) instead of the old contact_ids plain-id array. create-activity / update-activity accept a contacts payload in place of contact_ids, and the activities-timeline component's reference_field var takes contacts (matched internally on contacts.contact_id) instead of contact_ids. Emitted events still flatten the references to plain ids under references.contact_ids, so event reverse-lookups are unchanged. Existing data written with contact_ids needs a migration to the new shape.
  • Read pipelines join contact docs into a separate contacts_enriched field (lookup_contacts now matches on contacts.contact_id), keeping the stored reference objects intact for the edit form to round-trip back into the selector. The list table's Contacts column, detail-page contact chips, and view pages all read the enriched docs.
  • New lookup_collections var configures the real Mongo collection names used by the read-pipeline $lookup stages: lookup_collections.contacts (default user-contacts) and lookup_collections.companies (default companies). Override when an app points its connections at differently-named collections ($lookup from takes a collection name, not a connectionId).
  • New components.contact_card_extra_fields / components.company_card_extra_fields vars: extra { label, value } rows rendered under each linked contact's name/email and each linked company's name on the activity-detail chips. value is a top-level key on the projected doc — extend the lookup stage's $project to surface nested source fields.
  • Form rework: the type picker is now a SegmentedSelector (was a dropdown Selector), and the linked-contacts selector relabels per type — Attendees (meeting), CC (email), Participants (otherwise). The "Additional Details" divider above consumer fields.attributes is removed; attribute fields now render directly after the built-in fields.
  • View detail page main column: removed the Status History section (duplicates the events timeline in the History card) and the inline Linked Contacts / Linked Companies sections (duplicates the dedicated sidebar cards).
  • View detail header: collapsed the separate type-chip / title / description blocks into a single header (title + rich-text description) with refined typography, and moved the type + current-stage pills into the wrapping card's extra slot. Captured date, duration (call / meeting), and direction (email) now render via a field-driven SmartDescriptions block whose fields config is the form's meta-row field defs, extracted to the shared components/activity_meta_fields.yaml so the form and the read-only view stay in sync.
  • Description rendering reads description.html instead of the whole TiptapInput value object (fixes [object Object] in the view). Excel export reads description.text for plain output.
  • get_activities.yaml now runs lookup_contacts + lookup_companies stages so the list table's Contacts/Companies columns populate. Dropped returnStoredSource: true so post-write refetches return the live doc immediately instead of waiting on Atlas Search index replication.
  • updated_at / created_at date formatting moved into the shared add_derived_fields.yaml stage — every consumer (detail, list, tile, options) now gets the formatted strings, not just the list page.
  • New optional references payload on create-activity and update-activity: any keys passed in this object are _object.assign'd onto both the inserted/updated doc and the emitted event's references: block. Lets consumers link activities to entities the module doesn't know about (e.g. deal_ids from a CRM app) without forking the module — existing callers passing only contacts / company_ids are unaffected.
  • capture_activity now forwards prefill.references through onOpen state seeding and into the create payload, and seeds cycle_check_self_id / cycle_check_ids so the embedded company-selector's get_companies_for_selector request doesn't ConfigWarning on hosts that don't otherwise declare those state keys. pages/new.yaml mirrors the same references state init and payload pass-through.
  • Fix event display app_name keying. Activities was writing per-event display titles under a hard-coded display.default.title instead of display.{app_name}.title, so the events module's display_key could never read them back (blank timeline titles). The module now declares a required app_name var and follows the same pattern as companies / contacts: defaults/event_display.yaml ships bare event-type keys, and the four write APIs wrap them under app_name via _build.if_none (override fully replaces — no merge) instead of the old _build.object.assign. Breaking: consumers must now pass app_name to the activities module entry.
  • get_activities.yaml stage filter targets status.stage instead of status.0.stage — Atlas Search can't address array elements by position, so the old path never matched and a stage filter returned zero rows.
  • Edit page fetches the activity in onInit instead of onMount, so block-level mount fetches (e.g. the file-manager's files request) see activity_id seeded before they fire.
  • View page mirrors the loaded activity's type into _state: type (init null in onInit, set on hydrate). Consumer fields.attributes visible conditions are written against _state: type (e.g. meeting-only fields); the key existed on the form pages via the type input block but was never set on the view page, so those conditions always evaluated false once SmartDescriptions started honoring visible: false.
  • cycle_check_self_id / cycle_check_ids initialised in onInit on every activity page that uses company-selector — silences the build-time ConfigWarning from companies' implicit _state references in get_companies_for_selector.yaml. Runtime unchanged (request _if_none defaults already covered it).

  Companies / contacts

  • cycle_check_self_id / cycle_check_ids initialised in onInit on the view pages. Any sidebar slot that hosts a company-selector (e.g. via the activities tile_activities slot-wired from the app) triggers companies' get_companies_for_selector request, which reads those _state keys. The build's _state validator warns when keys are referenced but undeclared on the page; the init silences the warning. Runtime unchanged (_if_none defaults take over).

• @lowdefy/modules-mongodb-events: ### Minor Changes

• #79 186049c Thanks @Saiby100! - Events: render action cards in the timeline by looking up each event's action_ids.

  • get-events gains a $lookup stage (event action_ids → action _id) that reshapes each action into the shape the EventsTimeline block expects: { id, status, message, link }. Status is the first element of the action's status array; message and link are read from the app-keyed display object ({display_key}.message / {display_key}.link), mirroring the per-app display scoping used for event titles. Actions whose current stage is not-required are dropped.
  • The block now receives actionStatusConfig (built-in action_status enum merged with the new action_status var), so action status badges and card colors render.
  • Link buttons: actions that store an app-scoped link (with a pageId) render a button; agenda-topic tasks have no link field so they render without one. An onActionClick handler is registered on the block — a Link action with params: { _event: true } — so clicking the button navigates to the action's pageId/urlQuery.
  • New action_status var (default {}) merged over the built-in modules/shared/enums/action_status.yaml stages (action-required, in-progress, done).
  • New lookup_collections.actions var (default actions) — the real collection name the timeline joins. Consumers mapping the actions collection to another name must set this to match the activities module's actions-collection.

• @lowdefy/modules-mongodb-files: ### Patch Changes

• #79 6936a5c Thanks @Saiby100! - Files: read upload metadata from the file event and set the S3 Content-Type field directly.

  • upload-policy now reads file_name / file_type from _event: file.name / _event: file.type instead of reconstructing the upload block's state path via block_id. This decouples the request from the consuming block's id and avoids a brittle _state lookup.
  • The S3 POST policy now sets Content-Type as a fixed field (_payload: file_type) and drops the equivalent eq $Content-Type condition — the value is asserted by the field rather than gated by a policy condition.
  • file-manager migrates its fetch/refresh Request actions to the requestIds array form with holdValue: true, matching the current Request action API.