Documents Tools
The documents a project writes from its own record: the business requirements document the client signs and the software requirements specification the team builds against, each asked for with a kind, a title, a file format (PDF or HTML) and a scope (the record as it stands, with or without drafts, or a frozen baseline), rendered in the background as the person who asked and under their permissions, numbered within its kind (`BRD #2`), with an opening page Heimdall drafts when nobody wrote it, moved to final by the project manager's approval, which supersedes the kind's earlier final copy, and shared with the client's guests from that moment.
The documents a project writes from its own record: the business requirements document the client signs and the software requirements specification the team builds against, each asked for with a kind, a title, a file format (PDF or HTML) and a scope (the record as it stands, with or without drafts, or a frozen baseline), rendered in the background as the person who asked and under their permissions, numbered within its kind (BRD #2), with an opening page Heimdall drafts when nobody wrote it, moved to final by the project manager's approval, which supersedes the kind's earlier final copy, and shared with the client's guests from that moment. These tools read a project's documents and which copy is final (list_documents), read one with its scope, its opening page and, on request, the rendered words, so an agent reads a BRD or an SRS without downloading it (get_document), and ask for a new one as the token's holder (generate_document), after which a person reviews the draft, edits the page and puts it to the project manager through submit_for_review; editing a draft, rendering it again, superseding a final copy and deleting a document stay in the application and the REST API.
Tools
How is this guide?
Last updated on