@cplace/mcp-server 1.5.3 → 1.6.0

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/_implementation.md

@@ -0,0 +1,42 @@
+## Specialized Configuration Tools
+
+Use these dedicated tools for resource planner widget configuration:
+
+| Tool | Purpose |
+|------|---------|
+| `cplace_resource_planner_get_configuration` | Get current config in friendly grouped format |
+| `cplace_resource_planner_configure_data_source` | Configure node search and date calculation |
+| `cplace_resource_planner_configure_groups` | Configure optional first/second grouping layers |
+| `cplace_resource_planner_configure_columns` | Configure attributesConfiguration and defaultColumnsConfiguration |
+| `cplace_resource_planner_configure_display` | Configure visual/display settings (partial updates) |
+
+**Workflow**:
+1. Add resource planner widget using `cplace_define_layout` / `layout.define()` with type `cf.cplace.resourceManagement.resourcePlannerDefinition`
+2. Configure data source: `cplace_resource_planner_configure_data_source` (node search + date calculation)
+3. Configure display: `cplace_resource_planner_configure_display` (intervals, colors, tree structure)
+4. Optionally configure groups: `cplace_resource_planner_configure_groups`
+5. Configure columns: `cplace_resource_planner_configure_columns` (attributes and default columns)
+
+**Get-Modify-Set Pattern**:
+1. Call `cplace_resource_planner_get_configuration` to get current state
+2. Modify the relevant section
+3. Call the corresponding configure tool with the complete desired state
+
+**Configuration Modes**:
+
+**Date Calculation** (via `dateCalculation`):
+- `STATIC`: Fixed start/end dates → activates `start`, `end`
+- `DYNAMIC`: Relative offset from today → activates `startValueDynamic`, `startUnitDynamic`, `endValueDynamic`, `endUnitDynamic`
+- `ATTRIBUTE`: Read from entity attributes → activates `startDateAttribute`, `endDateAttribute`
+
+**Optional Groups**:
+- `checkboxFirstGroup: true` → activates `searchFirstGroup`, `sortColumnFirstGroup`, `sortOrderFirstGroup`, `firstGroupSelection`, `firstGroupName`
+- `checkboxSecondGroup: true` → activates `searchSecondGroup`, `sortColumnSecondGroup`, `sortOrderSecondGroup`, `secondGroupSelection`, `secondGroupName`
+
+**App-Conditional Sections** (configure via generic layout tools):
+- Actions app installed → activates `actionSearch`, `sortColumnAction`, `sortOrderAction`, `actionSelection`
+- Chart app installed → activates `chartSearch`, `sortColumnChart`, `sortOrderChart`, `chartSelection`
+
+**Search Triplet Pattern**: Node selection, groups, root nodes, actions, and charts all follow the same pattern: a search attribute (use cplaceJson from cplace_search_pages) + sort column + sort order.
+
+**Version**: The `version` attribute is always set to `V2`. V1 is legacy and auto-migrated. Do not set manually.

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/actionSearch.md

@@ -0,0 +1,10 @@
+**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 this attribute
+
+**Note**: This attribute is only available when the Actions app is installed in the workspace.

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/attributesConfiguration.md

@@ -0,0 +1,30 @@
+Configure via `cplace_resource_planner_configure_columns` tool.
+
+**JSON Format** (stored as stringified JSON):
+```json
+{
+  "columns": [
+    {
+      "feature": "cf.cplace.resourceManagement.startDate",
+      "header": "Start Date",
+      "builtin": true,
+      "visible": true
+    },
+    {
+      "feature": "cf.cplace.myApp.customAttribute",
+      "header": "Custom Field",
+      "builtin": false,
+      "visible": false
+    }
+  ]
+}
+```
+
+Each column entry requires all 4 fields:
+- `feature`: Fully-qualified attribute name
+- `header`: Display name shown in column header
+- `builtin`: `true` for built-in columns, `false` for custom attribute columns
+- `visible`: Whether the column is visible by default
+
+Full replacement semantics — the provided array completely replaces the current configuration.
+Use `cplace_resource_planner_get_configuration` to read current columns before modifying.

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/chartSearch.md

@@ -0,0 +1,10 @@
+**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 this attribute
+
+**Note**: This attribute is only available when the Chart app is installed in the workspace.

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/dateCalculation.md

@@ -0,0 +1,8 @@
+**Warning**: This is a mode selector that controls which period attributes are active!
+
+**Valid Values**:
+- `STATIC`: Fixed start/end dates (activates `start` and `end` date attributes)
+- `DYNAMIC`: Relative to today (activates `startValueDynamic`, `startUnitDynamic`, `endValueDynamic`, `endUnitDynamic`) — most common
+- `ATTRIBUTE`: Read from entity attributes (activates `startDateAttribute`, `endDateAttribute`)
+
+**Note**: Only the period attributes corresponding to the selected mode are active. The others are hidden and ignored.

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/defaultColumnsConfiguration.md

@@ -0,0 +1,7 @@
+Configure via `cplace_resource_planner_configure_columns` tool.
+
+Uses the same JSON format as `attributesConfiguration` — see that attribute's documentation for the column structure.
+
+This attribute controls which columns are visible by default when the widget loads. The `visible` field in each column entry determines default visibility.
+
+Full replacement semantics — use `cplace_resource_planner_get_configuration` to read current state before modifying.

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/searchFirstGroup.md

@@ -0,0 +1,8 @@
+**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 this attribute

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/searchNode.md

@@ -0,0 +1,8 @@
+**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 this attribute

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/searchRootNode.md

@@ -0,0 +1,10 @@
+**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 this attribute
+
+**Note**: Root node searches often use relative UID filters. When using `relativeReference` filters, provide a real page UID as `embeddingEntityUid` — without it, the relative filter won't be included in the returned cplaceJson.

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/searchSecondGroup.md

@@ -0,0 +1,8 @@
+**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 this attribute

package/dist/widget-specifications/cf.cplace.resourceManagement.resourcePlannerDefinition/treeStructure.md

@@ -0,0 +1 @@
+**Note**: Values represent hierarchy attributes defined on the node type. The dynamic enumeration lists attributes that can establish parent-child relationships for tree display. Select the attribute(s) that define how nodes are organized hierarchically.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cplace/mcp-server",
-  "version": "1.5.3",
+  "version": "1.6.0",
   "description": "MCP server that provides Claude Desktop with tools to interact with cplace APIs",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",