- Cross-System Automatic Data Synchronization:
- Through preset variables, information flows seamlessly between multiple systems. Solvea can directly call synchronized data to execute processes, eliminating repetitive information collection and improving processing efficiency.
- 🌰 Example: In some customer ticketing systems, the system can automatically retrieve relevant customer information (e.g., an order number). If this information is preset as a system variable, when the ticket workflow is handed over to Solvea for processing, simply referencing the corresponding variable name allows Solvea to automatically fetch and display the detailed information associated with that variable.
- Multi-Node Information Consistency Assurance (especially in Multi-Agent scenarios):
- By using globally unique identifiers (variables) as information anchors, Solvea can stably track core data during multi-stage processing in complex flows, avoiding the risk of information misalignment during cross-node transfers.
- 🌰 Example: When a Multi-Agent system involves multiple individual Agents, complex processes can lead to confusion in the transfer of key information. If crucial information (like an order number) is set as a variable, this variable acts as a fixed unique ID. When Solvea switches between different Agents, merely mentioning the variable allows Solvea to accurately extract its value.
🌟 Note: After ticket integration, AI Fields prioritize extracting data from Metadata.
🌰 FAQ 1: How is a variable extracted if the order number provided by the user differs from the order number in the Metadata?
If the OrderNumber field in the Metadata is “##SV123456“, but the user’s message indicates the order number is “123456“, the variable named OrderNumber will prioritize the value “##SV123456” and define it as the order number.
In short: When the order number provided by the user is inconsistent with the order number in the Metadata, AI Fields will use the data from the Metadata.
🌰 FAQ 2: How is a variable extracted if the user does not provide an order number, but an order number exists in the Metadata?
If the OrderNumber field in the Metadata is “##SV123456“, but the user’s message does not contain any order information, the variable named OrderNumber will still take the value “##SV123456” and define it as the order number.
In short: When the user does not provide an order number, but an order number exists in the Metadata, AI Fields will use the data from the Metadata.
