What the data for this category looks like
Data is sourced from the State-owned Assets Supervision and Administration Commission (SASAC) investment supervision system, enterprise ERP and project management systems, industry market data, audit and financial statements. Updates occur on a quarterly basis. Commonly involved documents include annual investment plans, project proposals, feasibility study reports, due diligence reports, asset appraisal reports, and post-investment evaluation reports. The data covers business circulation information for four types of entities: central enterprise strategic investment departments, project companies, state-owned assets supervision departments, and external consulting and evaluation institutions. Fields are configured around the approval, investment decision process, and post-investment management stages of the full investment project lifecycle. No unified cross-system field standard exists.
Constraints on Workflow Orchestration
The multi-source, heterogeneous nature of the data requires workflow configuration to adapt to access formats of different data sources, including the SASAC investment supervision system and enterprise ERP. The variables parameter is used to uniformly connect data from multiple systems. The quarterly update frequency requires workflows to include synchronization nodes triggered on a quarterly basis, to ensure timeliness of documents such as annual investment plans and feasibility study reports. Document types cover the entire investment cycle. Workflows must assign circulation paths for different documents according to stages including project approval, investment decision, and post-evaluation, to match risk control requirements for state-owned assets supervision. For data related to state-owned assets, workflows must use the nodeId configuration to distinguish permission nodes for each stage, to prevent unauthorized operations. A failure handling link must also be reserved to address data anomalies or process interruptions.
Configuration Setup
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting Method | Rationale |
|---|---|---|
variables | Divide variable groups by project stages, including project number, investment budget, and core post-evaluation indicators. Values are determined through actual measurement | Covers core business data across the full investment project lifecycle, adapts to the data format requirements of multi-system docking |
nodeId | Set consecutive numbers according to project approval, investment review committee evaluation, and post-investment evaluation, with values ranging from 1001 to 1003 | Matches the stage permission division of state-owned assets supervision, clarifies the operation boundaries of each workflow node |
| HTTP call timeout setting | 600 seconds | Data return takes a long time when connecting to the SASAC investment supervision system and external consulting institution data |
| Variable optional value configuration | Pre-set two optional values: project application and post-evaluation report | Matches the document classification of daily business, reduces manual input errors |
| Scheduled trigger configuration | Trigger quarterly | Matches the quarterly update frequency of data in this category, ensures the timeliness of synchronized data |
Three Common Configuration Errors
- Phenomenon: After configuring optional variable values for a custom tool, preset options fail to display when calling, and the tool parameter configuration bar is blank. Cause: The enumeration range of optional values is not declared in the
variablesconfiguration, only static variable values are configured. - Phenomenon: When using an HTTP node to call a Peanut Shell address, an EN-class getaddrinfo error is returned. Cause: Trust rules for intranet penetration addresses are not configured, or the workflow does not allow access to external interfaces of non-public domain names.
- Phenomenon: Variable values in the workflow always remain as the initially written fixed content, and cannot be updated along with business stages. Cause: No variable update node is added to the workflow, and the
variablesparameter is not used to bind output data from subsequent nodes.
How to Verify a Complete Configuration
- Check whether the variable groups configured in
variablescover the required fields of the three core stages: project approval, investment decision, and post-evaluation. - Verify whether the HTTP node timeout setting matches the average response duration of the connected system, which can be confirmed through a single test call.
- Confirm whether the node ID allocation of the workflow is consistent with the stage permission requirements of state-owned assets supervision, with no unauthorized node configurations.
- Trigger the scheduled trigger task, and confirm whether the latest business documents are synchronized according to the preset cycle.
The values provided here are common starting points, and should be measured against the specific samples of the target deployment environment.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.