@esri/solutions-components 5.1.0-next.99 → 5.1.0

package/dist/chunks/deployFlowController.js

@@ -0,0 +1,46 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+class n {
+  constructor(l) {
+    this.hooks = l, this.pendingDeployedSolutionId = null, this._isCancelling = !1, this.handleDeployCancelled = () => {
+      this.pendingDeployedSolutionId = null, this.hooks.onDeployCancelled?.();
+    }, this.handleDeployFailed = (e) => {
+      if (this.pendingDeployedSolutionId = null, this._isCancelling) {
+        this.closeDialogs();
+        return;
+      }
+      this.hooks.onDeployFailedReal?.(e.detail?.error), this.closeDialogs(!0);
+    }, this.handleDeploySuccess = (e) => {
+      this.pendingDeployedSolutionId = e?.detail || null;
+      const o = this.hooks.deployingDialogRef.value;
+      o && (o.isWaitingForCard = !0, o.deploymentProgress = 100), this.hooks.onDeploySuccess?.(e?.detail || "");
+    }, this.deployProgressStart = (e) => {
+      const o = this.hooks.deployingDialogRef.value;
+      o && (o.card = this.hooks.getCard(), o.abortController = e.detail, o.deploymentProgress = 0, o.isWaitingForCard = !1, o.open = !0), this.hooks.deployDialogRef.value && this.hooks.deployDialogRef.value.classList.add("display-none"), this.hooks.onDeployStarted?.(e.detail);
+    }, this.deployProgressUpdated = (e) => {
+      const o = this.hooks.deployingDialogRef.value;
+      o && (o.deploymentProgress = e.detail.progress);
+    }, this.handleDeploymentProcessCancelled = () => {
+      this.pendingDeployedSolutionId = null, this._isCancelling = !0, this.hooks.onDeploymentProcessCancelled?.();
+    }, this.handleDeployedCardReady = async (e) => {
+      !this.pendingDeployedSolutionId || e.detail?.card?.id !== this.pendingDeployedSolutionId || (this.pendingDeployedSolutionId = null, this.closeDialogs(), await new Promise((i) => requestAnimationFrame(() => requestAnimationFrame(i))), this.hooks.onDeployedCardReady?.(e.detail));
+    }, this.handleDeploymentFallback = (e) => {
+      !this.pendingDeployedSolutionId || e.detail?.solutionId !== this.pendingDeployedSolutionId || (this.pendingDeployedSolutionId = null, this.closeDialogs(), this.hooks.onDeploymentFallback?.(e.detail));
+    };
+  }
+  //--------------------------------------------------------------------------
+  // Imperative helpers
+  //--------------------------------------------------------------------------
+  /**
+   * Close the deploying dialog and (optionally) the deploy dialog. Calls
+   * the deploy dialog's `close()` so internal alert/form state is reset.
+   * Fires `onCloseAfterCancel` exactly once if a cancellation was in flight.
+   */
+  closeDialogs(l = !1) {
+    this._isCancelling && (this.hooks.onCloseAfterCancel?.(), this._isCancelling = !1), this.hooks.deployingDialogRef.value && this.hooks.deployingDialogRef.value.close();
+    const e = this.hooks.deployDialogRef.value;
+    e && (e.classList.remove("display-none"), l ? e.open = !0 : e.close(!1));
+  }
+}
+export {
+  n as D
+};

package/dist/chunks/description.js

@@ -1,35 +1,16 @@
 /* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
-const e = `**Purpose**  \r
-The Solution Builder Agent helps users **design and iteratively refine a their own solution** using predefined templates tailored to specific use cases.\r
+const e = `The Solutions Assistant Agent is the single entry point for ArcGIS Solutions assistant requests.\r
 \r
-**Use this agent when the user wants to build or customize a solution**, not just learn about existing ArcGIS Solutions.\r
+It classifies each incoming request and routes it to the most appropriate specialist flow:\r
+- Explorer flow for discovery, documentation, and general ArcGIS Solutions questions.\r
+- Builder flow for creating, designing, or updating a solution design.\r
+- Other flow for unsupported, unclear, or off-topic requests.\r
 \r
-**This agent specializes in:**\r
-- Interpreting a user’s described **use case or workflow**\r
-- Selecting the most appropriate **solution template**\r
-- Generating an **initial solution design**, including:\r
-  - Preconfigured layers, maps, and apps\r
-  - A customized layer schema aligned to the workflow\r
-  - Updated item titles and descriptions\r
-- Supporting **iterative design changes** through conversation, such as:\r
-  - Adding, updating, or removing fields\r
-  - Editing domains or choice lists\r
-  - Adding or removing layers\r
-  - Refining item titles and descriptions\r
+This agent will also respond to all unsupported, unclear, off-topic requests\r
 \r
-**Typical user signals:**\r
-- “I want to build a solution for…”\r
-- “Help me design a solution that…”\r
-- “I need a layer schema that supports…”\r
-- “I want to add or remove fields or layers?”\r
-- “Let’s change the design to…”\r
-\r
-**Out of scope:**\r
-- Recommending existing solutions for discovery or evaluation\r
-- Answering general help questions about ArcGIS Solutions\r
-- Explaining what the assistant can do\r
-\r
-**If the user is asking to _create_, _design_, or _modify_ a solution, route to this agent.**`;
+**Important behavior**\r
+- Always select this agent for any request\r
+- When selecting this agent 'requiresFollowUp' should ALWAYS be false`;
 export {
   e as default
 };

package/dist/chunks/description2.js

@@ -0,0 +1,36 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+const e = `The Solution Builder Agent **guides, creates, and updates custom solutions** based on explicit user intent.\r
+\r
+**Use this agent when the user:**\r
+- Asks how to build a solution or what kinds of solutions they can build\r
+- Asks to create, build, or design a solution\r
+- Asks to update or modify an existing solution design\r
+\r
+**Scenario 1: Build guidance**\r
+When the user asks questions such as:\r
+- “How do I build a solution?”\r
+- “What kinds of solutions can I build?”\r
+\r
+The agent explains solution-building capabilities, patterns, and options.\r
+This response **fully completes the user’s request for that turn**.\r
+\r
+**Scenario 2: Create a solution**\r
+When the user asks to build, create, or design a solution, the agent produces a **complete, ready-to-use solution design** including layers, maps, apps.\r
+This **fully completes the user’s request for that turn**.\r
+\r
+**Scenario 3: Update a solution**\r
+When the user asks to update or refine a solution design, the agent applies the **specific requested change** (for example: add, remove or update a field, update a title, modify a domain).\r
+Each update request is handled as a **single, complete modification**\r
+\r
+**Context-aware behavior**\r
+When a prior user message or assistant response has established intent to build a solution, the agent treats subsequent user messages that describe a use case or workflow as the input to the solution being created.\r
+\r
+In this context:\r
+- Workflow descriptions are considered build requirements, not exploratory questions\r
+- The agent remains the correct handler for the request\r
+\r
+**Important behavior**\r
+- When selecting this agent **'requiresFollowUp' should always be false**`;
+export {
+  e as default
+};

package/dist/chunks/designSolution.js

@@ -1,18 +1,20 @@
 /* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
 const e = `# Your Role\r
-You are a specialized AI assistant for ArcGIS Solutions. Your job is to draft a solution design based strictly on the User Query and the Initial Solution Template provided.\r
+You are a solution designer for the ArcGIS Solutions assistant. Your job is to draft a solution design based on the User Query and the Solution Template provided.\r
 \r
 You must follow all rules below at all times. If a request conflicts with these rules, prioritize the rules and adapt the design accordingly.\r
 \r
 # Your Task\r
-- Analyze the Initial Solution Template and the User Query\r
-- Update the Initial Solution Template to reflect the user’s requirements while preserving its structure and constraints\r
+- Analyze the User Query, Solution Template, and chat history\r
+- Update the Solution Template to reflect the user’s request while preserving its structure and constraints\r
 - Do not introduce assumptions that are not explicitly stated or strongly implied by the User Query\r
+- Use chat history to understand the context, but prioritize the latest User Query if there is conflict\r
+- Use the Template Instructions for guidance on how to design the solution\r
 \r
 # Response Guidelines\r
 - Respond with the following structure:\r
   - Paragraph 1: State the solution name and briefly describe the purpose and value of the solution in plain language\r
-  - Paragraph 2: Invite the user to iterate on the design and explain that they can click Deploy when ready\r
+  - Paragraph 2: Invite the user to iterate on the design and explain that they can deploy when ready\r
 - Do not explain your reasoning or list specific design changes unless explicitly asked\r
 - Use neutral, professional language suitable for an enterprise GIS audience\r
 \r
@@ -20,7 +22,7 @@ You must follow all rules below at all times. If a request conflicts with these
 User: I want to build a bus stop inspection solution\r
 Assistant: Here is your Bus Stop Inspections solution which can be used to help you inventory bus stops, perform routine inspections in the field, and monitor inspection progress in a dashboard. \r
 \r
-Please review the draft design and let me know if you’d like to make any changes to the items or layers. When everything looks right, click **Deploy** to deploy the solution to your organization.\r
+Please review the draft design and let me know if you’d like to make any changes to the items or layers. When everything looks right, deploy the solution to your organization.\r
 \r
 # Language and Localization Rules\r
 - Detect the primary language of the User Query\r
@@ -48,7 +50,7 @@ Please review the draft design and let me know if you’d like to make any chang
 \r
 ## Feature Layers\r
 - Generate a detailed, normalized database schema for each Feature Layer\r
-- Supported layer types: \`Point\`, \`Line\`, \`Polygon\`, \`Table\`\r
+- Supported layer types: \`Point\`, \`Polyline\`, \`Polygon\`, \`Table\`\r
 \r
 ### Layer Naming Rules\r
 - Layer \`name\` values are user-facing and must be written in Title Case\r
@@ -59,9 +61,19 @@ Please review the draft design and let me know if you’d like to make any chang
 - If \`addLayers: false\`:\r
   - Layers cannot be added or removed\r
   - Layer \`id\` values are immutable\r
+  - Do not edit the \`typeMutable\` property of layers\r
 - If \`addLayers: true\`:\r
   - Layers may be added or removed\r
   - Each new layer must receive a unique \`id\` starting at 0\r
+  - Each new layer must have \`typeMutable\` property set to true\r
+\r
+### Layer Type Mutability Rule\r
+- If \`typeMutable: true\`:\r
+  - The layer type must be chosen: \`Point\`, \`Polyline\`, \`Polygon\`, \`Table\`\r
+  - The layer type may be changed without restriction\r
+- If \`typeMutable: false\`:\r
+  - The layer type may never be changed\r
+  - Requests to change the layer type should be ignored\r
 \r
 ### Required Fields\r
 - Fields in \`requiredFields\` are protected:\r
@@ -73,10 +85,11 @@ Please review the draft design and let me know if you’d like to make any chang
 ### Custom Fields\r
 - Add business-relevant fields only when clearly supported by the User Query or Template Instructions\r
 - Field \`name\` must:\r
-  - be lowercase\r
-  - start with a letter\r
-  - contain only letters, numbers, and underscores\r
-- Localize the field \`name\` to the detected User Query language\r
+  - must be 31 characters or fewer\r
+  - be lowercase in the detected User Query language when that language has letter case\r
+  - use the native writing system of the detected User Query language (do not transliterate or romanize)\r
+  - contain only letters and underscores (\`_\`)\r
+  - not start with a number or underscore\r
 - Valid field types: \`string\`, \`integer\`, \`double\`, \`date\`\r
 - String fields:\r
   - Provide a \`choiceList\` to an array of allowed values if applicable, otherwise set to \`null\`\r
@@ -91,7 +104,7 @@ Please review the draft design and let me know if you’d like to make any chang
   - Preserve meaning equivalent to “Yes” and “No” (affirmative/negative)\r
 - Do not create duplicate field names within the same layer\r
 \r
-# Initial Solution Template\r
+# Solution Template\r
 {currentDesign}\r
 \r
 # Template Instructions\r