@cplace/mcp-server 1.3.14

package/dist/widget-specifications/cf.cplace.lowcode.ai.chatWidget/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.lowcode.ai.chatWidget",
+  "Description": "{\"en\":\"Please use the \\\"Citizen AI Streaming Chat\\\" widget for new use cases. This widget is deprecated and will be removed in future versions.\",\"de\":\"Bitte verwenden Sie das \\\"Citizen AI Streaming-Chat\\\"-Widget für neue Anwendungsfälle. Dieses Widget ist veraltet und wird in zukünftigen Versionen entfernt.\"}",
+  "Localized Name": "{\"en\":\"[DEPRECATED] Citizen AI Chat\",\"de\":\"[VERALTET] Citizen AI Chat\"}",
+  "Icon": "fa-code",
+  "Plugin": "cf.cplace.citizenAi",
+  "App": "cf.cplace.lowcode.ai",
+  "Localized App Name": "{\"en\":\"Citizen AI\",\"de\":\"Citizen AI\"}",
+  "Repository": "cplace-citizen-ai",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.lowcode.ai.chatWidget/_meta.json

@@ -0,0 +1,10 @@
+{
+  "tags": [
+    "searchable",
+    "collaboration",
+    "low-code",
+    "connected",
+    "detail-view"
+  ],
+  "requiredApp": "cf.cplace.lowcode.ai"
+}

package/dist/widget-specifications/cf.cplace.lowcode.ai.chatWidget/_overview.md

@@ -0,0 +1,63 @@
+## Overview
+
+**DEPRECATED**: Please use the "Citizen AI Streaming Chat" widget for new use cases. This widget is deprecated and will be removed in future versions.
+
+The Chat Widget embeds an AI-powered chat interface on cplace pages where users can have conversational interactions with an AI assistant. It provides a low-code approach to building custom AI assistants by allowing developers to write CplaceJS scripts that define the chat behavior while leveraging the platform's AI infrastructure for model connections, memory persistence, and tool execution.
+
+## Use Cases
+
+### Custom AI Chat Assistants
+Create page-specific AI assistants that can answer questions about projects, summarize data, or provide contextual help based on the page content.
+
+### Data-Driven Conversations
+Build chat interfaces that can query and reason about pages retrieved from searches or connected tables, enabling users to ask questions about collections of data.
+
+### Guided User Interactions
+Use prompt suggestions to guide users toward common questions or actions, making the AI more discoverable and useful for specific workflows.
+
+### User-Specific vs. Shared Conversations
+Support both individual chat histories (each user sees their own conversation) or shared chat rooms (all users see the same conversation).
+
+### AI-Assisted Page Operations
+Allow the assistant to perform actions on pages (read/write) through No-Code Tools configured on the AI Assistant.
+
+## Example Scenarios
+
+- **Project Dashboard Chat**: A project manager views a project page and asks the AI to "summarize the open high risks" - the AI analyzes related risk pages and provides a summary
+- **Document Q&A**: Users ask questions about documents embedded or linked to a page
+- **Status Reports**: Users request "create a management summary" and the AI generates a report based on configured data sources
+- **Interactive Help**: Domain-specific help that understands the context of the current page
+
+## Design Considerations
+
+### Script-Based Architecture
+The widget requires a CplaceJS script with `checkAccess()` and `call()` functions. This provides flexibility but requires low-code development skills.
+
+### Memory Persistence
+Chat history is automatically persisted, with options for user-specific or shared conversation history. Configure `maxMessages` to control memory retention.
+
+### Data Source Integration
+The widget can access pages from multiple sources: search queries, explicit selection, or connected table widgets. This determines what context is available to the AI.
+
+### Permission Model
+- Only users with Low-Code permission can embed the widget
+- Runtime access is controlled by the `checkAccess()` function in the script
+- Widget can only be embedded in spaces where Citizen AI app is present
+
+## Common Pitfalls
+
+- Forgetting to implement the required `checkAccess()` function in the script
+- Not considering memory limits when dealing with long conversations
+- Assuming the widget works without the Citizen AI plugin being active in the space
+
+## Alternatives
+
+| Widget | When to Use Instead |
+|--------|---------------------|
+| **Citizen AI Streaming Chat** | Recommended for all new use cases - this is the replacement for the deprecated Chat Widget |
+| **Ask Your Page Widget** (`cf.cplace.citizenAi.askYourPageWidget`) | When you need simple, pre-configured "Ask Your Page" functionality without custom scripting |
+
+## Related Patterns
+
+- **AI Assistant Configuration** - Assistants created via the script can be configured with system messages, tools, and model parameters
+- **Connected Table Pattern** - Use `connectedTable` data source to let users ask questions about data displayed in another widget

package/dist/widget-specifications/cf.cplace.lowcode.ai.chatWidget/_summary.md

@@ -0,0 +1 @@
+[DEPRECATED] Please use the "Citizen AI Streaming Chat" widget for new use cases. This widget is deprecated and will be removed in future versions.

package/dist/widget-specifications/cf.cplace.meeting.pageHeader/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.meeting.pageHeader",
+  "Description": "{\"en\":\"Displays meeting details such as time, location, participants and agenda.\",\"de\":\"Zeigt Besprechungsdetails wie Zeit, Ort, Teilnehmer und Agenda an.\"}",
+  "Localized Name": "{\"en\":\"Meeting Details\",\"de\":\"Meeting-Details\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.meeting",
+  "App": "cf.cplace.meeting",
+  "Localized App Name": "{\"en\":\"Meetings\",\"de\":\"Meetings\"}",
+  "Repository": "cplace-paw",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.meeting.pageHeader/_meta.json

@@ -0,0 +1,12 @@
+{
+  "tags": [
+    "attributes",
+    "metadata",
+    "detail-view",
+    "read-only",
+    "collaboration",
+    "references",
+    "scheduling"
+  ],
+  "requiredApp": "cf.cplace.meeting"
+}

package/dist/widget-specifications/cf.cplace.meeting.pageHeader/_overview.md

@@ -0,0 +1,31 @@
+## Overview
+
+Displays meeting details such as time, location, participants and agenda.
+
+The Meeting Details widget serves as the primary information display for appointment pages within the cplace Meetings app. It renders meeting metadata in a visually organized, frameless layout, providing an at-a-glance view of all essential meeting details including start/end times with weekday formatting, location, organizer, and attendees (both required and optional) with profile images.
+
+The widget also provides actionable links for editing attendees and exporting the meeting to Outlook calendar format (.ics file).
+
+## Use Cases
+
+- **Appointment Page Header**: Display all critical meeting information at the top of appointment pages
+- **Meeting Overview**: Quick visual summary showing who is invited, when the meeting is, and where it takes place
+- **Attendee Management**: Direct access to edit required and optional attendees through an integrated edit link
+- **Calendar Integration**: One-click export to .ics format for importing meetings into personal calendar applications
+- **Participant Visualization**: Show organizer and attendees with profile images and color-coded roles for easy identification
+
+## Design Considerations
+
+This widget is specifically designed for appointment pages (type `cf.appointment`) within the Meetings app. It operates with fixed behavior and does not expose user-configurable options - it automatically displays all appointment attributes and generates action links based on the current page context.
+
+The widget renders without a frame to seamlessly integrate into the page layout. Visual styling distinguishes participant roles through color coding: organizer (gray), required attendees (green), and optional attendees (blue).
+
+Consider using this widget as the primary header element on appointment detail pages. It works best when combined with related widgets like Minutes (rich text), Files, and Comments widgets in a standard appointment page layout.
+
+## Related Patterns/Alternatives
+
+- **Attribute Widget** (`cf.cplace.platform.attributesWidget`): For displaying additional appointment attributes not shown in the header
+- **Rich Text Widget** (`cf.cplace.platform.richTextWidget`): For displaying meeting summary and minutes
+- **Files Widget** (`cf.cplace.platform.filesWidget`): For managing meeting attachments
+- **Comments Widget** (`cf.cplace.platform.commentsWidget`): For meeting discussions and notes
+- **Page Header Widget** (`cf.cplace.pageViewHeadline.widget`): For generic page headers without meeting-specific functionality

package/dist/widget-specifications/cf.cplace.meeting.pageHeader/_summary.md

@@ -0,0 +1 @@
+Displays meeting details such as time, location, participants and agenda, with quick actions for editing attendees and exporting to calendar (.ics) format.

package/dist/widget-specifications/cf.cplace.navigationTileWidget.widget/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.navigationTileWidget.widget",
+  "Description": "{\"de\":\"Ermöglicht, unterschiedliche Layoutalternativen eines Typs in Tabs zu organisieren.\",\"en\":\"Enables you to navigate from one page to another without using the workspace navigation menu.\"}",
+  "Localized Name": "{\"en\":\"Tile Navigation\",\"de\":\"Kachel-Navigation\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.navigationTileWidget",
+  "App": "cf.cplace.navigationTileWidget",
+  "Localized App Name": "{\"en\":\"Tile Navigation\",\"de\":\"Kachel-Navigation\"}",
+  "Repository": "cplace-paw",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.navigationTileWidget.widget/_meta.json

@@ -0,0 +1,9 @@
+{
+  "tags": [
+    "list",
+    "read-only",
+    "navigation",
+    "dashboard"
+  ],
+  "requiredApp": "cf.cplace.navigationTileWidget"
+}

package/dist/widget-specifications/cf.cplace.navigationTileWidget.widget/_overview.md

@@ -0,0 +1,71 @@
+## Overview
+
+Enables you to navigate from one page to another without using the workspace navigation menu.
+
+The Navigation Tile Widget provides visual, icon-based navigation through page hierarchies. It displays a reference page and its child pages as clickable tiles, where each tile shows the page's icon and name. The widget highlights the currently active page and automatically adapts its display for different screen sizes - showing horizontal tiles on desktop and a dropdown menu on mobile devices.
+
+Pages must be explicitly marked to appear in the navigation through a boolean flag ("Show in tile navigation"), giving administrators fine-grained control over which pages are included in the navigation interface.
+
+## Use Cases
+
+### Page Hierarchy Navigation
+Create navigation bars that display a parent page and all its child pages as tiles, allowing users to navigate between sibling pages without returning to the workspace navigation. This is particularly useful for dashboards, overview pages, or section landing pages where related pages need to be quickly accessible.
+
+### Section-Based Workspaces
+Build consistent navigation across multiple related pages at the same level in the hierarchy. Users can maintain context within a specific workspace section while easily switching between pages that share a common parent.
+
+### Workspace Homepage Navigation
+Display top-level sections of a workspace from the root page, providing quick access to main workspace areas. This serves as an alternative to traditional menu-based navigation and works well for workspaces organized into clear sections.
+
+### Contextual Page Navigation
+Navigate between pages that are related to the current page context. The widget can show navigation options that are contextually relevant based on the embedding page's position in the hierarchy.
+
+## Design Considerations
+
+### When to Use This Widget
+
+- You have a group of related pages that users frequently navigate between
+- You want to provide visual, icon-based navigation instead of text-based menus
+- You're building section-based workspaces with clear page hierarchies
+- You need navigation that adapts to mobile devices automatically
+
+### When NOT to Use This Widget
+
+- For deep navigation hierarchies (more than 2-3 levels deep)
+- When you have many pages at the same level (tiles work best with 3-8 items)
+- For navigation that doesn't follow the page hierarchy structure
+- When standard workspace navigation is sufficient for your use case
+
+### Reference Page Strategies
+
+The widget supports three reference page modes that determine which pages are displayed:
+
+**Parent Page Mode**: The most common pattern - displays siblings of the embedding page. If the widget is on "Team A", it shows the parent's children (Team A, Team B, Team C). Use this for lateral navigation between related pages at the same level.
+
+**Workspace Home Mode**: Displays top-level sections of the workspace. This creates consistent top-level navigation across all pages in the workspace, regardless of where the widget is embedded.
+
+**Embedding Page Mode**: Displays children of the current page. Use this for drilling down into sub-sections, where the embedding page serves as the parent for a group of child pages.
+
+### Page Visibility Control
+
+The widget requires explicit opt-in for pages to appear as tiles. Each page has a "Show in tile navigation" attribute that administrators must enable. This provides:
+
+- Fine-grained control over navigation structure
+- Ability to hide organizational pages that shouldn't be direct navigation targets
+- Protection against accidentally exposing internal pages
+
+### Responsive Behavior
+
+The widget automatically adapts its display based on screen size. Desktop and tablet users see horizontal rows of square tiles with icons, while mobile users see a compact dropdown menu with the current page name as the trigger. This ensures usability across all device types without requiring separate mobile configuration.
+
+## Common Pitfalls
+
+- Creating too many navigation tiles (more than 8) can overwhelm users and reduce visual clarity
+- Forgetting to enable the "Show in tile navigation" flag on pages will result in them not appearing in the widget
+- Using deep hierarchies with this widget - it works best for flat, shallow navigation structures
+- Not considering whether the reference page itself should be included as a navigation target
+
+## Related Widgets
+
+- **Breadcrumb Widget** - Provides path-based navigation showing the current page's location in the hierarchy; better for showing where users are rather than lateral navigation between siblings
+- **Standard Workspace Navigation** - cplace's built-in workspace menu provides comprehensive navigation for complex workspace structures with deep hierarchies

package/dist/widget-specifications/cf.cplace.navigationTileWidget.widget/_summary.md

@@ -0,0 +1 @@
+Enables you to navigate from one page to another without using the workspace navigation menu, displaying clickable tiles representing pages in a hierarchy.

package/dist/widget-specifications/cf.cplace.officeReports.headlineForReports/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.officeReports.headlineForReports",
+  "Description": "{\"en\":\"Widget for displaying a headline on report definition pages\",\"de\":\"Widget zur Anzeige einer Überschrift auf Berichtskonfigurations-Seiten\"}",
+  "Localized Name": "{\"en\":\"Visual: Office Report Type\",\"de\":\"Visual: Office Report Typ\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.officeReports",
+  "App": "cf.cplace.officeReports",
+  "Localized App Name": "{\"en\":\"cplace Office Reports\",\"de\":\"cplace Office Reports\"}",
+  "Repository": "cplace-office-reports",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.officeReports.headlineForReports/_meta.json

@@ -0,0 +1,8 @@
+{
+  "tags": [
+    "read-only",
+    "detail-view",
+    "reporting"
+  ],
+  "requiredApp": "cf.cplace.officeReports"
+}

package/dist/widget-specifications/cf.cplace.officeReports.headlineForReports/_overview.md

@@ -0,0 +1,57 @@
+## Overview
+
+The Headline for Reports widget displays a headline on report definition pages. It renders as an 80px tall header with a color-coded banner that provides visual branding and report-type identification for Office Report Configuration pages. The widget shows a report-type-specific background color, a semi-transparent Office application icon, and the text "cplace Office Report Configuration".
+
+The widget automatically detects the report type from the embedding page's configuration and applies the appropriate styling:
+
+| Report Type | Background Color | Icon |
+|-------------|------------------|------|
+| PowerPoint | Orange-red | PowerPoint icon |
+| Word | Blue | Word icon |
+| Excel | Green | Excel icon |
+| Excel with Macros | Green | Excel icon |
+| Unknown/Not set | Gray | Generic file icon |
+
+## Use Cases
+
+### Primary Use Case: Report Configuration Page Branding
+
+The widget serves as a visual header for Office Report Configuration pages, helping users immediately identify:
+- That they are working with an Office Report configuration
+- Which type of report (PowerPoint, Word, or Excel) is being configured
+
+### Typical Scenarios
+
+1. **PowerPoint Report Configuration** - Orange-red banner confirms the user is configuring a PowerPoint export
+2. **Word Report Configuration** - Blue banner distinguishes Word reports from other types
+3. **Excel Report Configuration** - Green banner appears for both standard Excel and macro-enabled Excel configurations
+4. **New Report Configuration** - Gray banner with generic icon indicates the report type has not yet been selected
+
+## Design Considerations
+
+### Fixed Behavior Widget
+
+This widget has no user-configurable parameters. Its appearance is entirely determined by the embedding page's report type attribute. This makes it a "place and forget" widget that automatically reflects the current configuration state.
+
+### Embedding Restrictions
+
+The widget can only be embedded in:
+- Pages of type `cf.cplace.officeReports.configuration`
+- Type definition layouts for the Report Configuration type
+
+Attempting to embed it in other contexts will result in an error.
+
+### Layout Integration
+
+The widget is designed to be used without padding and without a frame for seamless banner integration. In the standard Report Configuration layout, it occupies the first row at full width, appearing above all other configuration widgets.
+
+## Alternatives
+
+For general-purpose page headers or headlines, consider:
+- **cf.cplace.pageViewHeadline.widget** - Customizable headline widget for any page type
+- Standard attribute display widgets if you need to show the page name dynamically
+
+## Related Patterns
+
+- **Office Reports Configuration Layout** - This widget is part of the standard layout for report configuration pages, working alongside the Template Placeholders and Script Placeholders widgets
+- **Visual Type Identification** - Similar to how other specialized page types may use banner widgets for visual branding

package/dist/widget-specifications/cf.cplace.officeReports.headlineForReports/_summary.md

@@ -0,0 +1 @@
+Displays a headline on report definition pages with report-type-specific color coding and icons (PowerPoint, Word, Excel). Provides visual identification of the report type being configured.

package/dist/widget-specifications/cf.cplace.officeReports.scriptPlaceholders/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.officeReports.scriptPlaceholders",
+  "Description": "{\"en\":\"Shows the assignments of the uploaded template in a table.\",\"de\":\"Zeigt die Zuordnungen der hochgeladenen Vorlage in einer Tabelle.\"}",
+  "Localized Name": "{\"en\":\"Script\",\"de\":\"Skript\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.officeReports",
+  "App": "cf.cplace.officeReports",
+  "Localized App Name": "{\"en\":\"cplace Office Reports\",\"de\":\"cplace Office Reports\"}",
+  "Repository": "cplace-office-reports",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.officeReports.scriptPlaceholders/_meta.json

@@ -0,0 +1,10 @@
+{
+  "tags": [
+    "low-code",
+    "table",
+    "read-only",
+    "detail-view",
+    "metadata"
+  ],
+  "requiredApp": "cf.cplace.officeReports"
+}

package/dist/widget-specifications/cf.cplace.officeReports.scriptPlaceholders/_overview.md

@@ -0,0 +1,22 @@
+## Overview
+
+The Script Placeholders widget shows the assignments of the uploaded template in a table. It analyzes Low-Code scripts used for Office report generation and displays all placeholder definitions found within. The widget parses scripts to identify `report.put()` and `slide.put()` calls, showing the placeholder name, line number, and validation status against the Office template. This enables developers to ensure consistency between their scripts and templates before generating reports.
+
+## Use Cases
+
+- **Report Development**: View all placeholders defined in a report script with their exact line numbers for easy navigation and debugging
+- **Template-Script Validation**: Identify mismatches between script placeholder definitions and actual template placeholders (PowerPoint shapes, Word bookmarks, Excel cells)
+- **Dynamic Column Tracking**: See which placeholders are used as dynamically-added table columns in Excel reports
+- **Script Error Detection**: Get immediate feedback when scripts contain parsing errors or syntax issues
+- **Quality Assurance**: Use as live documentation of what data a report configuration expects, helping QA teams verify completeness
+
+## Design Considerations
+
+This widget is designed exclusively for Report Configuration pages and works in tandem with the Template Placeholders widget. Place both widgets side-by-side to enable cross-validation between script definitions and template placeholders. The widget automatically reads the script attribute from the embedding page and receives template data from its companion widget, requiring no manual configuration.
+
+The widget requires the Office Reports plugin to be installed and should only be used on pages of type `cf.cplace.officeReports.configuration`.
+
+## Related Widgets
+
+- `cf.cplace.officeReports.templatePlaceholders` - Displays placeholders found in the Office template; works as a companion to show the template side of validation
+- `cf.cplace.officeReports.headlineForReports` - Shows visual indicator of report type (PowerPoint, Word, Excel) in the same layout

package/dist/widget-specifications/cf.cplace.officeReports.scriptPlaceholders/_summary.md

@@ -0,0 +1 @@
+Shows the assignments of the uploaded template in a table, displaying placeholder definitions from Low-Code scripts with line numbers and validation status against the Office template.

package/dist/widget-specifications/cf.cplace.officeReports.templatePlaceholders/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.officeReports.templatePlaceholders",
+  "Description": "{\"de\":\"Zeigt die im Ziel-Dokument verwendbaren Platzhalter, die sich aus den konfigurierten Zuordnungen ergeben.\",\"en\":\"Shows the placeholders that can be used in the target document that result from the configured mappings.\"}",
+  "Localized Name": "{\"en\":\"Template\",\"de\":\"Vorlage\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.officeReports",
+  "App": "cf.cplace.officeReports",
+  "Localized App Name": "{\"en\":\"cplace Office Reports\",\"de\":\"cplace Office Reports\"}",
+  "Repository": "cplace-office-reports",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.officeReports.templatePlaceholders/_meta.json

@@ -0,0 +1,10 @@
+{
+  "tags": [
+    "files",
+    "table",
+    "read-only",
+    "detail-view",
+    "reporting"
+  ],
+  "requiredApp": "cf.cplace.officeReports"
+}

package/dist/widget-specifications/cf.cplace.officeReports.templatePlaceholders/_overview.md

@@ -0,0 +1,24 @@
+## Overview
+
+The Template Placeholders widget shows the placeholders that can be used in the target document that result from the configured mappings. When a template file is uploaded to a Report Configuration page, this widget parses the document and displays a table of all detected placeholders that can be populated with data through cplace.js scripts.
+
+The widget displays format-specific information: slide numbers for PowerPoint, cell locations for Excel, and placeholder types for all formats. It serves as a reference tool for developers configuring report templates.
+
+## Use Cases
+
+- **Template validation**: Verify that a newly uploaded template contains the expected placeholders before writing the population script
+- **Script development**: Reference the exact placeholder names while writing cplace.js report scripts to ensure correct spelling and casing
+- **Template maintenance**: Review changes to placeholder lists when updating existing report templates
+- **Troubleshooting**: Diagnose report generation issues by comparing template placeholders against script-defined values
+
+## Design Considerations
+
+This widget is specifically designed for Report Configuration pages and cannot be embedded elsewhere. It is a read-only display widget that automatically refreshes when the template file changes. The widget adapts its table columns based on the document format (PPT shows slide numbers, Excel shows cell locations).
+
+Use this widget alongside the Script Placeholders widget to provide a complete view of both template-based and dynamically-defined placeholders on report configuration pages.
+
+## Related Widgets
+
+- **Script Placeholders** (`cf.cplace.officeReports.scriptPlaceholders`) - Shows placeholders defined in the report script code, complementing the template-based placeholders shown by this widget
+- **Generate Report** (`cf.cplace.cplaceReportGeneration.generateReportWidget`) - Triggers report generation using the placeholders configured through template and script widgets
+- **Headline for Reports** (`cf.cplace.officeReports.headlineForReports`) - Provides UI elements for report configuration pages in the Office Reports suite

package/dist/widget-specifications/cf.cplace.officeReports.templatePlaceholders/_summary.md

@@ -0,0 +1 @@
+Shows the placeholders that can be used in the target document that result from the configured mappings. Parses Office templates (PowerPoint, Word, Excel) to display available substitution keys for script-based report generation.

package/dist/widget-specifications/cf.cplace.orgaTree.edit/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.orgaTree.edit",
+  "Description": null,
+  "Localized Name": "{\"en\":\"Edit Organizational Structure\",\"de\":\"Organisationsstruktur bearbeiten\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.orgaTree",
+  "App": "cf.cplace.orgaTree",
+  "Localized App Name": "{\"en\":\"Organizational Structure\",\"de\":\"Organisationsstruktur\"}",
+  "Repository": "cplace-project-planning",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.orgaTree.edit/_meta.json

@@ -0,0 +1,11 @@
+{
+  "tags": [
+    "tree",
+    "references",
+    "drag-drop",
+    "inline-edit",
+    "navigation",
+    "scheduling"
+  ],
+  "requiredApp": "cf.cplace.orgaTree"
+}

package/dist/widget-specifications/cf.cplace.orgaTree.edit/_overview.md

@@ -0,0 +1,62 @@
+## Overview
+
+The Edit Organizational Structure widget serves as the primary interface for managing organizational structures within cplace. It displays a hierarchical tree representation showing relationships between departments, teams, users (persons), and their associated schedules. The widget enables visualization, navigation, and manipulation of organizational hierarchies through an interactive tree interface.
+
+The tree structure includes:
+- **Departments** - Root level and nested (subdepartments), containing users and teams
+- **Teams** - Belong to departments and contain user members
+- **Persons** - Can belong to multiple departments and/or teams, expandable to show schedules
+- **Virtual Schedule Nodes** - Group "Own schedules" and "Substitute schedules" under users
+- **Schedules** - Leaf nodes linked to project planning functionality
+
+## Use Cases
+
+### Organizational Structure Management
+Building and maintaining company or project organizational structures. Suitable for creating initial structures, updating during reorganizations, adding new departments, and restructuring via drag-and-drop.
+
+### Team Management
+HR managers and department heads organizing teams within departments. Create new teams, view all teams and members at a glance, move teams between departments.
+
+### User Assignment and Overview
+Managers viewing which users belong to which departments and teams. Users can appear in multiple locations when they belong to multiple organizational units.
+
+### Schedule Management Access
+Navigating to user schedules through the organizational tree. Access own schedules, substitute schedules (where user is deputy), and project schedules.
+
+### Homepage and Navigation Hub
+Serves as the primary landing page for workspaces with the Organizational Structure app, providing central navigation for all organizational data.
+
+## Design Considerations
+
+### Drag-and-Drop Reorganization
+- Only departments can be moved via drag-and-drop (not teams or users)
+- Server-side validation prevents invalid hierarchy structures
+- Position options: "before", "after", or "inside" the target node
+
+### Context Menu Actions
+Actions are context-sensitive based on node type:
+- **Departments**: New Department, New Team, Open, Edit access rights, Delete
+- **Teams**: New Team, Open, Edit access rights, Delete
+- **Schedules**: Copy, Open, Delete
+- **Persons/Virtual Nodes**: Open in new tab
+
+### Permission Model
+The widget respects cplace permissions - actions are hidden (not disabled) when users lack required permissions. Create, edit/move, delete, and read operations all require appropriate rights.
+
+### Data Loading
+Uses lazy loading - root departments load initially, child nodes load on expansion. Real-time updates via platform events for create/delete operations.
+
+## Common Pitfalls
+
+- Assuming teams and users can be reorganized via drag-and-drop (only departments support this)
+- Expecting selection functionality - the edit widget focuses on navigation and manipulation, not selection
+- Real-time sync only covers create/delete events, not edits to existing items
+
+## Related Widgets
+
+- **Project Tree Widget** (`cf.cplace.projectTree`) - Similar hierarchical tree for project management, shares base infrastructure
+- **Personal Tree Content Provider** - Provides schedule management functionality integrated into this widget
+
+## Alternatives
+
+For pure viewing without editing capabilities, consider a read-only tree display. For schedule-focused workflows, the project tree widget may be more appropriate.

package/dist/widget-specifications/cf.cplace.orgaTree.edit/_summary.md

@@ -0,0 +1 @@
+Provides an interactive tree view for managing organizational hierarchies, allowing users to create, edit, reorganize, and navigate departments, teams, members, and their associated schedules through drag-and-drop operations and context menus.

package/dist/widget-specifications/cf.cplace.outlookMessageIntegration.outlookMessages/_catalog-data.json

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.outlookMessageIntegration.outlookMessages",
+  "Description": "{\"en\":\"The widget allows you to upload emails directly from Microsoft Outlook to cplace using drag \\u0026 drop. Supports e-mails in .msg format.\",\"de\":\"Das Widget ermöglicht es Ihnen, E-Mails direkt aus Microsoft Outlook per Drag \\u0026 Drop auf cplace hochzuladen. Unterstützt E-Mails im .msg-Format.\"}",
+  "Localized Name": "{\"en\":\"Emails\",\"de\":\"E-Mails\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.outlookMessageIntegration",
+  "App": "cf.cplace.outlookMessageIntegration",
+  "Localized App Name": "{\"en\":\"Outlook Email Integration\",\"de\":\"Outlook-E-Mail-Integration\"}",
+  "Repository": "cplace-paw",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.outlookMessageIntegration.outlookMessages/_meta.json

@@ -0,0 +1,12 @@
+{
+  "tags": [
+    "files",
+    "metadata",
+    "table",
+    "drag-drop",
+    "read-only",
+    "detail-view",
+    "collaboration"
+  ],
+  "requiredApp": "cf.cplace.outlookMessageIntegration"
+}

package/dist/widget-specifications/cf.cplace.outlookMessageIntegration.outlookMessages/_overview.md

@@ -0,0 +1,50 @@
+## Overview
+
+The Outlook Messages widget allows you to upload emails directly from Microsoft Outlook to cplace using drag and drop. It supports e-mails in .msg format, parses the email content using Apache POI's HSMF library, and creates structured email pages as children of the current page. This eliminates information silos by bringing email conversations into the shared workspace where they can be searched, referenced, and accessed by team members.
+
+## Use Cases
+
+### Project Communication Archive
+Teams working on projects can archive relevant email correspondence directly in project pages, keeping all project-related information in one place and preserving email context within the project workspace.
+
+### Issue Documentation
+When issues are reported or discussed via email, import the email into the issue page to create an audit trail of communications and reference email content when resolving problems.
+
+### Client Communication Tracking
+Import customer or client emails into relevant account pages to maintain a complete history of email interactions and share email context with team members who were not on the original thread.
+
+### Compliance and Record-Keeping
+Store important business emails within structured records, create searchable archives of email communications, and maintain email evidence linked to specific business processes.
+
+## Design Considerations
+
+### Parent-Child Relationship
+Imported emails are always created as child pages of the page containing the widget. This hierarchical relationship means the parent page becomes a container for related email correspondence.
+
+### Read-Only Data Preservation
+Once imported, email data cannot be edited. This enforces data integrity and ensures the email record remains an accurate representation of the original message.
+
+### File Format Limitation
+Only Microsoft Outlook .msg files are supported. Users must export emails from Outlook before importing them into cplace. This is not a live email integration.
+
+### Attachment Handling
+Email attachments are automatically extracted and stored as cplace Document entities linked to the email page. They can be viewed using the standard files widget on the email detail page.
+
+## Common Pitfalls
+
+- **Wrong file format**: The widget only accepts .msg files, not .eml or other email formats
+- **Permission requirements**: Users must have edit permissions on the parent page to upload emails
+- **Expecting live sync**: This is a one-time import, not a synchronized connection to Outlook
+
+## Alternatives
+
+| Alternative | When to Use |
+|-------------|-------------|
+| **Files Widget** | When you need to store email files without parsing their content into structured data |
+| **Rich String Widget** | When you need to manually add email content as formatted text |
+| **Comments Widget** | When you need collaborative discussion rather than archived correspondence |
+
+## Related Patterns
+
+- **Document Archive Pattern**: Use alongside other file upload widgets for comprehensive document management
+- **Audit Trail Pattern**: Combine with version history to track when emails were imported and by whom

package/dist/widget-specifications/cf.cplace.outlookMessageIntegration.outlookMessages/_summary.md

@@ -0,0 +1 @@
+Allows you to upload emails directly from Microsoft Outlook to cplace using drag and drop. Supports e-mails in .msg format, creating structured email records as child pages with preserved metadata and attachments.