What data for this category looks like
The typical users of this category are enterprise IT administrators, OA administrators, and business process administrators. The documents they create and maintain daily include process configuration sheets, approval node tables, form field descriptions, and change records. Data sources mainly come from OA systems, organizational structure data, internal system documents, and user feedback. Updates are triggered by process changes, usually at least once per month. The most time-consuming work links are approval rule sorting, node permission configuration, and test verification. Errors may cause approval freezes, permission mistakes, or deviations in system implementation. Unlike the identity account and permission management category, this category focuses on business approval paths and form configuration.
What constraints do these characteristics impose on the tool calling and plugins link
The structured nature of daily documents requires tool calling parameters to match specific configuration items such as approval nodes and form fields, to avoid disconnects between calling results and process logic. The low data update frequency means the plugin calling result caching strategy must adapt to the change rhythm, reducing resource consumption from repeated calls. The serious consequences of errors require that failure retry and exception alert mechanisms be configured for the tool calling link, to prevent process blockages. Additionally, most work scenarios for this category involve internal office system integrations, so the permission scope of tool calls must be strictly limited to internal enterprise resources to avoid unauthorized access.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | auto | Adapts to the multi-step approval calling requirements of office process configuration, automatically matching the tool type for corresponding nodes |
functionCall | enabled | Supports calling custom plugins to complete process configuration logic such as approval rule verification and permission validation |
| Plugin call timeout | 300 seconds | Matches the standard response duration of office process approval nodes, avoiding blocking the overall process |
| Plugin return result cache duration | 7 days | Adapts to the monthly update frequency of data changes for this category, balancing real-time performance and resource usage |
| Number of plugin call results per single call | Top 10 | Adapts to the approval node information display requirements of office process configuration, avoiding information overload |
Three common mistakes
- When calling a custom plugin, returning the fixed domain name
api.example.comcauses access failures. This occurs because the actual API domain name of the enterprise internal OA system was not substituted in the plugin configuration. - Calling the
/api/core/dataset/updateinterface returns a 500 error, while browser access works normally. This occurs because the API call permission whitelist for office system process configuration was not configured, causing the interface to be blocked. - Streaming output cannot be implemented when calling other models in the workflow. This occurs because the streaming callback configuration corresponding to
functionCallwas not enabled, or the output format requirements of the approval nodes for office process configuration were not matched.
How to confirm configurations are correctly set
- Initiate a simulated approval process to trigger plugin calls, and check whether the returned results match the preset approval rules and form field requirements.
- View the plugin call logs in FastGPT v4.17.0 to confirm that the configuration parameters for
toolChoiceandfunctionCallhave been loaded normally. - Test interface calls to verify that the configured timeout duration and cache duration meet expectations, with no abnormal errors.
- Submit an official process configuration change, observe the process running status, and confirm that no blockages or permission exceptions occurred during plugin calls.
The values listed here are common starting points, and should be evaluated 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-10-19.