When?
Your data (Excel, databases, etc.) has been updated and you want to apply your analyses to this new data?
Do you regularly have new data sets (Excel, CSV, Text, etc.) and want to apply your analyses?
Do you need to share validated analysis structures with your teams?
Do you need to view different JMP platforms together?
Do you need to customize JMP?
Here are some of the situations in which the dashboard is most useful
What?
A dashboard can be a single analysis or a set of analyses. It can be incorporated into an add-in so that it can be accessed from JMP and shared within teams (*). It can be connected to the database, and therefore contain accesses to it, or it can be applied to a newly supplied dataset
How?
Step 1: Load the data
This step can be very important. We recommend that you load the data at this stage using the File menu. The particularities of this loading will be explained in step 4.
In this example, I will use the attached excel file
Step 2: Define the analyses
The analyses that will populate your dashboard must have been defined on the basis of a single file.
In this case, I created a Distribution, a Control Chart and also a graphic with the Graph Builder
Step 3: Combine analysis
Once the analyses have been defined, you'll need to combine them together. To do this, use the File -> New-> dashboard tool.
You'll need to choose the template closest to the desired final rendering.
In my case, as I have a control chart, I like to use this one, which has an elongated graph at the bottom.
Then simply drag and drop the analyses into the position you feel is most appropriate.
Step 4: Data Management
How will the dashboard be used? Do you want it to launch access to the data (which may have changed since the last time it was run)? Should it apply to the current table? Should it allow the user to choose which file to open or not?
By default, the dashboard will execute the contents of the Source script attached to the data table before the dashboard is launched. This is why opening the file properly gives you the source script in question. If this source file evolves over time, you are ok with this step. If you want the user to choose their file because your data structure regularly generates a new file, or if you want the dashboard to apply to the table already opened by the user, then you'll need to change a property
The data table property allows you to choose between embedded script (execution of the source script), the current table or the choice made by the user with the prompt option
Step 5: Execute the dashboard
Simply select the run the dashboard option to have the dashboard run (with potentially regenerated data access).
Step 6: Save & Create an add-in
As with any script, there are various ways of saving the dashboard, but my favourite is the add-in, which has the following advantages:
- enriches the JMP environment with my day-to-day business analyses
- easy to share with other users
This first tab is used to define the file name and version.
It is also necessary to specify the name of the application that will appear in the JMP menus on the second tab (Menu Item name zone). This step is important because it allows you to properly define the tool.
Once the dashboard has been saved, the JMP add-in menu will be enhanced with this new tool.
This add-in can also be shared with other JMP users. Simply give them the file in question and the end user will install it by double-clicking on it.
(*) : If team members are not JMP users, then a JMP Live type report could be proposed.
