Skip to main content

Integration guideSeal API and Scripts

JMP

Link statistical analyses, graphs and reports to lab records.

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

JMP to SealSeal API and Scripts

Seal reads
Exported analyses, graphs and reports
Writes back
If agreed
Source of truth
Agreed when scoped
Set up
Scoped with your team
Neil › Analysis record
draft

Keep this analysis together with its input records.

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
Exported analyses, graphs and reports
Returns
  • Inputs, analysis outputs and reproducibility context
  • Missing or unmatched information
  • Next steps for your team to review
Illustrative work with JMP: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Link JMP analyses, graphs and reports to the Seal records they describe, through exported files or Seal’s API. Keep the data table, JMP script and software version with each result so the analysis can be reproduced.

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

2Keep a JMP result reproducible from its data table and script.

Route

After an analysis, the platform’s red triangle menu saves a script to the data table, under Save Script > To Data Table. The script is JSL that reproduces the analysis.⁠¹ On Windows, File > Export writes a report as text, JSON, Excel, an image, PDF, HTML, RTF, PowerPoint or Word.⁠²

What each file reproduces

A JMP report file (.jrp) holds the JSL and the data, or a reference to it, needed to rebuild a live report.⁠³ A journal is a copy of the report window and is not connected to the data table. A self-contained project embeds its data tables and scripts in one file.⁠⁴⁵ JMP Version() returns the version that is running; record it with the result.⁠⁶

When it fails

A saved script will not run
A script saved to a journal holds the path to its data table, and does not run if the table cannot be found.⁠⁷ Attach the data table, or a report or project that embeds it, with the result in Seal.
The report no longer matches its table
With Automatic Recalc off, JMP shows a warning icon when the data table changes and the report is out of step with it.⁠⁷ Rerun the script before exporting, so the figures in Seal come from the table as it now stands.
An export carries the data with it
Interactive HTML embeds the data unencrypted, and JMP advises plain HTML for sensitive data.⁠⁸ Export sensitive analyses as PDF or plain HTML.

Check one record

Take one capability analysis filed in Seal and open its data table in the JMP version recorded with it. Running the table’s saved script should redraw the same report. If it does not, the table or the script has changed since the result was filed.

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. 1JMP: create and save scripts in data tables.
  2. 2JMP 19 menu card for Windows.
  3. 3JMP: save reports.
  4. 4JMP: save platform results in journals.
  5. 5JMP: save a project.
  6. 6JMP: utility functions.
  7. 7JMP: Save Script menus in reports.
  8. 8JMP: publish reports as interactive HTML.