1 min lesing
EQS documents
Read-only access to EQS/Extend document management — procedures, guides, flowcharts and the organisational unit tree.
Procedures and guides out of EQS without opening the vendor’s own interface — including the flowcharts, which are recognised as diagrams rather than dumped as prose.
What it is
Section titled “What it is”EQS (Extend) is a third-party document management system used for procedures, guides and process documentation. This integration reads whichever tenant it is pointed at: the category tree, documents and their revisions, rendered files, and the organisational unit tree.
It resolves a document’s current revision and reports whether that revision was ever actually approved — using the approval date and approver rather than the revision’s status label, because status names vary between tenants and cannot be relied on.
Use it for
Section titled “Use it for”- “What is the current procedure for this, and has it been approved?”
- “Show the categories under this part of the organisation.”
- “Give me this document as a PDF.”
- “Which units exist in the organisational tree?”
- “Is there a flowchart for this process?”
| Function | Answers |
|---|---|
| Usage guide | How categories, documents and revisions relate — the assistant reads this first |
| List categories | The category tree, filtered by parent, unit or global scope |
| Get document | A document’s metadata, its current revision, and whether that revision was approved |
| Get document body | A revision’s content — flowcharts are flagged as diagrams rather than returned as text |
| Get document file | The rendered PDF or the revision’s source file |
| List org units | The organisational unit tree |
Data and permissions
Section titled “Data and permissions”- Read-only. Nothing is written back to EQS.
- Optional scoping. The integration can be restricted to specific categories or organisational units at configuration time. Unset by default.
Getting started
Section titled “Getting started”The integration needs API credentials for your EQS tenant. Talk to your Customer Success Manager.
Limitations
Section titled “Limitations”- Approval status is reported from the approval record, not from the revision’s status name — a document can carry a status that reads as current without ever having been approved, and the integration will say so.
- Binary and Office attachments are described, not read. A PDF comes back rendered; a spreadsheet comes back as metadata — its type and size — rather than as inlined content.
- Not every EQS module is available. Messages, competence and users are not part of this integration.
- Read-only means read-only. Revising a procedure still happens in EQS, by whoever owns it.