Skip to main content

Integration guideSeal API and Scripts

TIBCO Spotfire

Explore selected scientific and quality records from Seal in Spotfire.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

Seal to TIBCO SpotfireSeal API and Scripts

Seal sends
Selected Seal records
Source of truth
Seal
Set up
Scoped with your team
Neil › Operational report
draft

Bring our quality data into an operational report.

Neil

  • Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
Reads
Selected Seal records
Returns
  • Defined measures and the records behind them
  • Missing or unmatched information
  • Next steps for your team to review
Illustrative work with TIBCO Spotfire: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Make selected scientific and quality records from Seal available to TIBCO Spotfire for visual analysis through a connection set up with Seal’s API. Keep units, sample identities and record versions with the exported data.

Connection setup and permissions

Use Seal’s APIs or scripting engine for a connection tailored to your process. Agree the data mapping, access and direction of transfer before implementation.

Related blueprints

2Load Seal records into a Spotfire analysis.

Route

Spotfire’s OData connector loads data from any OData-compliant web service.⁠¹ Spotfire also connects natively to Snowflake and PostgreSQL, if Seal records reach one of them first.⁠² Data functions run scripts in TERR, open-source R or a Python interpreter.⁠³

Record identity

Keep units, sample identities and record versions with the exported data, so a point on a chart can be traced back to its Seal record.

Updates

Scheduled updates preload analyses with fresh data on Web Player instances. An update can also be started by a process outside Spotfire, through EMS or a web service.⁠⁴ A rule sets whether updated data appears on its own or each user chooses when to load it.⁠⁴

When it fails

A scheduled update keeps failing
Spotfire Server retries a failed scheduled update ten times by default, and the number can be changed from the command line.⁠⁵ The Activity page shows each attempt’s status, with messages and links to the logs.⁠⁶ Fix the cause before the retries run out, then confirm the analysis shows the update time you expect.
Two reviewers see different values
Where the rule lets users choose when to load updated data, one may still be looking at an earlier update.⁠⁴ Show the update time on the analysis, so each reviewer knows which data they are reading.

Check one record

Load one sample set from Seal into a test analysis. Check each sample identity, value and unit against the Seal records. Then revise one result in Seal, run the update and confirm the analysis shows the new value with the record’s new version.

3Start with the job.

Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.

Discuss this connection →

4Before it goes live.

Access and any write-back

Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.

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.

Read the assurance detail →

References

  1. 1Spotfire: OData connector.
  2. 2Spotfire: supported data sources.
  3. 3Spotfire: authoring data functions.
  4. 4Spotfire Server: scheduled updates to analyses.
  5. 5Spotfire Server: retries for failed scheduled updates.
  6. 6Spotfire Server: monitoring scheduled updates.