Support for Knowledge

[DanielMadsenDK]

It would be valuable to extend Fluent with support for the Knowledge Management area, allowing knowledge articles to be defined, version-controlled, and deployed alongside other application artifacts.

Knowledge articles are an important part of application lifecycle management. During development, troubleshooting, and operational support, teams frequently document findings, known issues, implementation decisions, workarounds, and best practices in the knowledge base. Keeping this content close to the source code would make it easier to maintain, review, and manage through the same development workflow used for other application components.

By enabling knowledge articles to be authored in Fluent and synchronized with ServiceNow instances, teams could:

• Store knowledge content in source control.
• Review changes through pull requests and code reviews.
• Promote knowledge articles consistently across environments.
• Keep documentation aligned with application changes.
• Improve knowledge sharing and reduce repeated troubleshooting efforts.

This would help treat knowledge as a first-class citizen in the development process, improving both developer productivity and long-term maintainability.

[zaidongy]

I see knowledge articles as "Data Records" on the instance, fluent is good at building "Config Records". I agree there is value in having fluent APIs to config knowledge bases, setup approval groups, link custom approval retire flows, etc., However I see our users continue to use our MCP server to create and update knowledge articles in ServiceNow.

[u173487]

I would love his.

The ability to write your entire KB structure in code then have your documentation in source control deployable into an instance or marked for deletion.

Bonus points if you could store markdown in a git repo and include it in a fluent defined KB. That way all documentation could be in source control and deployed on schedule.