We're Warning You: Control Chart Warnings in JMP® Live 16 (2021-EU-45MP-733)

Aurora Tiffany-Davis, JMP Senior Software Developer, SAS
Josh Markwordt, JMP Senior Software Developer, SAS
Annie Dudley Zangi, JMP Senior Research Statistician Developer, SAS

In this session, we will introduce an exciting feature new in JMP Live 16. You and your colleagues can now get notifications (onscreen and via email) about out-of-control processes.

We will demonstrate control chart warnings, from the perspective of:

A JMP Desktop user
A JMP Live content publisher
A regular JMP Live user

We will point out which aspects of control chart warnings were available before version 16, and which aspects are new.

Join us to learn:

Which JMP control chart warnings platforms are supported.
How to control which posts produce notifications.
How to control who gets notifications.
How to pause notifications while you get a process back under control.
How to review (at a high level) the changes over time for a particular post.

Auto-generated transcript...

Speaker	Transcript
	Thank you for joining us today
	to learn about a new feature in
	JMP Live 16: Control Chart
	Warnings. You may be thinking
	Control Chart Builder has been
	available in JMP Desktop since
	version 10 and Control Chart
	Warnings have been available in
	JMP Desktop since version 10. So
	what's actually new here? What's
	new is in JMP Live version
	16 we now have a way to grab
	your attention if there's a
	control chart post that has
	warnings associated with it. In
	other words, if there's a
	process that might have a
	problem. We do this through the
	use of onscreen indicators as
	well as active notifications
	that can go out to users
	on screen and by email.
	I'd like to now introduce just
	a few of the people who helped
	to develop this feature.
	I am Aurora Tiffany Davis,
	senior software developer on the
	JMP Live team, and during
	today's demonstrations, I'll be
	showing you JMP Live from the
	perspective of a regular user.
	We also have with us today Josh
	Marquordt. Josh is a senior
	software developer on the JMP
	HTML5 team, and during today's
	demonstrations he's going to
	show you the perspective of a
	JMP Live content publisher.
	Finally, we have Annie Dudley
	Zangi. She is a senior research
	developer on the JMP statistics
	team and she's going to be
	demonstrating the control chart
	features within JMP Desktop
	itself. Annie, would you like
	to get us started?
	Thanks Aurora. Yes, so I'm gonna
	be demoing this with showing
	you how this works using a
	simulated data set based on a
	wine grape trial that happened
	in California. So what we have
	here is 31 lots, several
	cultivars and yield, brix
	sugar and pH. So let's start with
	Control Chart Builder.
	First, I'm going to pull in the
	yield (that's in kilograms).
	And then I'll pull
	in the location.
	Has a subgroup variable.
	I don't care about...so much about
	the limits. What I am concerned
	about instead is whether or not
	we have any particular lots that
	are going out of control there.
	Going above the limits or below
	the limits. And I care about how
	each of the cultivars are doing,
	so I'll pull that into the phase
	location, which basically
	subgroups all the all the
	different...or subsets all the
	different cultivars for us. So we
	can see that we have differences
	and kind of unique things going
	on with the different grapes.
	Next I'm going to turn on
	the warnings.
	And to...the easiest way to do that
	is to scroll down under the
	control panel and select
	warnings and then tests.
	We're going to turn on Test 1,
	one point beyond the limits, and
	then Test 5 as well.
	OK, I see no tests have failed.
	That's pretty good.
	And now you might recall we
	were looking at two other
	response variables, so I'm
	going to turn on the Column
	Switcher so we can look at all
	three of them. We can just flip
	through them using the Column
	Switcher.
	So we started with yield. We'll
	take a look at sugar. Alright,
	we can see the Aglianico has
	very low sugar content, whereas
	the other four have a higher
	sugar content. And we can see the
	different pH levels for each of
	the five grape varieties. OK,
	well we've got these 31 lots in.
	I think we're ready to publish
	it. Josh, would you like to show
	us how to send that up?
	Thanks Annie, so I have the same
	report up that Annie just showed
	you and I'm ready to publish to
	JMP Live. The first thing I
	would need to do as a new
	publisher would be to set up a
	connection to JMP Live.
	If I go to file, publish,
	and manage connections.
	You can see that
	I have a couple of connections
	already created, but I'm going
	to add a new one.
	First you need to give
	the connection a name just to help keep
	track of multiple connections.
	The next thing you need is
	the URL of the server you're
	trying to connect to,
	including the port number.
	Finally, at the bottom of the
	dialog you can supply an API key
	which says for scripting access
	only. You only need this if you
	are going to be
	interacting with the server
	using JSL, which we're going to
	do later in this demonstration,
	so I'm going to get my API key
	from JMP Live.
	I'm logged in.
	I go to my avatar in the upper
	right-hand corner and select
	settings to see my user
	settings. At the top there is
	some information about my
	account, including the API
	key. I click generate new
	API key and copy this by
	clicking the copy button.
	to my clipboard, then I can
	return to JMP and simply paste
	it in here and click next.
	Authenticate
	to
	JMP Live. And you will be told that
	your connection was created
	successfully and you can save it
	now. It is now present in my
	list of connections and ready to
	use for publishing. You only
	have to do that the very first
	time you set up the connection.
	The next time you publish, you
	can just use it.
	So now I can go to file, publish
	and publish to JMP Live.
	And select my connection from
	the dropdown at the top.
	Create a new post is selected by
	default. So I click next.
	And this dialogue looks very
	similar to what it did in 15.2,
	except now there's an
	additional checkbox here that
	says enable warnings.
	This is present for every
	warnings-capable report.
	If I hover over it, it says,
	"Selecting enable warnings will
	notify interested parties when
	this post has Control Chart
	warnings." I'll get back to who
	the interested parties are in
	a moment, but first I wanted
	to explain what warnings-
	capable reports are. In JMP
	16 only the Control Chart
	Builder is warnings-capable
	and able to tell JMP
	Live about warnings that are
	present within it. There are
	plans to expand to other
	platforms in the future.
	A Control Chart Builder can be
	combined with other reports in a
	dashboard or tabs report.
	And it can be combined with
	the Column Switcher as we're
	showing in this example.
	Some more complex scenarios
	could cause an otherwise
	warnings-capable report to not
	be able to share warnings and
	this enable warnings checkbox
	would be gone.
	For example, the Column Switcher
	only works with a single Control
	Chart Builder. If you try to
	combine it with multiple control
	charts in a dashboard, that
	would no longer be warnings-
	capable in JMP 16.
	So back to who are the
	interested parties? I, as the
	publisher of the report,
	am an interested party,
	as well as the members of any
	group I publish to, if that
	group is warnings-enabled.
	So I am going to publish this
	report to the Wine Trials Group
	and leave enable warnings
	checked so that JMP will
	tell JMP Live about any
	warnings that are present.
	The report will come up in JMP
	Live. And the contents of the
	report look much like they did
	in 15 and 15.2
	The points have
	tooltips. You're able to brush
	and select and the Column
	Switcher is active, allowing you
	to explore the results in
	multiple columns. Now I'm going
	to hand it over to Aurora so she
	can show you some of the new
	features in JMP Live.
	Yeah, thank you Josh. So Josh
	just published a post to JMP
	Live that is warnings-enabled,
	but that doesn't actually have
	any warnings going on right now,
	so I can show you what that
	looks like from the perspective
	of a regular JMP Live user
	and what it looks like is not a
	whole lot. There really isn't
	anything to draw my attention to
	Josh's post. There isn't any
	special icon showing up on his
	post. I don't have any new
	notifications. If I open the
	post itself, and I opened
	the post details,
	and I scroll down, I will see
	that there's a new section that
	did not exist prior to JMP Live
	version 16. And that's the
	warnings section. This section
	is here because the publisher
	said, by checking that
	enable warnings checkbox in
	JMP desktop at publish time,
	the publisher is saying, I
	think that other JMP Live
	users are going to care whether
	or not there are warnings on my
	post. And so we have a warning
	section here. But right now it
	just tells us a very reassuring
message	there are no warnings
	present. If we scroll down
	further, we can see the
	system comment that JMP
	Live left in the comments
	stream at publish time, and
	again, this just tells
	us a nice reassuring
message	this post has zero
	active control chart
	warnings. I'll pass it back
	to Annie now so that she can
	walk us through the next
	step of the grape trial.
	Thanks, Aurora.
	So as I said before, we're
	getting new data in. We had 31
	locations before. Now we have 32.
	The original study
	was adding some some actual
	restricted irrigation lots so
	that they could find out how the
	five different grapes responded
	with restricted...with more dry
	regions. So if we take a look at
	the control chart with these
	these restricted values,
	we can see that the yield is
	lower in this new...in this new
	lot that was just added. And
	in fact, with the Tempranillo
	grape it is...it is below the
	lower limit. We can take a look
	at the sugar to see how that
	responded and we can see that
	the sugar actually went up for
	our new restricted irrigation
	dry spot.
	The pH wasn't wasn't
	anything abnormal.
	So I think we need to
	update this. Josh, do you
	want to show us how?
	Yes, so new in JMP 16 in JMP
	Live is the ability to update
	just the data of a report.
	This is useful because you don't
	need to rerun the JSL or
	recreate the report in JMP and
	republish. You simply want to
	update the existing report with
	new data. This can be done
	directly from the JMP Live UI
	by selecting details
	and scrolling down to the data
	section where you can view the
	data table that is associated
	with the report. And click manage
	to update it.
	Click on update data
	and select update next to the
	table you want to update.
	And click submit.
	You're returned to the report.
	You will see that it is
	regenerating and the updated
	content shows the warnings that
	Annie mentioned. Now I'm going to
	hand it over to Aurora to
	demonstrate some of the other
	ways that JMP Live lets you
	know you have warnings. Thank
	you, Josh. OK, so Josh has taken
	a post that was warnings-enabled
	and now he's updated the data on
	it so there actually are
	warnings now, so I can show you
	what that looks like from the
	perspective of a regular JMP
	Live user. We can see now that
	his post looks a bit different
	than it did before. It has a new
	red icon on it that draws the
	eye, and when we hover on that
	icon it says there are control
	chart warnings in this post.
	What that's telling me in a
	little bit more detail is, first
	I know that the publisher of
	this post cares about control
	chart warnings because the
	publisher has chosen to turn on
	those tests within JMP desktop.
	Second, I know the publisher
	thinks that other JMP Live
	users might care about control
	chart warnings on this post
	because that publisher has chosen to
	enable that JMP Live feature.
	And third, of course, I know that
	there actually are control chart
	warnings on the post. Now I'll
	see this icon on any post. I
	also see it on a folder if that
	folder has a post inside of it
	that fulfills all these same
	criteria. If I click on this
	icon, I am taken to
	the warnings section of the post
	details, just like I showed you
	last time, only now there's more
	interesting stuff in this
	section. Now it tells me that
	there are control chart warnings
	and which columns those warnings
	are present on (yield and brix
	sugar) and it tells me some
	details about the warnings. But
	if I want more details, I can
	scroll down just a bit and click
	open log. That tells me a lot.
	It tells me for every column
	How many warnings there are;
	what that translate to in terms
	of warning rate; which tests
	the publisher actually
	decided to turn on an JMP
	desktop; and also specifically
	which data points failed
	tests and which tests they
	failed. I can also copy this
	to my clipboard.
	If I scroll down further to the
	comments stream, I can see a new
	system comment. It says the
	posters regenerated because the
	post content was updated, and
	when the post content was
	updated, there are now control
	chart warnings on the following
	columns. So you can see here
	that these comments stream can
	serve as kind of a high-level
	history of what's been going on
	with the post. Right now I'll
	leave Josh a quick comment
	saying it looks like reduced
	irrigation had a
	big impact. Now
	the icon that I saw on the card,
	that would be seen by any JMP
	Live user, and any JMP Live user,
	if they open the post details,
	would see these system comments
	and they would see this warning
	section. But not just any JMP
	Live user would get a new
	notification actively pushed to
	them, but I do have that
	notification. I can see it up
	here in my notifications tray.
	And I also have one sitting in
	my email inbox right now, and
	it's very detailed. The email
	contains all of the information
	that is present when we saw open
	log just a moment ago. Now, why
	did I get this notification? I
	got it because I'm a member of
	the group that published...that
	the post was published to. And
	furthermore, the administrator
	of that group has turned on this
	JMP Live warnings feature.
	They've enabled warnings for the
	group itself, and by doing that,
	the group admin was telling JMP
Live	I think the members of my
	group are really going to care
	about control chart warnings, so
	much so that you should actively
	push notification out to them if
	we get any new control chart
	warnings on the posts in this
	group. In other words, my
	group admin agrees with the
	publisher. They both want to
	draw my attention to these
	potential problems.
	Now I'll turn it back to Annie
	so she can walk us through the
	next part of the grape trial.
	Thanks, Aurora.
	OK, so we we last looked at the
	adding of the restricted
	irrigation lot and now we have a
	couple new lots come in.
	Nothing, nothing special about
	those. Let's take a look at the
	graph. Um, what do we see here?
	Well, we see the restricted
	irrigation, but nothing special
	with those. Let's see if
	anything happened with the
	sugar. No, we see the two new
	points at the end after the
	restricted irrigation, but
	nothing special there and not a
	whole lot new. But we do still
	need to update the graph and
	update it on the web. So Josh, do
	you want to show us how we can
	update it this time?
	So I have already
	demonstrated how you could
	update the data through the
	JMP Live UI, but you can
	also do this through JSL.
	First, I'm going to declare a
	couple of variables, including
	the report ID. The report ID can
	just be found at the end of the
	URL after the last slash; it's a
	series of letters and numbers
	that identifies the report to
	replace. There are ways to
	retrieve the report ID through
	JSL, which I will show in a
	moment, but for now we're just
	going to save that.
	We're also going to update our
	updated data set that Annie just
	showed you so that we can
	provide it to JMP Live. So if I
	run these, it opens the data table.
	The next thing we need to
	do is to create a
	connection to JMP Live.
	This will use this the
	named connection that we...
	that I created at the
	beginning of the demo,
	Discovery Demo server, here.
	I use the new JMP Live command,
	which will create a JMP Live
	connection object. I provide
	an existing connection and
	it can prompt if needed, but
	I've already authenticated.
	So if I run this,
	I get a new connection. As I had
	mentioned at the beginning, you
	can use this connection to
	search for reports, as well as
	get a particular report object
	by ID. I'm going to use our
	variable that I pasted in
	to get the report we've
	been working on.
	That report can be...
	you can get a scriptable
	report from that result
	object to get a live report
	that you can examine for a
	number of pieces of information.
	Here I grabbed a live report
	and got the ID.
	I got the title,
	description and the URL.
	And you can see in the log that
	the ID I retrieved
	matches the one that I
	pasted in
	to the report.
	I also got the title.
	The description is blank 'cause
	we didn't provide one when we
	originally published. And I also
	got the URL, the full URL, that I
	could use to either open the
	report through the script or for
	some other purpose, such as
	creating a larger report
	that links to it.
	In preparation of the next step,
	I'm just going to get the
	current date and time, which I'm
	going to use to decorate the
	title a bit, prove that we've
	updated it through JSL.
	But the key command here is
	the update data command, which
	lets us update just the data
	of the report, just like I did
	through the JMP Live UI. It
	takes the ID as well, which
	here I'm going to retrieve
	from the live report object.
	And then takes the data command
	which you provide the new
	data table that you are
	uploading, as well as the name of
	the the current data table that
	you want to replace.
	That
	update result object can also
	be queried to retrieve a
	number of pieces of
	information, like if it was
	successful, the status you got
	back, any error messages which
	could be useful in a more
	automated setting to provide
	details as to why publish of
	the new data failed. So I'm
	going to run this.
	And it said that it was
	successful. And if I bring up
	my report, you get this popup
	that says an updated version
	of this report is available.
	Now I can choose to dismiss it
	and continue looking at the
	current context I have, but I'm
	going to say to reload.
	And we see the new data points
	here without having to refresh
	the entire page.
	We go back to
	JMP.
	The last thing I wanna do is
	show that other pieces of the
	report can also be manipulated
	through JSL. Here I'm simply
	going to give it a new title. I
	don't like the one that was
	provided by default, so I had
	declared this variable with
	a new title, and I'm going
	to append to that, the date
	and time to help
	distinguish when this
	update was done.
	I'm going to use the set Title
	Command to send that to the live
	report and then close my data
	table to wrap up.
	Run these and
	bring up the report. In
	a moment you'll see the
	title refresh both here
	and in the details.
	Here it is with the date
	and time.
	Now I'm gonna hand it back over
	to Aurora so she can show you
	more of what happened in JMP
	Live with this update. Thank
	you, Josh. So I can see Josh has
	updated title on his post. And so
	he has updated a post that was
	warnings-enabled and had
	warnings. He's updated with new
	data, and the new data, and just
	like the previous data, has
	control chart warnings. So I can
	show you what this kind of
	persistent warning situation
	looks like to a regular JMP
	Live user. So I can see here that
	the icon that draws the eye and
	says there are control chart warnings in the post
	that's still present in a
	persistent warning scenario. If
	I open the post,
	and I open the post details, I
	can see the warning section. Only
	now, it tells me I have warnings
on three columns	yield brix
	sugar and pH. If I scroll down
	to the comments stream, I can
	see that same notification about
	the warnings here in the
	comments stream. And I also, I'd
	like to point out, have a new
	active notification that is pushed
	out to me. I have a new one here
	and that's telling me that the
	new data, just like the old
	data, does have warnings
	associated with it. Now I'll
	turn it back to Annie and she
	can take us through the next
	step of the grape trial.
	Thanks, Aurora.
	So last we talked, we were
	looking at Lot #34. 33 and 34
	were added, so we've got
	one new lot come in. That's lot
	#35. Let's see how it looks.
	Oh my goodness, the yield is way
	out of...out of control. This is...
	this is just unbelievable. This
	is...this is just remarkable. How's
	the sugar look? Well, the sugar
	looks about normal, like we would
	expect. The pH is also
	about where we would expect.
	This is something that's
	clearly going to involve some
	investigation, but we still need
	to report this. Josh, would you
	like to update the web?
	So,
	we've demonstrated that you
	can update just the data of
	the report, which is useful
	when you want to keep the
	report contents the same
	and just update the data.
	But there's also the ability to
	replace the report which existed
	before, and it's still useful if
	you want to update the contents
	of the report itself.
	I realize in addition to
	updating the data, I don't
	really want to have this moving
	range chart at the bottom. It
	doesn't really make sense in
	this context, so I'm going to
	right click and say remove
	dispersion chart and get rid of
	that. So now the report is ready
	to be replaced.
	I got to file publish, publish
	to JMP Live, and it looks like
	it did before except instead of
	selecting create a new post, I'm
	going to decide to replace an
	existing post and click next.
	New in JMP 16,
	we've updated this search
	window.
	My report is right at the top of
	the list, but you also have the
	ability to search by by keyword.
	And...
	and restrict the number of
	reports if you've published a
	lot, or this was a while ago and
	you have difficulty finding it.
	I'm going to pick the report I
	want to replace and click next.
	On this screen I get a
	summary of the existing
	picture and title. I'm going
	to update the title,
	just to draw attention to
	the fact that I replaced it,
	and give the description.
	This time I know something might
	be wrong with the yield. So
	while the report does have
	warnings, this time I'm going to
	decide to uncheck the enable
	warnings checkbox. Information
	about the warnings will still be
	sent to JMP Live
	and be available at a later
	time, but I don't want everyone
	to get notified about the
	warnings just yet.
	Click publish.
	And again, I'm told that my
	report has been updated and I
	can reload it.
	And the new information for the
	title and description appear in
	the details. I'll hand it
	back to Aurora so she can
	show you what else has
	happened in JMP Live.
	Thank you, Josh. So just to
	summarize, again, Josh has
	taken a post that has control
	chart warnings in it, but this
	time when he republished it,
	he decided not to enable the
	JMP Live warnings feature.
	I'm gonna show you what that
	looks like to a regular JMP
	Live user because the content
	publisher has control over
	whether their control chart
	warnings are exposed on JMP
	Live in a way that's going to
	draw the attention of other
	users. And Josh decided that
	that attention really wouldn't
	be productive right now. So what
	does it look like to me? It
	really doesn't look like a whole
	lot. There is no icon on the
	card to draw my eye to it. I
	don't have a new notification.
	If I open the post and I open
	post details, and I scroll down,
	that warning section that I've
	showed you several times before,
	it's not even present, because Josh has
	said I don't think other JMP Live
	users really need to know
	about the state of the warnings
	on this post right now.
	Furthermore, if I scroll down to
	the comments stream, you know, I
	can go back all the way to the
	beginning and I can see when it
	was published, it did not have
	control chart warnings and then
	it was updated and it did. It
	was updated again and it still
	did. The most recent comment
	that I see says Josh Marquordt
	has republished the post, and
	it doesn't tell me anything
	one way or the other about
	control chart warnings. And
	again, that's because the
	publisher has control over
	whether these things are
	exposed to other JMP Live
	users.
	While I'm here, I'll leave a
	quick comment because I see in
	the description that Josh wants
	us to look at the yield.
	And it looks very, very
	off to me, so I'm going to say,
	could this be
	A data entry error?
	Oops, that was my scroll mistake
	and I'll submit that and then
	I'll turn it back over to Annie
	so that they can do some
	troubleshooting on this process.
	Thanks, Aurora. So we went back
	and we talked with the data
	entry people and it turns out
	they were entering in pounds
	instead of kilograms. As you
	notice right here, we're in
	kilograms. So we updated the
	data, did a little division
	on it, and now the yield
	looks like more like what we
	would expect. The sugar and
	the pH have been unaffected.
	Josh, would you like to
	show how to republish?
	Yes, so we've shown several ways
	to update the data. I'm going to
	go back to the first way I
	replaced it by updating it to
	the the JMP Live UI. I'll click
	on details. And scroll down
	to the data section
	again, click manage.
	Update data.
	And when I click update I'm
	going to select the fixed
	data that Annie just
	presented and submit.
	Go back to the report, see
	it regenerate.
	And
	like we noted the
	yield is back to looking
	normal. I'm going to leave
	a comment for Aurora to let
	her know that we fixed the
	...the units.
	Then hand it back to her to show
	you what has changed in JMP
	Live. Aurora... Thank you, Josh.
	So I can see his post here. I
	can open it and right away
	looking at the report itself I
	can see that things look a lot
	better on the yield. So I'm
	curious about what that what
	that was. I'm going to scroll
	down here and actually I can get
	here because I notice I have a
	new notification. What's that
	about? I click on it and I see
	that Josh has replied to my
	comment; that will take me
	directly to the post also. And
	if I scroll down to those
	comments and I look at that
	reply, I can see, OK the units
	were in pounds instead of
	kilograms. It's been fixed now.
	Fantastic. So it looks like the
	grape trial is back on track
	and we're making good progress.
	Um, I'd like to take a step back
	now and talk about the different
	kinds of JMP Live users that
	there are and how they interact
	with control chart warnings.
	We've talked a lot during these
	demonstrations about the power
	that Josh had as the content
	publisher. The content publisher
	has control over which tests are
	turned on or not in JMP
	desktop. And the publisher
	also has control over whether
	or not to enable this JMP
	Live feature on the post.
	But before when I got a
	notification about control chart
	warnings, I mentioned that I got
	it because the post is published
	to a particular group. So I'd
	like to show you a little bit
	more about those groups. If I go
	to the groups page, I can see
	the Wine Trials Group that this
	post has been published to, and
	I can see that it is warnings-
	enabled. If I hover over that, it
	says control chart warning
	notifications will be sent to
	members of this group. Let's
	open that group up.
	You can see here as well that
	it's enabled and because I
	actually happen to be the
	administrator of this group, I
	can change that. If you come over
	here to the overflow menu,
	which is these three dots,
	click that, and I have the
	option to disable warnings and
	stop sending these
	notifications out to my group
	members.
	I can also change it bac. If I
	change it from disabled to
	enabled, then I get a prompt and
	it says send notifications now.
	JMP Live is telling me,
	OK, you've got a group;
	it's got some posts in it;
	because you didn't care
	previously about control chart
	warnings in this post there
	could be posts in this group
	already that have warnings and
	none of your members know
	about it. So now that you do
	care about control chart
	warnings in this group, would
	you like me to go ahead and
	send out notifications to all
	of the members of the group
	about any control warnings
	that already exist on the
	posts in here? I'll say no for
	now because we already know
	about this particular problem.
	But what if I'm not a content
	publisher and I'm not a group
	administrator? I'm just a
	regular JMP Live user and I'm
	getting notifications about
	other people's processes. As with
	any other kind of notification,
	I can opt out. And I would do
	that by going up here and
	clicking on my notification bell
	icon, clicking on the settings
	icon. And if I scroll down, I'll
	see that there is a new type of
	notification called control
	chart warnings. I can toggle
	this on or off to say whether or
	not I want these notifications
	at all. And if I do,
	I can let JMP Live know with
	what frequency I want to receive
	emails about these
	notifications. I think that
	Josh also has some closing
	thoughts for us, so I'll
	turn it over to him, Josh.
	Thanks, Aurora.
	So we demonstrated the new control
	chart warnings in JMP Live 16,
	how it lets you notify
	interested parties about tests
	that generate warnings in
	Control Chart Builder.
	We've shown some new features in
	the JMP Live UI that draw
	attention to the warnings and
	give you details about what
	occurred. And settings to control
	the notifications and warnings
	from the perspective of both the
	publisher and group admins.
	We've also shown that there's
	several ways to update
	reports and get data into
	JMP Live 16. You can publish
	a report from the JMP
	desktop.
	You can update just the data,
	which is a new feature in JMP
	Live 16, through both the JMP
	Live UI, as well as updating just
	the data through JSL.
	And you can also still
	republish a report
	from the JMP desktop
	to change its contents.
	I only briefly touched on the
	JSL capabilities in JMP Live
	16 so if you're interested in
	more details or on how to take
	this process and automate it,
	please see Brian Corcoran's
	talk on the JMP community at
The Morning Update	Creating
	An Automated Daily Report to
	Viewers Using Internet-Based
	Data. It takes a control chart
	warnings example and shows how
	you might make this a daily
	process that publishes
	automatically.
	Please see our talk on the JMP
	community and leave us feedback.
	Finally, we wanted to say thank
	you. We are just a few members
	of a much larger...several teams
	that have worked on this
	feature. On the JMP
	desktop in Statistics, Annie
	Dudley Zangi and Tonya Mauldin
	worked on Control Chart Builder.
	The JMP Live team led by Eric
	Hill contributed to both this
	feature and many of the other
	features that we got to
	indirectly show while giving
	this demo. The JMP
	Interactive HTML team led by
	John Powell created the content
	of the reports of control chart
	folder in JMP Live.
	Our UX and design work is done
	by Stephanie Mencia and our project
	manager is Daniel Valente.
	Thank you.
	Thank you everyone. Thank you.

Presenter

Aurora Tiffany-Davis

We're Warning You: Control Chart Warnings in JMP® Live 16 (2021-EU-45MP-733)

Presenter

Files