@cplace/test-mcp-server 0.1.15 → 1.1.0

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.cplace.visualizations.tupleLineChart",
+  "Description": "{\"de\":\"Ermöglicht die Darstellung von Werten eines Tupel-Attributs im zeitlichen Verlauf.\",\"en\":\"Enables the display of values of a tuple attribute over time.\"}",
+  "Localized Name": "{\"en\":\"Tuple Line Chart\",\"de\":\"Tupel-Liniendiagramm\"}",
+  "Icon": "cf-widget",
+  "Plugin": "cf.cplace.visualizations",
+  "App": "cf.cplace.platform",
+  "Localized App Name": "{\"en\":\"cplace Basis\",\"de\":\"cplace Basis\"}",
+  "Repository": "cplace-paw",
+  "* Details DE": null,
+  "* Details EN": null
+}

package/dist/widget-specifications/cf.cplace.visualizations.tupleLineChart/_meta.json

@@ -0,0 +1,11 @@
+{
+  "tags": [
+    "chart",
+    "time-series",
+    "references",
+    "read-only",
+    "searchable",
+    "dashboard"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.cplace.visualizations.tupleLineChart/_overview.md

@@ -0,0 +1,50 @@
+## Overview
+
+The Tuple Line Chart widget enables the display of values of a tuple attribute over time. It visualizes time-series data stored in tuple entities by displaying numeric or enumeration values over time. It extracts data from tuple references attached to pages and plots them as line series, making it ideal for monitoring trends, progressions, and changes in associated tuple data.
+
+This widget works specifically with cplace's tuple concept - lightweight data structures representing collections of related attribute values. Each tuple contains a date attribute (for temporal positioning) and one or more value attributes (numeric or enumeration).
+
+## Use Cases
+
+- **Tracking numeric values over time**: Monitor quantitative measurements that change over time (e.g., kilometrage readings, performance metrics, budget consumption)
+- **Monitoring status changes**: Track categorical states over time using enumeration values with optional icons (e.g., inspection status history, approval states)
+- **Comparing multiple metrics**: Display multiple related measurements from the same tuple simultaneously (e.g., actual vs. projected values)
+- **Cross-entity comparison**: Use search mode to compare the same metrics across multiple entities on a dashboard
+
+## Operating Modes
+
+### Embedded Mode (Single Page)
+When embedded directly on a page without a search query, the widget displays tuple data from that specific page only. Multiple value attributes create separate series on the same chart. Use this for detail pages showing historical data for one entity.
+
+### Search Mode (Multiple Pages)
+When configured with a search query, the widget finds multiple pages and creates separate series for each. If multiple value attributes are selected, series names combine page name with attribute name. Use this for dashboards comparing data across multiple entities.
+
+## Design Considerations
+
+### When to Use Tuple Line Chart
+- Data is stored in tuple entities (marked with `.asTuple()`)
+- You need to visualize temporal progressions from tuple collections
+- Values are either all numeric or all enumeration (not mixed)
+
+### When to Use Base Line Chart Instead
+- Data comes from regular page attributes, not tuples
+- You need more flexibility in data source configuration
+- Time-series data is not stored in tuple structures
+
+### Prerequisites
+1. A custom type must be defined as a tuple
+2. The tuple type must have at least one date attribute and one numeric or enumeration attribute
+3. A main entity type must have a multi-reference attribute pointing to the tuple type
+4. Tuple instances must exist and be referenced by pages
+
+## Common Pitfalls
+
+- Selecting value attributes of mixed types (some numeric, some enumeration) - all must be the same type
+- Using enumeration attributes with different element sets - all enum attributes must share identical elements
+- Configuring a tuple attribute that references multiple tuple types - exactly one tuple type is required
+
+## Related Patterns
+
+- **Base Line Chart** (`cf.cplace.visualizations.scriptingLineChart`) - Generic line chart for non-tuple data sources
+- **Tuples Widget** (`cf.cplace.tuplesWidget.widget`) - Table-based display for editing tuple data
+- **Connected Bar Chart** (`cf.platform.connectedBarChart`) - Alternative visualization for categorical comparisons

package/dist/widget-specifications/cf.cplace.visualizations.tupleLineChart/_summary.md

@@ -0,0 +1 @@
+Enables the display of values of a tuple attribute over time. Visualizes time-series data from tuple entities as a line chart, plotting date and numeric or enumeration values for tracking trends and progressions.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.attributeHistory",
+  "Description": "{\"en\":\"Shows the change history of an attribute.\",\"de\":\"Zeigt die Änderungshistorie eines Attributs.\"}",
+  "Localized Name": "{\"en\":\"Attribute Versions\",\"de\":\"Attribut-Versionen\"}",
+  "Icon": "fa-undo",
+  "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>\n\n<p>The 'Attribute Versions' widget shows the version history of an individual attribute in a tabular form.</p>\n\n<p>// This widget is a nested widget.</p>\n\n<p>To configure the 'Attribute Version' widget the following information has to be provided:</p>\n\n<p><strong>Settings</strong></p>\n\n<p>// * Title: Bilingual text. Widget Title.<br>\n// * Page: cplace page. The page that contains the attribute of which you want to display the version history. If you do not specify a page, the current page will be set automatically.<br>\n// * Attribute name*: The custom attribute of which you want to display the version history.<br>\n// * Show editor*: True/false. Detemines if the name of the user who made the edit should be displayed.<br>\n// * Default filter*: Determines if all changes should be displayed or if one of the default filters 'Today', 'Last week', 'Last month', or 'Last years' should be set.<br>\n// * Show filter button*: True/false. Determines if a filter button should be displayed on top of the results.</p>\n\n<p><strong>Key benefits</strong></p>\n\n<p>&nbsp;</p>\n\n<p><strong>Examples</strong></p>"
+}

package/dist/widget-specifications/cf.platform.attributeHistory/_meta.json

@@ -0,0 +1,11 @@
+{
+  "tags": [
+    "attributes",
+    "table",
+    "metadata",
+    "read-only",
+    "detail-view",
+    "collaboration"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.attributeHistory/_overview.md

@@ -0,0 +1,79 @@
+## Overview
+
+The Attribute Versions widget shows the change history of an attribute. It tracks and visualizes how a specific attribute's value has evolved over time, displaying a chronological table showing what changed, when it changed, and who made each change. The widget is essential for maintaining audit trails, troubleshooting issues, and providing transparency into data evolution.
+
+The widget retrieves all edit ChangeSets associated with the entity that contain changes to the specified attribute, including the initial value set when the entity was first created. It can display up to 100 historical changes with optional time-range filtering.
+
+## Use Cases
+
+### Audit Trail and Compliance
+Track who changed critical attribute values and when. Maintain compliance records for regulated industries and provide evidence for audits in quality management, financial compliance, or other regulated contexts.
+
+### Troubleshooting and Root Cause Analysis
+Investigate when a value was changed that led to an issue. Identify who made a problematic change and understand the sequence of changes leading to the current state.
+
+### Progress Tracking
+Monitor how status fields evolved over time, track progression through workflow stages, and observe trend changes in numeric or date fields. Useful for understanding project lifecycles and work item evolution.
+
+### Collaboration and Transparency
+Show team members the evolution of shared data and provide visibility into who contributed what changes. Build trust through transparent change tracking.
+
+### Data Recovery Insights
+See previous values that might need to be restored, understand what was lost if incorrect changes were made, and reference historical values for reporting purposes.
+
+## Common Scenarios
+
+- **Project Status Tracking**: Display how a project's status field changed from "Planning" to "In Progress" to "On Hold" to "Completed"
+- **Budget Evolution**: Show how a budget amount was adjusted over time by different team members
+- **Priority Changes**: Track when and by whom a task's priority was escalated
+- **Assignment History**: See who was assigned to a work item over time
+- **Risk Level Monitoring**: Track changes to risk assessment values
+
+## Design Considerations
+
+### Single Attribute Focus
+The widget displays history for one attribute only. To track multiple attributes, use multiple widget instances on the same page. This focused approach keeps the display simple and reduces cognitive load.
+
+### Version Compatibility
+The widget handles version history from different cplace versions gracefully. For older ChangeSets that didn't store new values (pre-5.11), the widget derives missing values from later changes and indicates this with a question mark icon.
+
+### Time Range Filtering
+Use the optional filter button to allow users to dynamically switch between viewing all changes or filtering to recent periods (today, last week, last month, last year). The default filter sets the initial view when the page loads.
+
+### Display Limits
+The widget displays a maximum of 100 history items. For attributes with extensive change history, this limit ensures reasonable performance. A placeholder row indicates when older changes exist beyond the current filter.
+
+### Editor Visibility
+Choose whether to show the "Editor" column based on your needs. Enable it for accountability and collaboration contexts, disable it for cleaner displays when the change author is less relevant.
+
+## Constraints and Limitations
+
+### Non-Derived Attributes Only
+The widget only tracks attributes that store actual values, not computed or derived properties. Derived attributes don't have stored change history.
+
+### CustomEntity Only
+The widget works exclusively with custom entities (pages with custom types). It cannot track built-in system entity attributes.
+
+### Edit ChangeSets Only
+Only changes from edit operations are included. The initial value is shown, but other ChangeSet types (deletion, etc.) are not included in the attribute-specific tracking.
+
+### No Access Control Filtering
+All historical changes are visible regardless of current user permissions. This ensures complete audit trail visibility but means sensitive historical changes remain visible even if editor permissions have changed.
+
+### No Export Functionality
+The widget displays data in-page only with no built-in CSV or Excel export capability. For exportable history, consider alternative approaches or custom development.
+
+## Related Widgets
+
+### Version Info Widget (`cf.platform.modificationInfo`)
+Shows overall entity modification metadata (created/modified dates and users). Use together with Attribute Versions for a complete audit trail - Version Info provides the high-level timeline while Attribute Versions provides attribute-specific detail.
+
+### Comments Widget (`cf.platform.comments`)
+Provides manual annotations about changes. Use together with Attribute Versions to combine automatic data change tracking with human explanations and context.
+
+### Attributes Widget (`cf.platform.attributes`)
+Displays current attribute values. Use on the same page to show both current state (Attributes) and historical evolution (Attribute Versions).
+
+## Technical Context
+
+The widget is part of the platform's versioning and audit trail capabilities, built on top of the ChangeSet system. It provides user-facing visibility into the versioning backend, complementing system-wide version tracking with attribute-specific detail.

package/dist/widget-specifications/cf.platform.attributeHistory/_summary.md

@@ -0,0 +1 @@
+Shows the change history of an attribute, displaying old values, new values, timestamps, and editors in a chronological table format.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.attributes",
+  "Description": "{\"en\":\"Shows all attributes of a page and allows you to edit them.\",\"de\":\"Zeigt alle Attribute einer Seite und erlaubt ihre Bearbeitung.\"}",
+  "Localized Name": "{\"en\":\"Attributes\",\"de\":\"Attribute\"}",
+  "Icon": "fa-pen-square",
+  "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>\n\n<p>The 'Attributes' widget displays all attributes of the page on which it is added and allows you to edit their values.</p>\n\n<p><strong>Key benefits</strong></p>\n\n<p>&nbsp;</p>\n\n<p><strong>Examples</strong></p>"
+}

package/dist/widget-specifications/cf.platform.attributes/_meta.json

@@ -0,0 +1,9 @@
+{
+  "tags": [
+    "attributes",
+    "form",
+    "detail-view",
+    "inline-edit"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.attributes/_overview.md

@@ -0,0 +1,89 @@
+## Overview
+
+The Attributes widget shows all attributes of a page and allows you to edit them. It provides a comprehensive view of all attributes defined on a page's type, automatically discovering and displaying every attribute without requiring manual selection or layout configuration. This "convention over configuration" approach makes it the simplest way to show complete attribute information on any entity page.
+
+The widget displays attributes in the order defined in the type definition and includes custom attributes, built-in system attributes, and inherited attributes from parent types.
+
+## Use Cases
+
+### Standard Page Attribute Display
+
+Display all attributes on entity detail pages where complete attribute coverage is needed. This is common for:
+
+- Entity detail pages where all information should be visible
+- Admin or configuration pages showing complete data
+- Forms where all attributes need to be filled out
+
+### Rapid Prototyping
+
+Build pages quickly without manually configuring individual attribute widgets. The widget automatically adapts when type definitions change, making it ideal for:
+
+- Early development phases
+- Proof-of-concept implementations
+- Internal tools where UI polish is secondary
+
+### Settings and Configuration Pages
+
+Display all configuration options for system settings pages, entity configuration forms, or type definition pages showing available attributes.
+
+### Full Edit Forms
+
+Provide complete editable forms for entities when users need to edit multiple attributes at once, such as bulk data entry scenarios or entity creation workflows.
+
+## Design Considerations
+
+### Zero Configuration Philosophy
+
+The widget intentionally has no user-configurable parameters. This design choice prioritizes:
+
+- Immediate functionality without setup
+- Automatic adaptation to type definition changes
+- Consistent presentation across all entity types
+
+### Permission-Aware Rendering
+
+The widget respects entity-level permissions:
+
+- Read permission is required to view the widget
+- Edit permission is required to see the "Edit" button
+- Individual attributes may have additional read/write restrictions
+
+### Attribute Filtering
+
+By default, the widget excludes attributes marked as "hidden in attributes widget" in the type definition. The order of attributes matches the type definition order.
+
+## Alternatives
+
+Consider these alternatives when the Attributes widget does not meet your requirements:
+
+| Requirement | Recommended Alternative |
+|-------------|------------------------|
+| Custom layout with columns or grouping | Grouped Attributes of a Page (`cf.cplace.platform.attributesGroup`) |
+| Display only specific attributes | Grouped Attributes of a Page or Single Attribute widgets |
+| Custom labels or conditional visibility | Single Attribute (`cf.platform.singleAttribute`) |
+| Display attribute based on table selection | Connected Single Attribute (`cf.platform.connectedSingleAttribute`) |
+
+### Decision Guide
+
+**Use the Attributes widget when**:
+- You need to show all attributes of a page
+- Zero configuration setup is preferred
+- Default ordering and layout is acceptable
+- Building internal tools or prototypes quickly
+
+**Consider alternatives when**:
+- Custom attribute layout is required
+- Only specific attributes should be visible
+- Attributes need custom labels or conditional visibility
+- Integration with table selections is needed
+
+## Embedding Constraints
+
+The widget can be embedded on:
+- CustomEntity pages (standard entity pages with type definitions)
+- Type definition pages
+
+The widget cannot be embedded in:
+- Spaces (workspace-level pages)
+- Documents (file entities)
+- Other widgets (it is not container-embeddable)

package/dist/widget-specifications/cf.platform.attributes/_summary.md

@@ -0,0 +1 @@
+Shows all attributes of a page and allows you to edit them. Automatically renders all defined attributes according to the page's type definition without requiring manual configuration.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.comments",
+  "Description": "{\"en\":\"Enables comments to be added to a page.\",\"de\":\"Ermöglicht das Hinzufügen von Kommentaren zu einer Seite.\"}",
+  "Localized Name": "{\"en\":\"Comments\",\"de\":\"Kommentare\"}",
+  "Icon": "fa-comments",
+  "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>\n\n<p>The 'Comments' widget allows users to add comments to a cplace page.</p>\n\n<p><strong>Settings</strong></p>\n\n<p>// * Widget title: Bilingual text.</p>\n\n<p>// * Fixed height:</p>\n\n<p>&nbsp;</p>"
+}

package/dist/widget-specifications/cf.platform.comments/_meta.json

@@ -0,0 +1,9 @@
+{
+  "tags": [
+    "comments",
+    "collaboration",
+    "inline-edit",
+    "detail-view"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.comments/_overview.md

@@ -0,0 +1,52 @@
+## Purpose
+
+Enables comments to be added to a page.
+
+The Comments widget enables threaded discussions directly on any cplace page. It provides a native collaboration mechanism where users can have conversations, give feedback, and discuss page content without leaving the page context.
+
+## When to Use
+
+- **Collaboration needs**: When team members need to discuss or provide feedback on page content
+- **Review workflows**: For approval processes where reviewers need to leave feedback
+- **Knowledge sharing**: On wiki or documentation pages where questions and clarifications arise
+- **Task coordination**: On work items where team communication is needed
+
+## Design Considerations
+
+### Automatic Scoping
+
+The Comments widget automatically displays the comment thread for the page it's placed on. Unlike other widgets, it requires no data source configuration or search filters—it simply works with the embedding page's comment thread.
+
+### Layout Placement
+
+Comments typically serve a supporting role rather than being the primary content. Consider these placement strategies:
+
+**Below main content**: Place comments in a lower row when discussion is secondary to the main content. Users read the content first, then scroll to participate in discussion. Works well for documentation and wiki pages.
+
+**Side-by-side with content**: Place comments next to the main content when users need to reference what they're discussing. Useful for review pages, task details, or anywhere discussion directly relates to visible content.
+
+**Dedicated section**: Give comments full width when discussion is the primary purpose, such as in a "Discussion" alternative layout tab.
+
+### Pairing with Other Widgets
+
+Comments are frequently paired with the Files widget in a "utilities" row, providing both attachment management and discussion in a compact layout below main content.
+
+When placed beside a content widget, both should have consistent visual height to maintain layout balance.
+
+### Single Instance Principle
+
+Only one Comments widget is needed per layout—multiple instances would show the same thread. If different discussion contexts are needed, consider using alternative layouts with different comment scopes.
+
+## Trade-offs
+
+| Consideration | Implication |
+|---------------|-------------|
+| Notification behavior | Comment activity may trigger notifications based on workspace settings |
+| Permission dependency | Users need appropriate permissions to participate in discussions |
+| Space allocation | Narrow layouts limit readability of longer discussion threads |
+
+## Related Widgets
+
+- **Files**: Often paired in a utilities row for attachments + discussion
+- **Text/Rich String**: Content that users discuss
+- **Attributes Group**: Details that provide context for discussion

package/dist/widget-specifications/cf.platform.comments/_summary.md

@@ -0,0 +1 @@
+Enables comments to be added to a page. Use when team members need to discuss content, provide feedback, or coordinate on work items without leaving the page context.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.connectedBarChart",
+  "Description": "{\"en\":\"Visualizes an attribute of a table or a search configurable in the widget as a bar chart.\",\"de\":\"Visualisiert ein Attribut einer Tabelle oder einer im Widget konfigurierbaren Suche als Säulendiagramm.\"}",
+  "Localized Name": "{\"en\":\"Bar Chart\",\"de\":\"Säulendiagramm\"}",
+  "Icon": "fa-chart-bar",
+  "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>\n\n<p>The 'Bar Chart' widget can be used to visualize an attribute of a table (i.e. a table column) or the result of a configurable search as a bar chart.</p>\n\n<p><strong>Settings</strong></p>\n\n<p>// * Table: The connected table to be used as the source of the bar chart.</p>\n\n<p>// * Search: If no connected table is specified the results of the search specified here will be used to generate the bar chart.</p>\n\n<p>// * Title: Bilingual text.</p>\n\n<p>// * Height in pixels:</p>"
+}

package/dist/widget-specifications/cf.platform.connectedBarChart/_implementation.md

@@ -0,0 +1,10 @@
+**Data Source Modes** (mutually exclusive, one required):
+- **Connected Table** (`tableWidgetId`): Uses data from a connected table widget (e.g., Embedded Search as Table) on the same page. Takes precedence if both are set.
+- **Standalone Search** (`search`): Uses a configured search query as data source.
+
+**Typical Configuration Workflow**:
+1. Choose data source mode:
+   - Set `tableWidgetId` to connect to an existing table widget, OR
+   - Configure `search` with a search query
+2. Select `attributeName` - the attribute to aggregate/group by (only available after data source is configured)
+3. Optionally set `title` and `height`

package/dist/widget-specifications/cf.platform.connectedBarChart/_meta.json

@@ -0,0 +1,11 @@
+{
+  "tags": [
+    "chart",
+    "attributes",
+    "searchable",
+    "filterable",
+    "connected",
+    "dashboard"
+  ],
+  "requiredApp": null
+}

package/dist/widget-specifications/cf.platform.connectedBarChart/_overview.md

@@ -0,0 +1,70 @@
+## Overview
+
+Visualizes an attribute of a table or a search configurable in the widget as a bar chart.
+
+The Connected Bar Chart widget displays the frequency distribution of values for a selected attribute across a dataset. It aggregates data by counting occurrences of each distinct value and renders the results as vertical bars (columns) using Highcharts. The chart is interactive, supporting Y-axis zoom for detailed inspection of data.
+
+## Use Cases
+
+### Status Distribution Analysis
+Visualize how many items exist in each status state (e.g., "Open", "In Progress", "Done"). This is particularly useful for project management dashboards to identify bottlenecks where items accumulate in certain statuses.
+
+### Category Distribution
+Display the distribution of items across categories, types, or priority levels. Examples include showing products by category or issues by priority (Low, Medium, High, Critical).
+
+### Workload Analysis
+Visualize how many items are assigned to each person to identify unbalanced workloads. Useful for resource planning and capacity management.
+
+### Enumeration Value Distribution
+Any enumeration or reference attribute can be visualized to show value distribution across a dataset, helping identify the most and least common values.
+
+## Operating Modes
+
+### Connected Table Mode
+Links to an existing table widget on the same page. The chart inherits the table's search configuration and filters, automatically updating when the table data changes. This mode is ideal for interactive dashboards where users filter data in the table and see the chart update accordingly.
+
+### Standalone Search Mode
+Defines a search directly in the widget configuration, operating independently from other widgets. This mode is useful for fixed visualizations or separate analysis views that should not be affected by user interactions elsewhere on the page.
+
+## Design Considerations
+
+### When to Use Bar Chart
+- Showing distribution across discrete categories
+- Comparing frequencies of different values
+- Working with attributes that have a reasonable number of distinct values (fewer than 50)
+- Needing vertical/column representation for clarity
+
+### When to Consider Alternatives
+- **Too many values**: When the attribute has many distinct values, the chart becomes cluttered and hard to read
+- **Proportional data**: When showing percentages or proportions is more important than absolute counts, consider a pie chart
+- **Multi-dimensional analysis**: When comparing two attributes simultaneously, consider the Connected Matrix widget
+- **Continuous data**: For time-series or continuous numerical data, line charts may be more appropriate
+
+### Chart Characteristics
+- Vertical column chart with distinct colors for each bar
+- Y-axis zoom enabled for detailed inspection
+- Data labels showing count values on each bar
+- Tooltips on hover for additional detail
+- No legend (each bar represents a unique category)
+
+## Common Pitfalls
+
+- **Selecting attributes with too many distinct values**: Results in an unreadable, cluttered chart. Pre-filter data or choose attributes with limited cardinality.
+- **Not specifying a data source**: The widget requires either a connected table widget or a standalone search configuration.
+- **Standalone search targeting multiple types**: When using standalone search mode, the search must return entities of a single type for attribute selection to work.
+
+## Alternatives to Consider
+
+| Widget | When to Use Instead |
+|--------|---------------------|
+| `cf.platform.connectedPieChart` | When showing proportions/percentages is more important than absolute counts |
+| `cf.platform.connectedMatrix` | When analyzing relationships between two attributes |
+| `cf.platform.connectedNumberOfResults` | When only the total count matters, not distribution |
+
+## Related Patterns
+
+### Dashboard Pattern
+Multiple chart widgets (bar, pie, matrix) connected to the same table widget. The table provides interactive filtering, and all connected charts update together to reflect the filtered data.
+
+### Fixed Report Pattern
+Standalone charts with predefined searches, creating consistent visualizations that are not affected by user interactions. Useful for standardized reports and executive dashboards.

package/dist/widget-specifications/cf.platform.connectedBarChart/_summary.md

@@ -0,0 +1 @@
+Visualizes an attribute of a table or a search configurable in the widget as a bar chart. Connects to a table widget for synchronized filtering or uses a standalone search for independent visualizations.

package/dist/widget-specifications/cf.platform.connectedBarChart/search.md

@@ -0,0 +1,15 @@
+**Warning**: Search must have exactly ONE type filter AND ONE space filter to be valid!
+
+**Validation Requirements**:
+- The search configuration must define exactly one type
+- The search configuration must define exactly one space
+- If these requirements are not met, the widget displays an error
+
+**Correct Usage**: Use the `cplaceJson` field from a `cplace_search_pages` response.
+
+**Workflow**:
+1. Call `cplace_search_pages` with filters for the desired type and space
+2. Take the `cplaceJson` field from the response
+3. Use that value for the `search` attribute
+
+**Note**: This attribute is only used when `tableWidgetId` is not set. If both are configured, `tableWidgetId` takes precedence.

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

@@ -0,0 +1,12 @@
+{
+  "Widget": "cf.platform.connectedMatrix",
+  "Description": "{\"en\":\"Visualizes the content of a table broken down according to two search criteria.\",\"de\":\"Visualisiert den Inhalt einer Tabelle aufgeteilt nach zwei Suchkriterien.\"}",
+  "Localized Name": "{\"en\":\"Matrix\",\"de\":\"Matrix\"}",
+  "Icon": "fa-th",
+  "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>\n\n<p>The 'Matrix' widget displays the filtered content of table columns in the form of a grid pattern with an x and y axis.</p>\n\n<p>The x and y axes are formed on the basis of two attributes of the types by which the linked search table is filtered.</p>\n\n<p><strong>Settings</strong></p>\n\n<p>// * Table*:</p>\n\n<p>// * Title: Bilingual text.</p>\n\n<p>// * Height:</p>\n\n<p>// * Minimum width of matrix:</p>\n\n<p>// * Maximum row height:</p>\n\n<p>// * Label x-axis: Bilingual text.</p>\n\n<p>// * Attribute for x-axis*:</p>\n\n<p>// * Style x-axis*:</p>\n\n<p>// * Label y-axis: Bilingual text.</p>\n\n<p>// * Attribute for y-axis*:</p>\n\n<p>// * Style y-axis*:</p>\n\n<p>// * Attributes for icons</p>\n\n<p>// * Maximum number of results*:</p>\n\n<p>&nbsp;</p>\n\n<p><strong>Examples</strong></p>\n\n<div class=\"cplace-ckeditor-img-full-width\"><img alt=\"\" src=\"/file/9hzaox5ha1h4rz3hby692mqea/Product/cf.platform.connectedMatrix/2019-04-09-10-41-00-443.png\" width=\"1268\"></div>"
+}

package/dist/widget-specifications/cf.platform.connectedMatrix/_meta.json

@@ -0,0 +1,11 @@
+{
+  "tags": [
+    "matrix",
+    "searchable",
+    "connected",
+    "references",
+    "navigation",
+    "dashboard"
+  ],
+  "requiredApp": null
+}