@cplace/mcp-server 1.3.14

package/dist/widget-specifications/cf.cplace.platform.connectedAttributesGroup/singleSelectionWidgetId.md

@@ -0,0 +1,15 @@
+**Warning**: Despite the localized name "Data source", this is NOT where you provide data - it's a widget ID selector!
+
+**Purpose**: Specifies which widget on the same page provides entity selection events. When a user selects an entity in that widget, this connected attributes group widget refreshes to show that entity's attributes.
+
+**Valid Widget Types**: Currently only table widgets (`cf.cplace.platform.table`) implement the required `ISingleEntitySelectionProducer` interface.
+
+**How to Get Valid Values**: The dropdown is populated dynamically by `SingleSelectionWidgetEnumerationProvider` which finds all widgets on the same page that can provide entity selection events.
+
+**Workflow**:
+1. Ensure there is at least one table widget on the same page
+2. The table widget's ID will appear in the enumeration dropdown
+3. Select the table widget ID you want to connect to
+4. The layout configuration field becomes visible after this is set
+
+**Note**: The layout visibility is controlled by `showPropertyInEdit()` - layout field only shows after a selection widget is configured.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.platform.dynamicIframe",
+  "Description": "{\"de\":\"Bindet den Inhalt einer beliebigen Webseite (als Inlineframe) ein oder erzeugt eine Schaltfläche zum Aufrufen einer festgelegten URL. Die URL kann dabei in Abhängigkeit von Attributwerten dynamisch erzeugt werden.\",\"en\":\"Integrates the content of any site (as an inline frame) or generates a button for calling up a defined URL. Here the URL can be created dynamically depending on attribute values.\"}",
+  "Localized Name": "{\"en\":\"Dynamic Inline Frame\",\"de\":\"Dynamischer Inlineframe\"}",
+  "Icon": "fa-laptop",
+  "Plugin": "cf.cplace.platform",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace",
+  "* Details DE": null,
+  "* Details EN": "<p><strong>More Details</strong></p><p>The 'Dynamic Inline Frame' widget can either be used to embed the content of any other webpage by means of an iframe element or to create a button for calling a specified URL. The URL can also be generated dynamically based upon attribute values.</p><p><strong>Settings</strong></p><p>// * Title*: Bilingual text.</p><p>// * URL pattern*: Name generation pattern. You can use attribute names in angle brackets &lt;&gt;, to include attributes of the embedding page.</p><p>// * Show only button*: True/false. If this option is set, instead of displaying an iframe only a button that opens a new tab will be shown.</p><p>// * Button label:</p><p>// * Height:</p>"
+}

package/dist/widget-specifications/cf.cplace.platform.dynamicIframe/_meta.json

@@ -0,0 +1,9 @@
+{
+  "tags": [
+    "attributes",
+    "media",
+    "read-only",
+    "detail-view"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.cplace.platform.dynamicIframe/_overview.md

@@ -0,0 +1,49 @@
+## Overview
+
+Integrates the content of any site (as an inline frame) or generates a button for calling up a defined URL. Here the URL can be created dynamically depending on attribute values.
+
+The widget extends the standard Inline Frame widget by enabling dynamic URL construction using page attributes. Instead of a static URL, users define URL patterns with attribute placeholders (using angle bracket syntax `<attributeName>`), which are substituted with actual values at runtime. This allows context-aware embedding of external content based on the data of the current page.
+
+The widget supports two display modes:
+- **Inline Frame Mode** (default): Embeds external content directly within the page
+- **Button Mode**: Shows a button that opens the URL in a new browser tab
+
+## Use Cases
+
+- **External Documentation Integration**: Display context-specific documentation based on page attributes (e.g., `https://docs.company.com/<productId>/manual.html`)
+- **External API Visualization**: Embed dashboards or reports from external systems using page data as parameters
+- **Third-Party Tool Integration**: Integrate with external tools like Jira by constructing URLs from page attributes (e.g., `https://jira.company.com/browse/<ticketId>`)
+- **Dynamic Map Embedding**: Show location-based content using address or coordinate attributes
+- **External Form Integration**: Link to external forms with pre-filled data from page attributes
+
+## Design Considerations
+
+### When to Use Dynamic Inline Frame vs Inline Frame
+
+- Use **Inline Frame** (`cf.platform.iframe`) for static URLs that don't change based on page content
+- Use **Dynamic Inline Frame** when the URL should incorporate values from page attributes
+
+### URL Pattern Syntax
+
+- Attribute references use angle brackets: `<attributeName>`
+- Multiple attributes can be combined in a single URL pattern
+- Attribute values are automatically URL-encoded when part of a larger pattern
+- Special case: When the entire pattern is a single attribute (e.g., `<url>`), no encoding is applied to allow storing complete URLs
+
+### Button Mode
+
+Use button mode when:
+- External sites block iframe embedding (X-Frame-Options)
+- Users prefer opening content in a separate tab
+- The iframe display is not desired for UX reasons
+
+### Validation Requirements
+
+- The URL pattern must contain at least one attribute reference
+- All referenced attributes must exist in the page type
+- Referenced attributes must have non-empty values at runtime
+
+## Related Patterns
+
+- **Inline Frame** (`cf.platform.iframe`): For static URL embedding without dynamic content
+- **Single Attribute** (`cf.platform.singleAttribute`): For displaying attribute values directly rather than embedding external content

package/dist/widget-specifications/cf.cplace.platform.dynamicIframe/_summary.md

@@ -0,0 +1 @@
+Integrates the content of any site (as an inline frame) or generates a button for calling up a defined URL. The URL can be created dynamically depending on attribute values.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.platform.tableWidget",
+  "Description": "{\"en\":\"Displays a list of search results.\",\"de\":\"Zeigt eine Liste von Suchergebnissen an.\"}",
+  "Localized Name": "{\"en\":\"Table 2.0\",\"de\":\"Tabelle 2.0\"}",
+  "Icon": "fa-table",
+  "Plugin": "cf.cplace.platform",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.platform.tableWidget/_implementation.md

@@ -0,0 +1,11 @@
+**Configuration Modes**:
+- `search`: Query pages via embedded search (most common)
+  - Requires: `search` attribute with `cplaceJson` value from `cplace_search_pages`
+- `connectedWidget`: React to selection from another widget on the page
+  - Requires: `connectedWidgetId` pointing to the source widget
+
+**Typical Configuration Workflow**:
+1. Configure `search` (and optionally `connectedWidgetId` for master-detail)
+2. Define visible columns via `columns` attribute
+3. Optionally configure sorting (`multiSortColumns`), filtering (`filters`), and grouping (`groupColumn`)
+4. Configure display options via `displayOptions` multi-enum

package/dist/widget-specifications/cf.cplace.platform.tableWidget/_meta.json

@@ -0,0 +1,12 @@
+{
+  "tags": [
+    "table",
+    "searchable",
+    "filterable",
+    "sortable",
+    "selectable",
+    "connected",
+    "navigation"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.cplace.platform.tableWidget/_overview.md

@@ -0,0 +1,188 @@
+## Overview
+
+Displays a list of search results.
+
+The Table Widget is a next-generation table implementation that presents search results in a tabular format with modern web component architecture. It serves as both a primary data display component and a powerful data producer for connected widgets, supporting advanced features like multi-column sorting, dynamic filtering, and customizable column configurations.
+
+**Status**: Beta (requires feature flag `newTableEnabled`)
+
+## Key Capabilities
+
+- **Search-based data display**: Executes configured searches and displays results in a table format
+- **Multi-producer architecture**: Acts as a data source for other widgets through three producer interfaces
+  - Search results provider (ISearchProducer)
+  - Single entity selection (ISingleEntitySelectionProducer)
+  - Multi-entity selection (IMultiEntitySelectionProducer)
+- **Advanced table features**: Multi-level sorting, column customization, filtering, and pinned columns
+- **Connected widget support**: Establishes master-detail relationships with other widgets
+
+## Use Cases
+
+### Primary Data Display
+**When to use**: Display search results in a structured, sortable table format
+
+**Example scenarios**:
+- All projects in a workspace with status and owner columns
+- Team members with their roles, departments, and contact information
+- Task lists with status, assignee, and due dates
+
+**Why this widget**:
+- Clean tabular organization of data
+- Native sorting and filtering capabilities
+- User-configurable column visibility and order
+
+### Master Table in Master-Detail Pattern
+**When to use**: One table drives the content of detail widgets on the same page
+
+**Example scenario**: Project list table connected to:
+- Project details widget (shows selected project attributes)
+- Project team widget (shows team members of selected project)
+- Project timeline widget (shows schedule of selected project)
+
+**Why this widget**:
+- Implements producer interfaces for single and multi-entity selection
+- Emits selection events that connected widgets consume
+- Enables coordinated page layouts with dynamic detail views
+
+### Connected Table (Detail Table)
+**When to use**: Table content depends on selection from another widget
+
+**Example scenarios**:
+- Task table showing tasks for a project selected in a project dropdown
+- Team member table filtered by department selected in a department selector
+- Issue table scoped to the component selected in a component list
+
+**Why this widget**:
+- Connects to selection producers via `CONNECTED_WIDGET_ID` configuration
+- Automatically refreshes when connected widget selection changes
+- Provides context-filtered views based on parent selections
+
+### Search Result Provider
+**When to use**: Provide search results to visualization widgets (charts, metrics)
+
+**Example scenario**: Table showing filtered issues connected to:
+- Pie chart showing issue distribution by status
+- Bar chart showing issues by priority
+- Number widget showing total count
+
+**Why this widget**:
+- Implements ISearchProducer interface for sharing search results
+- Allows multiple widgets to visualize the same dataset
+- Handles permissions and execution mode properly for consumers
+
+### Multi-Column Sorted Lists
+**When to use**: Complex sorting requirements with multiple sort criteria
+
+**Example scenarios**:
+- Employee list sorted by department (primary), then seniority (secondary), then name (tertiary)
+- Product catalog sorted by category, then price, then rating
+
+**Why this widget**:
+- Supports `MULTI_SORT_COLUMNS` configuration for multi-level sorting
+- Maintains sort order across refreshes
+- Users can configure sorting priorities
+
+### Filtered Data Views
+**When to use**: Pre-configured filters need to be applied to displayed data
+
+**Example scenarios**:
+- "My Open Tasks" table with pre-filtered view showing user's assigned tasks
+- "High Priority Issues" table showing only urgent items
+- "This Month's Activities" with date range filter
+
+**Why this widget**:
+- Supports `FILTERS` configuration for pre-configured filtering
+- Combines search definition with filter criteria
+- Users can add additional filters on top of pre-configured ones
+
+## Design Considerations
+
+### When to Use This Widget
+
+Use the Table Widget when:
+- You need a modern, feature-rich table implementation
+- The `newTableEnabled` feature flag is active in your environment
+- You're building new pages requiring table functionality
+- You need master-detail patterns with connected widgets
+- You want to provide search results to multiple visualization widgets
+
+### Prerequisites and Dependencies
+
+**Required**:
+- Feature flag `newTableEnabled` must be active
+- Valid search definition in configuration
+- Widget must be embedded in a page
+
+**Optional**:
+- Connected widgets for producer/consumer patterns
+- Column and filter configurations for customized views
+- Multi-sort configuration for complex sorting
+
+### Beta Status Considerations
+
+The widget is marked with `@Beta` annotation, indicating:
+- API may undergo changes in future releases
+- Feature flag controls availability in production
+- Monitor feature flag status in target environments
+- Consider migration planning if replacing legacy table widgets
+
+## Common Patterns
+
+### Pattern 1: Standalone Table
+Simple table displaying search results with optional customization:
+- Configure search query
+- Define visible columns
+- Optionally add pre-configured filters
+- Enable/disable "Create New" button
+- Pin first column for horizontal scrolling
+
+### Pattern 2: Master Table with Details
+Table driving multiple detail widgets:
+- Master table produces single entity selection
+- Multiple detail widgets connect to the master table
+- Each detail widget shows different aspects of selected entity
+- Selection in master table updates all connected details
+
+### Pattern 3: Table with Analytics
+Table providing data to visualization widgets:
+- Table widget executes search and produces results
+- Multiple chart widgets connect to the table
+- Each chart visualizes a different aspect of the data
+- Metric widgets show aggregated statistics
+
+### Pattern 4: Hierarchical Tables
+Parent-child table relationship:
+- Parent table (e.g., Departments) produces single selection
+- Child table (e.g., Employees) connects to parent table
+- Child table search is filtered by parent selection
+- Changing parent selection updates child table content
+
+## Comparison with Other Table Widgets
+
+### vs. Embedded Search as Table (EMBEDDED_SEARCH_AS_TABLE)
+
+**Table Widget advantages**:
+- Modern web component architecture (vs. legacy AngularJS)
+- Cleaner producer interface implementation
+- Feature-flagged for controlled rollout
+- Better separation of concerns in state management
+
+**When to use Table Widget**:
+- New implementations on modern infrastructure
+- When `newTableEnabled` feature flag is active
+- For new pages requiring table functionality
+
+**When to use Embedded Search as Table**:
+- Legacy pages still on AngularJS
+- When `newTableEnabled` feature flag is not active
+- Existing implementations that don't need migration
+
+The Table Widget is the "next generation" implementation with improved architecture, while Embedded Search as Table is the established, production-stable version.
+
+## Related Widgets
+
+- **Embedded Search as Table** (`cf.cplace.platform.embeddedSearchAsTable`): Legacy table widget, production-stable alternative
+- **Single Attribute Widget**: Common detail widget for displaying attributes of selected entity
+- **Attributes Group Widget**: Shows multiple attributes of connected entity selection
+- **Chart widgets** (Pie, Bar, Line): Visualize data from table search results
+- **Number of Results Widget**: Shows count metrics from table search results

package/dist/widget-specifications/cf.cplace.platform.tableWidget/_summary.md

@@ -0,0 +1 @@
+Displays a list of search results in an interactive, configurable table format with advanced features like sorting, filtering, column configuration, and widget connectivity. Use for structured data display and as a data source for connected widgets through master-detail patterns.

package/dist/widget-specifications/cf.cplace.platform.tableWidget/columns.md

@@ -0,0 +1,16 @@
+**Warning**: Every column must reference an attribute that actually exists on the **target type** being displayed in the table. Before configuring columns, use cplace MCP tools to look up the target type's actual attributes and verify that each column attribute name exists. Never assume or reconstruct attribute names. Columns referencing non-existent attributes will fail silently or produce errors.
+
+**JSON Format**:
+```json
+[
+  {"name": "'cf.cplace.myType.attributeName'", "visible": true},
+  {"name": "'cf.cplace.myType.otherAttribute'", "visible": false},
+  {"name": "name", "visible": true}
+]
+```
+
+**Important**:
+- **Custom attributes** require single quotes around the attribute name: `"'cf.cplace.myType.attributeName'"`
+- **Builtin attributes** (e.g., `name`, `createdAt`, `creator`, `modifiedAt`, `modifier`, `owner`) are specified without quotes: `"name"`
+
+**Note**: Order in array determines column display order. Hidden columns (`visible: false`) can still be used for sorting/filtering.

package/dist/widget-specifications/cf.cplace.platform.tableWidget/displayOptions.md

@@ -0,0 +1,12 @@
+**Multi-select enum** controlling table display behavior. Selected values enable the corresponding feature.
+
+**Available options**:
+- `showToolbar`: Show the toolbar with action buttons
+- `showQueryBar`: Show the query/filter bar above the table
+- `showColumnHeader`: Show column headers
+- `showStatusBar`: Show the status bar (pagination) below the table
+- `showLinksInNameColumn`: Make entity names clickable links
+- `showNewButton`: Show the "Create New" button
+- `displayRowsInCompactMode`: Display rows in compact/single-spaced mode
+
+**Note**: When a new widget is created, default display options are applied automatically. The defaults include all options except `displayRowsInCompactMode`.

package/dist/widget-specifications/cf.cplace.platform.tableWidget/multiSortColumns.md

@@ -0,0 +1,16 @@
+**JSON Format**:
+```json
+[
+  {"sortColumn": "'cf.cplace.myType.attribute1'", "sortOrder": "asc", "sortingPriorityIndex": 1},
+  {"sortColumn": "'cf.cplace.myType.attribute2'", "sortOrder": "desc", "sortingPriorityIndex": 2},
+  {"sortColumn": "name", "sortOrder": "asc", "sortingPriorityIndex": 3}
+]
+```
+
+**Valid sortOrder values**: `"asc"`, `"desc"`
+
+**Important**:
+- **Custom attributes** require single quotes around the attribute name: `"'cf.cplace.myType.attributeName'"`
+- **Builtin attributes** (e.g., `name`, `createdAt`, `creator`, `modifiedAt`, `modifier`, `owner`) are specified without quotes: `"name"`
+
+**Note**: `sortingPriorityIndex` determines which sort applies first (lower = higher priority).

package/dist/widget-specifications/cf.cplace.platform.tableWidget/search.md

@@ -0,0 +1,21 @@
+**Warning**: Do not manually construct search JSON!
+
+**Correct Usage**: Use the cplaceJson field from cplace_search_pages response
+
+**Workflow**:
+1. Call cplace_search_pages with your desired filter
+2. Take the cplaceJson field from the response
+3. Use that value for the search configuration
+
+**Relative Filters** (e.g., "show items referencing current page"):
+
+When using `relativeReference` filters, you MUST provide a real page UID as context:
+
+```
+cplace_search_pages(
+  search_filter: [{"relativeReference": {"attribute": "myType.refAttr", "operator": "embeddingCustomEntity"}}],
+  embeddingEntityUid: "page/abc123"  // ← Real page UID required!
+)
+```
+
+Without a concrete `embeddingEntityUid`, the relative filter won't be included in the returned `cplaceJson`.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.pptexport.pgPreviewWidget",
+  "Description": "{\"en\":\"Shows a preview of a Presentation Graphic export of visualized schedules.\",\"de\":\"Zeigt eine Vorschau eines Präsentationsgrafik-Exports von visualisierten Terminplänen\"}",
+  "Localized Name": "{\"en\":\"Presentation Graphic Schedule Preview\",\"de\":\"Präsentationsgrafik-Plan-Vorschau\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.pptexport",
+  "App": "cf.cplace.pptexport",
+  "Localized App Name": "{\"en\":\"Presentation Graphic\",\"de\":\"Präsentationsgrafik\"}",
+  "Repository": "cplace-project-planning",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.pptexport.pgPreviewWidget/_meta.json

@@ -0,0 +1,11 @@
+{
+  "tags": [
+    "timeline",
+    "read-only",
+    "reporting",
+    "scheduling",
+    "connected",
+    "media"
+  ],
+  "requiredApp": "cf.cplace.pptexport"
+}

package/dist/widget-specifications/cf.cplace.pptexport.pgPreviewWidget/_overview.md

@@ -0,0 +1,92 @@
+## Overview
+
+Shows a preview of a Presentation Graphic export of visualized schedules.
+
+The widget displays a preview of Presentation Graphic (PG) exports for project schedules. "PG" stands for "Presentation Graphic" and refers to a visual representation of project schedules (Gantt charts) that can be exported to PowerPoint (PPTX) or PDF formats. The widget generates paginated image previews of how schedules will appear in the final export and provides action buttons for configuration, refresh, and export operations.
+
+## Use Cases
+
+### Schedule Export Preview
+Users want to see how their project schedules will look before exporting them to presentations.
+
+**Example Scenario**: A project manager preparing a stakeholder presentation wants to preview how their project Gantt chart will appear in PowerPoint before generating the final export.
+
+### Direct Schedule Export
+Users need to quickly export project schedules to PowerPoint or PDF for reporting or presentations.
+
+**Example Scenario**: During a project review meeting, a team lead needs to quickly export the current project schedule as a PDF to share with attendees.
+
+### Connected Table Integration
+Users want the preview to automatically update based on schedule selections in a connected table widget.
+
+**Example Scenario**: A portfolio manager has a table listing multiple project schedules and wants to preview different schedules by clicking on rows in the table, with the PG preview automatically updating.
+
+### Iterative Configuration
+Users need to refine the visual presentation of schedules by iterating between configuration changes and preview.
+
+**Example Scenario**: A project administrator is setting up a presentation profile with custom colors, column widths, and layout options, using the preview to validate each change.
+
+## Design Considerations
+
+### Schedule Selection Strategy
+
+The widget supports multiple approaches to selecting schedules for preview and export:
+
+- **Explicit Selection**: Directly select one or more schedule pages
+- **Embedding Selection**: Use the schedule from the embedding page
+- **Search-based Selection**: Use a search query to dynamically find schedules with optional sorting
+- **Relative Selection**: Select schedules via an attribute on the embedding page
+- **Connected Table**: Reactively select schedules from a connected table widget
+
+Choose the selection strategy based on whether schedules are known at widget configuration time (explicit), determined by context (embedding/relative), or need to be dynamic (search/connected table).
+
+### Profile Configuration
+
+Profiles define how the presentation graphic is rendered (layout, colors, columns, etc.). The widget can:
+- Use an explicitly selected profile page
+- Use the profile configured in the first selected schedule
+- Use a cplace.js script to dynamically determine the profile
+
+Explicit profile selection is most predictable, while script-based selection allows for advanced customization based on context.
+
+### Preview vs Export
+
+The widget supports two primary operating modes:
+- **Preview Mode**: Shows image preview of the presentation graphic with optional action buttons
+- **Export Mode**: Hides the preview and only shows export buttons for direct downloads
+
+Use preview mode when users need visual validation before export. Use export-only mode when space is limited or the visual preview is not needed.
+
+### Display Options
+
+Key visibility controls include:
+- Toggle preview image visibility
+- Control whether preview generates immediately on widget load
+- Show/hide individual action buttons (refresh, edit, export PDF, export PPTX)
+- Configure widget frame and title display
+- Set fixed or dynamic widget height
+
+These options allow tailoring the widget appearance for different use cases, from compact export-only buttons to full-featured preview interfaces.
+
+## Related Widgets
+
+### Related Types
+- **Schedule Type**: Project schedules (Gantt charts) from the project planning plugin
+- **Profile Type** (`cf.cplace.pptexport.profile`): Configuration pages that define PG layout and styling
+
+### Integration Points
+- **Table Widgets**: Can connect to any table widget to reactively update based on row selection, enabling master-detail patterns
+- **PG Configurator**: Opens a separate configuration interface for designing the presentation layout
+- **Export Handlers**: Backend handlers that generate PPTX and PDF exports
+
+### Plugin Dependencies
+- Part of the `cf.cplace.pptexport` plugin
+- Works with schedules from `cf.cplace.projectPlanning`
+- Uses the external library `cf-cplace-pgpptintegration` for PowerPoint generation
+
+## Common Pitfalls
+
+- **Invalid Configuration**: The widget cannot generate previews if both the button bar and preview are hidden, or if no schedules or profile are selected
+- **Performance**: Generating previews for many large schedules can be slow; consider limiting schedule selection or using search filters
+- **Profile Mismatch**: Using the schedule's own profile may produce unexpected results if schedules have different profiles configured
+- **Connected Table**: When using connected table mode, ensure the table widget is properly configured to emit selection events

package/dist/widget-specifications/cf.cplace.pptexport.pgPreviewWidget/_summary.md

@@ -0,0 +1 @@
+Shows a preview of a Presentation Graphic export of visualized schedules. Generates paginated image previews and provides buttons to configure the presentation layout, refresh the preview, and export to PowerPoint or PDF formats.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.projectTree.editProjects",
+  "Description": "{\"en\":\"Lets you create and manage schedules and projects in the project structure tree.\",\"de\":\"Ermöglicht das Anlegen und Verwalten von Plänen und Projekten im Projektstrukturbaum.\"}",
+  "Localized Name": "{\"en\":\"Edit Project Structure\",\"de\":\"Projektstruktur bearbeiten\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.projectTree",
+  "App": "cf.cplace.projectTree",
+  "Localized App Name": "{\"en\":\"Project Structure\",\"de\":\"Projektstruktur\"}",
+  "Repository": "cplace-project-planning",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.projectTree.editProjects/_meta.json

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

package/dist/widget-specifications/cf.cplace.projectTree.editProjects/_overview.md

@@ -0,0 +1,81 @@
+## Overview
+
+Lets you create and manage schedules and projects in the project structure tree.
+
+The widget provides an interactive tree view for visualizing and managing the hierarchical structure of projects and schedules. It enables users to create, reorganize, and manage project hierarchies through drag-and-drop functionality, allowing restructuring of projects and schedules within the project tree.
+
+The widget displays projects and their subprojects in an expandable/collapsible tree structure, shows schedules associated with each project, and supports both direct children and "additionally linked" projects/schedules (shown with a special icon to distinguish cross-references).
+
+## Use Cases
+
+### Portfolio Management Dashboard
+PMO teams use this widget to get a visual overview of all projects, navigate the project hierarchy to find specific projects or schedules, and restructure projects as organizational needs change.
+
+### Project Reorganization
+Move projects to new parent projects when organizational structure changes, transfer schedules between projects when scope or responsibility shifts, and clean up project hierarchies by deleting unused projects.
+
+### New Project/Schedule Creation
+Create subprojects directly under a parent project, create schedules from templates within the project structure, and build out project hierarchies with nested subprojects through context menu actions.
+
+### Cross-Project Relationships
+View projects that appear in multiple locations via "Additional Project Links", and manage thematic relationships between projects without changing the primary hierarchy.
+
+## Operating Modes
+
+### Default Mode (All Root Projects)
+When no configuration is set, the widget shows all root-level projects (projects without a parent) across all workspaces with the Project Structure app installed. This is useful for organization-wide portfolio views.
+
+### Filtered by Selection Mode
+Explicitly select specific projects as roots via the `rootProjects` attribute. Only those projects and their children appear in the tree. Useful for focused views on specific project groups.
+
+### Filtered by Search Mode
+Define a search query via the `rootProjectsSearch` attribute to dynamically find root projects. Can be combined with explicit selections (explicit + search results). Useful for dynamic views based on project attributes.
+
+## Design Considerations
+
+### When to Use This Widget
+Use this widget when users need to manage the overall project structure, create new projects/schedules, or reorganize existing hierarchies. Typical placement is on a dedicated "Project Structure" or "Portfolio" page, or on a project's dashboard to show its subprojects.
+
+### Problems It Solves
+- Provides a visual representation of complex project hierarchies that would be hard to understand in a flat list
+- Enables restructuring without navigating to individual project pages
+- Centralizes project/schedule creation actions in one interface
+- Shows cross-linked projects without duplicating the actual project data
+
+### Permission and Access Handling
+The widget respects access permissions and only shows items the user can read. If configured root projects exist but the user cannot see them (permissions), it displays an info message about invisible projects. The widget validates permissions before allowing moves, prevents moving a project into its own subtree (circular reference), and respects the "Project Structure Editor" role for restructuring permissions.
+
+## Key Interactions
+
+### Drag-and-Drop Reorganization
+Users can move projects to different parent projects, move schedules to different parent projects, reorder projects within the same parent (projects maintain an order index), and move additionally linked items between parents.
+
+### Context Menu Actions
+Right-clicking on items in the tree provides actions for:
+- Create Subproject (direct creation)
+- Create Subproject from Template
+- Create Schedule (new or from template)
+- Delete project/schedule
+- Open in new tab
+- Unlink project (for additionally linked items)
+
+## Related Patterns
+
+### Part of Project Structure App
+This widget is part of the Project Structure (`cf.cplace.projectTree`) app, which includes the Project type with parent/child relationships and "Additional Project Links", Schedule parent-project reference for organizing schedules under projects, Project Structure Editor role for users who can restructure projects but not edit their content, and template-based creation for projects and schedules.
+
+### Dependencies
+- **cf.cplace.planauswahl** - Provides the tree view infrastructure and base classes
+- **cf.cplace.projektplanung** - Provides Schedule type definitions
+
+The Project Structure app must be installed in the workspace, and Projects and Schedules must have the standard type definitions from the Project Planning solution.
+
+## Display Considerations
+
+- "Linked" items (via Additional Project Links) display with a different icon to distinguish them from direct children
+- Schedules appear before subprojects within each project node
+- The tree uses lazy loading for children to maintain performance with large hierarchies
+- Tree roots are initially expanded; child nodes load on demand
+- Root projects from search are sorted alphabetically
+- Direct children projects are sorted by order index (manually orderable)
+- Schedules are sorted by name

package/dist/widget-specifications/cf.cplace.projectTree.editProjects/_summary.md

@@ -0,0 +1 @@
+Lets you create and manage schedules and projects in the project structure tree. Displays a hierarchical tree with drag-and-drop reorganization and context menu actions for creating subprojects and schedules.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.projektplanung.scheduleLockState",
+  "Description": "{\"en\":\"Provides information on who is currently editing the schedule and offers the option to end schedule editing.\",\"de\":\"Informiert darüber, wer den Plan aktuell bearbeitet und bietet die Option, die Planbearbeitung zu beenden.\"}",
+  "Localized Name": "{\"en\":\"Schedule Edit State\",\"de\":\"Planbearbeitungs-Status\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.projektplanung",
+  "App": "cf.cplace.projektplanung.projektplanungBasic",
+  "Localized App Name": "{\"en\":\"Project Planning (Basic)\",\"de\":\"Projektplanung (Basis)\"}",
+  "Repository": "cplace-project-planning",
+  "* Details DE": null,
+  "* Details EN": null
+}