What this category's data looks like
This category’s data originates primarily from enterprise internal control systems, ERP platforms, financial sharing systems, audit management systems, and procurement contract project systems. The data update frequency is annual. Daily documents include internal control self-assessment reports, audit notices, audit working papers, issue lists, rectification ledgers, and rectification closure certificates. The document structure is fixed, with core fields covering issue descriptions, rectification requirements, supporting material associations, responsible entities, and other items. There are no frequently changing business fields.
What constraints do these characteristics place on the tool calling and plugins workflow
The heterogeneity of data sources requires tool calling to be configured with multi-data source adaptation plugins to pull audit and internal control documents from different systems. The fixed document structure requires functionCall to specify extraction of specific fields to avoid invalid content being included in the context. The annual update frequency allows plugins to be configured with a long cache refresh cycle to reduce resource consumption from repeated pulls. Additionally, this category involves compliance requirements. Tool calling must be linked to policy basis retrieval, and output content must comply with internal control audit compliance rules, so compliance check plugins must be configured.
How to set up the configuration
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | auto | Adapts to the multi-tool calling scenario of policy and regulatory basis Q&A, automatically matching compliance retrieval and document extraction tools |
functionCall | Specify extraction of issue description, rectification requirement, and supporting material fields | Matches the fixed field structure of documents in this category, ensuring extracted content meets business needs for audit rectification |
| Plugin data source configuration | Link to specified interfaces of internal control systems and audit management systems | Data sources are enterprise internal control, audit management, and other systems; precise pulling of corresponding business documents is required |
| Single tool call timeout period | 120–180 seconds | Pulling audit documents across systems requires longer processing time; reasonable thresholds are set based on actual measurements |
| Plugin cache refresh cycle | 365 days | The data update frequency of this category is annual; high-frequency cache refreshing is unnecessary to save resources |
| Maximum number of returned entries per single tool call | Top 20 entries | Avoids excessive documents causing context overflow, adapting to the precise retrieval needs of policy Q&A |
Three common configuration errors
- A plugin pull failure or container startup exception is displayed in the interface. The cause is failure to configure access whitelists for enterprise intranet systems, or failure to use plugin image sources adapted to intranet environments.
- Tool calling returns a large number of irrelevant documents that do not match policy and regulatory basis content. The cause is failure to specify document field filtering rules via
functionCall, and failure to link to audit-specific document types for this category. - Streamed output fails to filter non-compliant content as required, with expressions that do not meet compliance requirements appearing. The cause is failure to bind compliance check plugins, and failure to configure keyword filtering logic for streamed output.
How to confirm the configuration is complete
- Enter the FastGPT plugin management page, confirm that the status of configured data source interfaces shows normal operation.
- Initiate a test query, verify that tools automatically called via
toolChoicereturn category-specific documents such as internal control self-assessment reports and rectification ledgers. - Trigger tool calling, confirm that extraction results meeting field requirements are returned within the timeout period.
- Test the streamed output function, verify that the compliance keyword filtering logic takes effect, and irrelevant or non-compliant content is blocked.
The values provided are common starting points and should be measured against the reader's own samples.
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.