Q-Pulse
Ask neil about selected quality records and bring the evidence into your investigation.
Put this connection to work Set up Q-Pulse in the docs
Summarise this Q-Pulse nonconformance and the actions included in the shared response. What evidence is still missing?
I’ll use the referenced capture, cite its record identity and distinguish supplied actions from information we still need.
Selected Q-Pulse JSON response
Quality follow-up brief
- Supplied findings and action status
- References and capture time
- Missing evidence and owner questions
What’s connected.
Connect selected Q-Pulse (Ideagen Quality Management) data through your approved JSON API or gateway. Share captured responses with chosen Seal groups, then use @ references to ask neil about findings, actions and missing evidence. Available fields depend on your installation’s API contract.
Connection setup and permissions
Q-Pulse, now Ideagen Quality Management, uses installation-specific interfaces. This configurable binding reads JSON objects or arrays from exact GET paths beneath an approved API prefix. Seal does not supply a Q-Pulse gateway or perform SOAP, Windows login or session-token exchange.
The entire selected JSON response is copied, including nested fields. The source endpoint must restrict its content to the intended records and columns. Credentials stay in the connection; the chosen Seal audience controls access to the copy.
Set up Q-Pulse
- Obtain the API guide for your Ideagen Quality Management Professional installation and agree read-only JSON endpoints. SOAP, Windows authentication and private installations need an approved compatible gateway supplied by your IT team.
- In Settings → Integrations → Q-Pulse, enter the approved HTTPS prefix, relative test path and supported authentication header. Test the connection and explicitly select the responses to share.
- Enable content copying, choose the Seal audience and sync. Reference a shared resource with @ in neil and ask a question about the supplied evidence.
Related blueprints
Start with the quality evidence you have.
These examples require the selected endpoint to include the relevant fields. Ask neil to identify missing evidence instead of assuming it has the whole quality system.
- Review a nonconformance
- Summarise the selected event and its supplied actions. Flag unresolved questions for the owner.
- Compare audit findings
- Compare the findings included in the referenced audit responses, with supporting record identities.
- Prepare a CAPA discussion
- Explain supplied status and due dates, and draft follow-up questions for your review.
Connection questions.
Does it connect to every Q-Pulse installation?
No. Your installation must expose the supported JSON GET and header-authentication contract, directly or through an approved gateway. Obtain the API guide and test a representative resource first.
Can neil read every quality record?
Only the selected responses shared with your Seal audience. Chat uses saved captures and their sync time. It does not query the whole source live or infer that a page contains every record.
Can we map results into Seal fields?
Yes. The existing integration read bindings expose selected data to ordinary Seal Scripts when Operational source entity sync is enabled. Your Script owns mapping, scheduling and downstream review.
Before it goes live.
Access and write-back
Reading records and writing back are separate decisions. Define which records are in scope, whose permissions apply and which changes require approval.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.