Skip to main content

Saving to the KB

Generated requirements can be saved back to knowledge bases. Users can save individual items, selected items, or all generated items to a destination KB. A workspace can also be configured to save items automatically when they are created in the provider.

Over time, the project knowledge base can contain both the original context and the artifacts produced from it, strengthening the material used by AI in future flows.

When to use​

  • Use saving to keep approved requirements as part of the project knowledge.
  • Use it when future generations should learn from already produced backlog items.
  • Use it when the team wants the KB to reflect both source documents and generated artifacts.
  • Use automatic saving when the workspace should store items created in the provider.

Before you start​

  • Review and refine the generated requirements.
  • Confirm the destination knowledge base.
  • Decide whether to save individual items, selected items, or all generated items.
  • Confirm whether the workspace should save items automatically when publishing to the provider.

Step by step: save requirements to a KB​

  1. Open the generated requirements in the workspace.
  2. Select the items that should be saved.
  3. Choose the destination knowledge base.
  4. Save the selected items.
  5. Confirm that the generated requirements were added to the project knowledge.
  6. Enable automatic saving in the workspace when this behavior should happen during provider creation.

Expected result​

The project knowledge base should include the generated requirements selected by the user or saved automatically by the workspace configuration.

See also​