@arcgis/ai-components 5.1.0-next.98 → 5.2.0-next.0

package/dist/chunks/arcgisKnowledgeGraph.js

@@ -0,0 +1,174 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
+import { StateGraph as w, START as y, END as h } from "@langchain/langgraph/web";
+import { a as f, c as x, b as k, d as _, e as b, s as K, q as v, g as p, h as A, t as g, r as M, i as S, G as T, j as u } from "./adapter.js";
+import "@arcgis/core/identity/IdentityManager.js";
+import "@arcgis/core/portal/Portal.js";
+import { j as q, s as c, h as C } from "./generateLayerDescriptions.js";
+import { AIMessage as E } from "@langchain/core/messages";
+import "@langchain/core/callbacks/dispatch/web";
+import "@langchain/openai";
+import "@arcgis/core/core/reactiveUtils.js";
+import "@arcgis/core/layers/FeatureLayer.js";
+import "@arcgis/core/request.js";
+import { ToolNode as G } from "@langchain/langgraph/prebuilt";
+import "@langchain/core/prompts";
+const m = [
+  f,
+  x,
+  k,
+  _,
+  b,
+  K,
+  v
+];
+async function R(e, o) {
+  const l = await p("arcgis_knowledge_tool_prompt"), a = A(o), r = {
+    assignedTask: e.agentExecutionContext.assignedTask,
+    userRequest: e.agentExecutionContext.userRequest,
+    priorSteps: e.agentExecutionContext.priorSteps,
+    contextType: a
+  }, n = await q({
+    promptText: l,
+    messages: e.arcgisKnowledgeMessages,
+    inputVariables: r,
+    tools: m
+  }), t = (n.tool_calls?.length ?? 0) > 0, s = typeof n.text == "string" ? n.text.trim() : "", i = s.length > 0, d = n.content.toString();
+  return !t && (a === "map" || a === "knowledgeGraph") ? {
+    ...e,
+    arcgisKnowledgeMessages: [...e.arcgisKnowledgeMessages, n],
+    outputMessage: a === "map" ? "No tools were found for the current view and prompt. Maps do not support changing nonspatial visibility, layout changes, or generation from queries." : "No tools were found for the current prompt and knowledge graph service. A knowledge graph service only supports search and query.",
+    status: "success"
+  } : {
+    ...e,
+    arcgisKnowledgeMessages: [...e.arcgisKnowledgeMessages, n],
+    outputMessage: t ? d : s,
+    status: t ? e.status : i ? "success" : "failed",
+    summary: d ? g(d) : "ArcGIS Knowledge Agent tool executed."
+  };
+}
+async function N(e, o) {
+  const l = new G(m);
+  try {
+    const a = await l.invoke(
+      {
+        messages: e.arcgisKnowledgeMessages
+      },
+      o
+    ), r = [];
+    for (const t of a.messages) {
+      let s;
+      if (typeof t.content != "string")
+        throw new Error(`Unexpected tool message content type: ${typeof t.content}. Expected string.`);
+      try {
+        s = JSON.parse(t.content);
+      } catch {
+        throw new Error(`Failed to parse tool message content as JSON. Tool: ${t.name ?? "unknown"}`);
+      }
+      if (!s || typeof s != "object" || !("toolName" in s))
+        throw new Error(
+          `Parsed tool message content does not have expected structure. Parsed content: ${JSON.stringify(s)}`
+        );
+      r.push(s);
+    }
+    await c(
+      {
+        text: `Finished executing ArcGIS Knowledge Agent tools: ${a.messages.filter((t) => t.name).map((t) => t.name).join(", ")}`
+      },
+      o
+    );
+    const n = r.filter((t) => typeof t != "string").map((t) => `- Called Tool: ${t.toolName}, Status: ${t.status}`);
+    return {
+      ...e,
+      outputMessage: n.join(`
+`),
+      summary: n.length ? g(n.join(`
+`)) : "ArcGIS Knowledge Agent did not execute any tools or return any results.",
+      arcgisKnowledgeMessages: [...e.arcgisKnowledgeMessages, ...a.messages],
+      arcgisKnowledgeToolResult: r
+    };
+  } catch (a) {
+    const r = a instanceof Error ? a.message : String(a);
+    return await c({ text: `ArcGIS Knowledge Agent tool execution failed: ${r}` }, o), {
+      ...e,
+      outputMessage: `ArcGIS Knowledge Agent tool execution failed: ${r}`,
+      status: "failed",
+      summary: `ArcGIS Knowledge Agent tool execution failed: ${r}`,
+      arcgisKnowledgeMessages: [...e.arcgisKnowledgeMessages]
+    };
+  }
+}
+const L = (e, o) => (
+  //agent services (ex: embeddingsWorker) would go in the array below, if required.
+  M([], "ArcgisKnowledge Agent")(e, o)
+);
+async function z(e, o) {
+  const a = (e.arcgisKnowledgeToolResult ?? []).map((d) => ({
+    ...d,
+    details: void 0
+    // Remove details to avoid overwhelming the LLM with too much info
+  })), { knowledgeGraph: r } = await S(o), n = T.getDataModelTypesSummary(r.dataModel), t = {
+    assignedTask: e.agentExecutionContext.assignedTask,
+    userRequest: e.agentExecutionContext.userRequest,
+    toolResult: a,
+    dataModelSummary: n
+  }, s = await C({
+    promptText: await p("arcgis_knowledge_summarize_result_prompt"),
+    modelTier: "default",
+    inputVariables: t
+  }), i = typeof s == "string" ? s : s.content;
+  return {
+    ...e,
+    outputMessage: i,
+    status: "success",
+    summary: g(i),
+    arcgisKnowledgeMessages: [...e.arcgisKnowledgeMessages, new E(i)]
+  };
+}
+const D = () => new w(u).addNode("requireArcgisKnowledgeServices", L).addNode("agent", R).addNode("tools", N).addNode("summarizationLLM", z).addEdge(y, "requireArcgisKnowledgeServices").addEdge("requireArcgisKnowledgeServices", "agent").addConditionalEdges("agent", (o) => (o.arcgisKnowledgeMessages[o.arcgisKnowledgeMessages.length - 1]?.tool_calls?.length ?? 0) > 0 ? "tools" : h).addConditionalEdges("tools", (o) => o.status === "failed" ? h : "summarizationLLM").addEdge("summarizationLLM", h), F = String.raw`The purpose of this agent is to work with Knowledge Graph data, a graph database technology that represents and stores data as interconnected entities (nodes) and relationships (edges).
+This agent has two categories of skills: those that work with an active link chart visualization of a subset of the data in the knowledge graph, and those that work with the knowledge graph data more generally against the entire dataset in the service and database.
+For link charts, the agent enables users to interact with a link chart by adding new entities (also called nodes) or relationships (also called edges), removing existing entities or relationships, 
+expanding the graph from particular entities, finding relationships between specified entities on the link chart and adding them to the link chart, finding all relationships 
+that exist out from specified entities and adding those to the link chart, changing whether or not nonspatial data is visible, or changing the layout of the link chart.  
+This agent is designed to handle requests that manipulate the specific link chart.
+For knowledge graph data more generally, the agent can generate Open Cypher queries based on user prompts that represent inquiries into the data of the knowledge service and its graph database,
+and can alternatively use those queries to create a new link chart visualization from the results if requested.
+
+Supported actions:
+- **Change or Apply Layout**: Changes the current layout visualization strategy of the link chart  (e.g., "Change the layout to basic-grid", "Apply hierarchical layout").  Valid layout types include organic-standard, organic-community, basic-grid, hierarchical-bottom-to-top, radial-root-centric, tree-left-to-right, geographic-organic-standard, chronological-mono-timeline.  A best effort should be made to transform the user's request into one of these layout types.
+- **Change Nonspatial Data Visibility**: Changes whether or not nonspatial data is visible on the link chart (e.g., "Show nonspatial data", "Hide nonspatial data").  Valid settings are "hidden" and "visible".  A best effort should be made to transform the user's request into one of these settings.
+- **Generate a cypher query**: Generates an Open Cypher query based on the user's prompt which represents an inquiry into the data of the knowledge service and its graph database, attempting to filter based on certain conditions and traverse specified relationships. The generated query should be syntactically correct and optimized for performance.  The user should explicitly request that a cypher query be returned - if they do not, the purpose of the query is for one of the other tools or skills.
+- **Create a New Link Chart from a user prompt**: Identifies that the users prompt is an inquiry into the data of the knowledge service and its graph database and creates a new link chart from the results.  The user should have requested that a link chart be created or made(or similar term) from their prompt
+- **Add Records (entities or relationships)**: Identifies that the users prompt is an inquiry into the data of the knowledge graph service and its graph database, and that the user wants to take the result of the inquiry and add those entities and/or relationships to the link chart.  The generated query should be syntactically correct and optimized for performance.
+- **Search Graph Data**: Generates and runs a lucene syntax query based on the user's prompt, returning matching entity and relationship records from the knowledge graph.
+- **Query Graph Data**: Generates and executes a cypher query based on the user's prompt, and displays the results in the chat pane, allowing the user to explore the data in their knowledge graph.
+
+_example: "Change the layout to hierarchical-bottom-to-top"_  
+_example: "Apply radial-root-centric layout"_  
+_example: "Show nonspatial data"_  
+_example: "Hide nonspatial data"_
+_example: "Turn off nonspatial visibility"_
+_example: "Generate a cypher query to find all entities connected to 'Entity A' via 'Relationship X' that were created after 2020"_
+_example: "Generate a query to find all employees of Company Esri who joined after 2015 and are located in California"_
+_example: "Tell me how to find all products supplied by Supplier Y that have a price greater than $1000"_
+_example: "Create a new link chart showing all entities related to 'Entity B' through 'Relationship Y'"_
+_example: "Find all people who work for Microsoft and put them on a new link chart"_
+_example: "Add all entities connected to 'Entity C' via 'Relationship Z' to the current link chart"_
+_example: "Add all the people who work for Esri to the current link chart, and all the cars that they drive"_
+_example: "Find all the products supplied by Supplier X and add them to my visualization"_
+_example: "Expand the link chart from 'Entity D' to show its direct connections"_
+_example: "Find all the cars and then add everything up to two hops away from them on the link chart"_
+_example: "Connect Emma and Rob on the link chart if there is a relationship between them"
+_example: "Discover and add all the relationships originating at 'Entity E' to the link chart"_
+_example: "Show me all entities with a name similar to 'Smith' and add them to the link chart"_
+_example: "Find reports in my graph that have a title similar to 'Quarterly Earnings'"_
+_example: "Find John Smith and all people he has made phone calls to in the last year"_
+_example: "What is the average age of all people who work for Esri?"_`, W = {
+  id: "arcgisKnowledge",
+  name: "ArcgisKnowledge Agent",
+  description: F,
+  createGraph: D,
+  workspace: u
+};
+export {
+  W as A
+};

package/dist/chunks/arcgis_knowledge_current_lc_context.js

@@ -0,0 +1,8 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
+const e = `## Additional System Context
+
+In addition to the user's inquiry prompt that precedes this system context, the current link chart has entities and relationships on it already, in the format of an array of objects containing identifiers and typeNames, in case this is needed for query generation (for example 'Add all records that are connected to people on this link chart to the link chart'). If the user is asking for a query that acts on 'the current link chart', 'my link chart', or similar then the cypher query should be filtered by the ids. For example, 'Match (n:Person)-[\\r]->(m) WHERE id(n) IN [\\'identifier1','identifier2'] return r, m. Curly braces (the '{' and '}' characters) are often part of identifier strings and should not be stripped out - the process of filtering by ids should not be altering the id strings. The entities and relationships that are on the current link chart are as follows:
+`;
+export {
+  e as default
+};

package/dist/chunks/arcgis_knowledge_current_map_context.js

@@ -0,0 +1,8 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
+const e = `## Additional System Context
+
+In addition to the user's inquiry prompt that precedes this system context, the current map has entities and relationships on it already, in the format of an array of objects containing identifiers and typeNames or type names that contain all entities or relationships of that type, in case this is needed for query generation (for example 'Add all records that are connected to people on this map to the map'). If the user is asking for a query that acts on 'the current map', 'my map', or similar then the cypher query should be filtered by the ids. For example, 'Match (n:Person)-[\\r]->(m) WHERE id(n) IN [\\'identifier1','identifier2'] return r, m. Curly braces (the '{' and '}' characters) are often part of identifier strings and should not be stripped out - the process of filtering by ids should not be altering the id strings. The entities and relationships that are on the current map are as follows:
+`;
+export {
+  e as default
+};

package/dist/chunks/arcgis_knowledge_lucene_generation_prompt.js

@@ -0,0 +1,101 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
+const e = `## ArcgisKnowledge Agent - Lucene Generation for Graph Search
+
+You are an assistant that generates a lucene query for graph query searching.
+
+The knowledge graph you will be searching has the following named types, and next to each named type is a list of its searchable text fields corresponding to graph properties.
+
+The search model data below is structured as follows:
+<TYPE_NAME> - [array, of, searchable, field, names]
+
+{dataModelForSearch}
+
+The user is trying to answer the following inquiry via text search:
+{inquiry}
+
+Return a lucene search query that will answer the user's inquiry. The generated response should be an object with the following properties:
+
+- \`query\` - string - the generated lucene query expression that answers the user's inquiry.
+- \`typeFilters\` - array of strings - restricts the search to only use the named types specified. If the search should not be restricted to specific named types, return null.
+- \`typeCategoryFilter\` - either 'entity', 'relationship' or 'both' - determines whether search should be limited to only entity or relationship types, or to search both. Generally should be set to 'entity' unless the user specifies they want to search both record types or specifically mentions relationships or refers to relationship types in their inquiry. If 'entity' is selected, then no relationship types should be included in \`typeFilters\` and vice-versa.
+- \`resultLimit\` - number (min 1) or null - the max number of search results to return. Set to 10 unless the user specifies they want a specific number of results returned. If the user specifically requests all search results to be returned or that the results should not be limited, return null.
+
+Additional rules for the generated arguments:
+
+- Only include specific search fields in the lucene query expression if the user inquiry specifies specific fields or properties, and the fields are present in the searchable field list of the corresponding named type shown above, otherwise search across all fields.
+- If the user's inquiry is specific to certain entity or relationship types in the graph, then return those types as the \`typeFilters\` property. Do not attempt to use search fields for this purpose. If no specific type filtering is requested or needed, then return null for this property.
+- Regular expressions are not supported in the lucene search syntax, so do not include such queries in the \`query\` property.
+
+**START EXAMPLE**
+
+### Example searchable property data:
+
+Entity Types:
+Author - [name, title]
+Report - [organization, summary, full_text, tags]
+
+Relationship Types:
+authored - [contribution_type]
+
+Searchable fields per type:
+
+Author:
+name
+title
+
+Report:
+organization
+summary
+full_text
+tags
+
+authored:
+contributionType
+
+### User Inquiry 1:
+
+Find the first 5 reports where summary mentions flood zoning near Sacramento, and the organization name is close to City of Sacramento Utilities, and tags containing stormwater.
+
+### Example generated query arguments 1:
+
+query: 'summary:"flood zoning" AND summary:Sacramento AND organization:"City of Sacramento Utilities"~2 AND tags:stormwater'
+
+typeFilters: ['Report']
+
+typeCategoryFilter: "entity"
+
+resultLimit: 5
+
+### User Inquiry 2:
+
+Find entities containing text like 'City of Sacramento Utilities'
+
+### Example generated query arguments 2:
+
+query: '"City of Sacramento Utilities"~2'
+
+typeFilters: null
+
+typeCategoryFilter: "entity"
+
+resultLimit: 10
+
+### User Inquiry 3:
+
+Find all reports authored by someone with the title of 'Researcher'
+
+### Example generated query arguments 3:
+
+query: 'title:"Researcher"'
+
+typeFilters: ['Author']
+
+typeCategoryFilter: "entity"
+
+resultLimit: null
+
+**END EXAMPLE**
+`;
+export {
+  e as default
+};

package/dist/chunks/arcgis_knowledge_summarize_result_prompt.js

@@ -0,0 +1,48 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
+const e = `## ArcgisKnowledge Agent - Action Summary
+
+You are a helpful Knowledge Graph assistant agent that has received a user inquiry and performed some tool call actions to answer their question or perform the desired operation.
+
+The knowledge graph you are working with has the following data model:
+
+{dataModelSummary}
+
+## User Input:
+
+Assigned task:
+{assignedTask}
+
+Latest user request:
+{userRequest}
+
+## Tool Call Result:
+
+{toolResult}
+
+## Your Goal:
+
+Based on the user request and tool call result above, generate a concise response that answers their question fully.
+
+If the above tool calls do not provide the information required to answer the users question, state this, and do not speculate.
+
+The general format for the summary should be (paragraphs of content separated by new lines, not bullet points):
+
+- A short, easy to read summary of the results and answer to the users inquiry, in the form of a concise 1-3 sentence summary. This can include the tool called and a brief summary of its settings. For multiple or complex settings (e.g. cypher or search query), these should instead be displayed in the code block below. It should always include any limitations in the results that the user should be aware of.
+- _Optional_ - Code block containing tool settings / query or search used etc for tool calls with multiple or complex settings
+- _Optional_ - Markdown table of query or search results preview if these tools were used, and this is appropriate to answer the user's question. Ensure long property values are truncated to short lengths (20 chars) in the table if not directly relevant to the user's query. Do not re-order data in the table. If a query or search of graph data was done, this should be displayed.
+- _Important_ If the summary or markdown table was generated based on data where only a limited preview of the full results of e.g. a search/query was available, indicate this at the end of the summary in a separate paragraph in italics, along the lines of 'NOTE: This summary was generated from a limited preview of the search / query results, and may not be accurate.'
+
+### STRICT OUTPUT RULES
+
+- Do NOT ask follow-up questions.
+- Do NOT offer additional actions or suggestions.
+- Do NOT explain what you can do next.
+- End the response immediately after the summary.
+- Do NOT include introductory phrases (e.g., "Found", "Here are", "The results show").
+- Do NOT restate the assigned task or user’s question.
+- Use Markdown formatting for the response, formatting in a way that makes the summary easy to read.
+- When presenting tabular data, output a valid Markdown table.
+`;
+export {
+  e as default
+};

package/dist/chunks/arcgis_knowledge_tool_prompt.js

@@ -0,0 +1,34 @@
+/* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
+const e = `# ArcgisKnowledge Tool Instructions
+
+You are an assistant that helps users answer questions and perform operations on their knowledge graph, map or link chart. You have been assigned the task below, which must be achieved by calling a single tool.
+
+## Task Details:
+
+Assigned task:
+{assignedTask}
+
+User Request:
+{userRequest}
+
+Prior steps:
+{priorSteps}
+
+Context type:
+{contextType}
+
+## Rules:
+
+1. Use the provided context type above for the following rule. If the context type is a map, you may never call any of the following arcgisKnowledge tools: changeNonspatialVisibility, applyLayout, createLinkChart.
+
+2. Use the provided context type above for the following rule. If the context type is a knowledgeGraph, you may never call any of the following arcgisKnowledge tools: changeNonspatialVisibility, applyLayout, createLinkChart, addRecords.
+
+3. If no tools apply to the assigned task, return zero tool calls and an empty message.
+
+4. If a tool is found for the assigned task, call exactly one arcgisKnowledge tool, with the appropriate arguments given the assigned task. Use the provided user request or prior steps only if needed for context based on the assigned task.
+
+5. CRITICAL: You are FORBIDDEN from making multiple tool calls. You MUST make exactly ONE tool call or ZERO tool calls.
+`;
+export {
+  e as default
+};

package/dist/chunks/converterUtils.js

@@ -1,4 +1,4 @@
-/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
+/* COPYRIGHT Esri - https://js.arcgis.com/5.2/LICENSE.txt */
 import g from "@esri/arcgis-html-sanitizer";
 import { marked as S } from "marked";
 S.use({