Workflow Builder was introduced in JMP 17. Use the attached JMP Journal to try Workflow Builder using your licensed version of JMP 17 and JMP Pro 17.
Questions answered by Ernest Pasour @ErnestPasour and Scott Wise @scwise during the live demo:
Q: In JMP 16, the enhanced log does not capture every action, will Workflow Builder have the same limitation?
A: Yes, Workflow builder is built on top of the events from the enhanced log. However, JMP 17 has expanded the number of items that are logged.
Q: Is there any way to slow the process down?
A: If you mean how to slow down the flow of the workflow process, you can add “wait” actions into the workflow builder steps that will let you control how fast steps are run. She shows how in one example. For example, to wait 10 seconds, in the "Step Settings", add a custom code action which will let you enter JSL. Put Wait(10) as the code. For a more advanced fix, you can group all the steps, then put the Wait(10) in the step actions where it will apply to every step. You can play with that depending on exactly what you need. Alternatively, you can step through one step at a time manually. Or add a "continue" dialog after each step.
Q: What happens when you execute something that requires user input?
A: There are ways to add places for user prompts (to close windows, to enter an output or input for an analysis report, etc.) via augmenting the saved scripts and/or using the step setting actions.
Q: Can you just copy the same command and apply to the rest?
A: Not in 17, although we hope to get that in for 18. However, hide tables is on the Step context menu, so you can multi-select to control that setting.
Q: Can you add a specific definition when showing the results instead of the JMP reference as the description?
A: Yes, she just copied and pasted from the documentation. You can add any text you want. You can also use the URL option in the message action. That allows you to point to a web page which could contain text, or even a video.
Q: Can this be extended to show how results can be presented in a report (e.g., PowerPoint)?
A: Exporting to PowerPoint is something that is captured yet by the Action Recorder, which means it won’t be recorded in the Workflow Builder. But you could save the script out into a Script Window for a Workflow Builder up to the PowerPoint step. Then you can paste it or type in the script for the PowerPoint action at the bottom and you will have one executable script to handle everything.
Q: How do you add the Reference Manager to the first step?
A: The reference manager applies to the entire workflow. The prompting will happen if tables appear to be needed and not open. You only need to visit the reference manager if the automatic behavior isn't sufficient.
Resources
