What inspired this wish list request?
I was just at a JMP event and was reviewing JMP Live's active use of a connected system to assign OOC points from specific control charts to specific users. This has been a large part of my job in the past.
What is the improvement you would like to see?
I would like to see this data exportable in either JMP tables or ideally piped directly to a database.
It would be maybe two files or tables: one to list each point's status and summary notes, and another to store user conversation per point.
Why is this idea important?
This is important because one of the first things we do when solving a problem is to search company history systems for previous examples of the issue. Have we seen this before? How did we solve it? Why are we seeing it again? This information can stay with one person, but in today's mobile workforce it is so imperative for a company to hold onto its data in a searchable way.
I have used scripts in the past to store information like this; which points are under investigation, which points have actions on them, and which points can be excluded or hidden.
Hi @leonwilde,
The functionality you are looking for is already available in the current version of JMP Live. You can either download a list of all warnings and their metadata or the full history of a warning, which includes comments made by users.
It is currently downloaded as a CSV file which you can further process and upload to your database.
I want the data automatically piped to a database. Why would I enter in all my data into a location where I'll need to manually download each one? It is far easier to enter the data into my current repository database directly without the extra step, as nice as it would be to have the comments directly connected to the report.
I want connection, not another task 
