This page is compatible with FastGPT v4.17.0.
What this category of data looks like
This category of data originates from databases, data dictionaries, masking tools, and access approval systems. It is updated per batch or single project. Daily associated documents include masking plans, field mapping tables, masking verification reports, and approval records. Core fields cover sensitive field identifiers, masking rule types, verification results, and approval status. No unified fixed units apply; adjustments are made based on project scenarios. Core data processing steps include sensitive field identification, rule configuration, and availability verification. Improper processing can lead to personal information leakage, data unavailability, or compliance audit failure.
What constraints do these characteristics impose on the "workflow orchestration" link
The batch update per project feature requires workflows to isolate variables and configurations by project. This prevents cross-project data confusion. The presence of multiple associated document types requires workflows to integrate document reading and field mapping nodes. This ensures accurate sensitive field identification and rule configuration. High compliance requirements for sensitive information processing require workflows to include built-in audit nodes. These nodes record execution logs for every masking operation. Scattered data sources require workflows to support multiple data source node connections. This automatically pulls sensitive field information from databases and data dictionaries, reducing manual entry errors.
How to set configurations
| Configuration Item | Recommended Setting | Rationale for This Setting |
|---|---|---|
variables scope configuration | Isolate per project | Data is updated in batches per project, avoids cross-project data confusion |
nodeId binding | Link to masking execution child nodes | Facilitates accurate tracking of execution logs for the masking process |
| Single sensitive field scan limit | 2000 characters | Adapts to field length ranges in daily documents |
| Masking rule mapping node | Link to field mapping table documents | Matches preset masking rules in daily documents |
| Audit log retention period | 7 days | Meets basic recording requirements for compliance audits |
| Approval trigger node | Bind to masking verification completion event | Aligns with circulation logic of daily approval records |
Three common mistakes
- Phenomenon: After the workflow runs, the masking results displayed in the interface still contain unhidden sensitive fields. Cause: The
variablesscope is not configured correctly, project-level variables are set to globally visible, and no hiding rules are configured for sensitive output nodes. - Phenomenon: When running workflows across projects, masking configurations from different projects are mixed and used together. Cause:
variablesare not isolated per project, and all projects share the same set of variable configurations, leading to data confusion. - Phenomenon: The variable reference bar of the knowledge base retrieval node shows as empty, or an error is reported during runtime indicating that the variable is undefined. Cause:
nodeIdis not correctly bound to the variable reference node, or the variable scope is not opened to this workflow link.
How to confirm that the configuration is correct
- Manually trigger a single-project workflow, check whether the sensitive field identification node automatically pulls the data dictionary information of the corresponding project, with no manually entered fields omitted.
- View the workflow audit log, confirm that the
nodeIdof the masking execution node has been correctly recorded, and the log retention period meets the preset 7-day requirement. - Simulate cross-project operation, verify that the
variablesconfigurations of different projects do not interfere with each other, with no data crossover. - Submit a masking verification request, confirm that the approval trigger node automatically transfers to the approval link after masking is completed.
The values given 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-10-19.