This documentation applies to FastGPT v4.17.0.
What this category of data looks like
Data sources for this category include CMDB databases, cloud resource inventories, auto-discovery tools, and procurement ledgers. Update frequency is daily or weekly. Documents generated on a regular schedule include configuration item lists, service component relationship topologies, change records, and asset inventory sheets. Data fields include configuration item unique identifiers, asset categories, affiliated business lines, dependency relationships, last update times, and additional fields. Some topology data includes node connection weights. All data must adhere to asset account-physical consistency verification rules.
What Constraints Do These Characteristics Impose on Sharing and Embedding?
This category of data contains sensitive asset dependency relationships and change records. As such, access scope must be restricted during sharing and embedding. Data updates occur daily or weekly. Embedded Q&A must sync the latest configuration item information, so external systems must be configured with a regular update mechanism. Configuration item lists and topology data have a large number of fields. External systems must restrict the number of returned fields and entries during embedding to avoid page overload. Internal ticket Q&A must be linked to operations and maintenance personnel permissions. Third-party identity verification docking capabilities provided in the commercial edition must be used to bind user identity identifiers, preventing unauthorized access to sensitive CMDB data. Additionally, historical conversation records are supported by localId for the same device and browser. Retention is not guaranteed across devices or after clearing browser cache. Obtaining historical conversations must be linked to the corresponding session identifier to ensure traceability to specific CMDB data query scenarios.
How to Configure Settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
Sharing entry shareId | Copy the full share link generated by the system; do not manually replace the identifier | Identify the sharing entry; business records and data permissions for configuration management and CMDB maintenance must still be handled by external systems |
| Share link validity period | Test starting point: 7 days; adjust based on actual testing of configuration management and CMDB maintenance collaboration cycles and revocation requirements | Verify availability within the validity period and access behavior after expiration; this value is not an official default or industry statistic |
| QPM | Test starting point: 20 requests per user per minute; adjust based on actual load | Limit access frequency for a single user; must be verified using request logs and actual load |
| Identity verification | When identity permission requirements apply, first verify the commercial edition capabilities and the uid returned by the third-party identity service | Holding a share link does not grant business data permissions; third-party identity and data scope must be verified separately |
| Referenced content display | Select display configurations for reference fragments, full text, and original text based on the sensitivity of configuration management and CMDB maintenance materials | Check displayed content within authorized data ranges; do not use hidden interfaces as a substitute for data permission control |
| Conversation record verification | Test example: Prepare 10 configuration management and CMDB maintenance Q&A samples, check in the same browser and another device respectively | Anonymous records rely on browser local identity; retention is not guaranteed across devices or after clearing cache |
Three Common Mistakes
- Sharing entries for configuration management and CMDB maintenance fail to open. First verify the full system-generated link and its validity period, then check browser request statuses. Do not manually replace
shareId. - The visibility range of configuration management and CMDB maintenance data does not match expectations. Verify third-party identity verification results, workflow request parameters, and external system data permissions separately. The sharing entry identifier itself does not provide business authorization.
- The same configuration management and CMDB maintenance Q&A is not visible on another device. For anonymous scenarios, first verify device, browser, and local identity status. Retention is not guaranteed across devices or after clearing cache; do not judge service anomalies solely based on this phenomenon.
How to Confirm Configurations Are Set Correctly
- Open the embedded page, access it using accounts with different identity identifiers (requires commercial edition third-party identity verification docking) to verify that returned configuration item data matches the permission scope of the corresponding role.
- Generate a login-free share link, delete a conversation record on the embedded page, and check whether the external system log records the corresponding session's localId and operation information.
- Modify a configuration item in CMDB, wait for the update cycle to pass, refresh the embedded page, and verify that the displayed configuration item information has been updated.
- View historical conversation records on the embedded page, access the share link using the same device and browser, and confirm that previous Q&A content can be loaded. Corresponding records cannot be loaded across devices or after clearing browser cache.
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-10-19.