System documents require regeneration when any underlying data or configuration items referenced by the document are changed, even if the visible content of the document itself does not appear different. This is because Ketryx takes a conservative approach to ensure all release documents are always up-to-date with the most current project data. For example, if a configuration item is updated—even if the updated field is not displayed in the document—the system will still mark the document as needing regeneration. This behavior ensures compliance and traceability by always reflecting the latest project state in your documentation.

For template-based release documents, any change to active records in the relevant project and version will cause the document to be considered out of date and require regeneration. If this enforcement is too strict, it can be adjusted in the project settings by deactivating the "Require up-to-date release documents" control Document Templating.

These distinct approaches to prompting document regeneration is by design - the more conservative approach to regeneration of templated docs is driven by the fact that a templated doc can potentially have any items relevant to it. Systems docs are more controlled and therefore can have more refined regeneration rules.