Investigate a production exception. Use the permitted Tulip records and show me the supporting evidence.
Once the records are shared with me, I’ll compare selected table rows with the quality event and batch records under review.
Selected rows from one Tulip table: record ID, sequence number, timestamps and visible supported columns.
Investigate a production exception
- Findings linked to source records
- Missing evidence and unresolved questions
- Follow-up work for your team
1What’s connected.
Use selected rows from a Tulip table in production and quality reviews. Select the records to share in Seal, then reference them with @ in documents, comments and Neil.
Connection setup and permissions
Seal’s Tulip connector reads one table with an API token scoped to tables:read. It does not write to Tulip.
The connection is restricted to one workspace and table. It captures record ID, sequence number, creation and update timestamps, and visible supported columns with their names and types. Decimals keep their original precision.
Hidden columns, images and files, user, machine and station details, and linked-table contents are not included. Table rows do not include app completions, signatures or audit trails, so a status column is not evidence that an app step was completed or signed.
Set up Tulip
- In the intended Tulip workspace, create an API token with tables:read scope only.
- Copy the table URL from your instance’s API documentation. Open Settings → Integrations → Tulip, enter the URL, API key and secret, then choose Test and connect.
- Search record IDs, select rows and review the preview, then choose Seal groups and enable sharing.
2Connect in Seal.
Sign in to Seal and open Settings → Integrations. An organisation admin can review the connection and complete the guided setup.
3What Neil can do with Tulip once connected
Once the connection is set up and the records are shared:
- Investigate a production exception
- Compare selected table rows with the quality event and batch records under review.
- Prepare a shift handover
- Summarise the exceptions and open items recorded in the selected rows for the next team.
- Check recorded values
- Compare quantities in the selected rows with the batch’s expected values. A status column is not an app completion or signature.
4Connection questions
Can table rows stand in for an electronic batch record?
No. Table snapshots exclude app completions, signatures and audit trails. Do not use them as a signed batch-release package.
5Before it goes live.
Access
The organisation library reads only; it makes no changes in Tulip. Define which records are shared and which Seal groups can read them.
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.