Workflow Builder or the "baby steps" into ScriptingWorkflow Builder is a new utility to record your JMP data preparation and analysis workflows. It is a way to capture, build, manage, and share your data steps and work without resorting to scripting. Learn how to easily reproduce and recycle an analysis that will save you and your organization precious time.
Re: Workflow Builder or the "baby steps" into ScriptingJmp 18: more options to structure a Workflow:
Re: Workflow Builder or the "baby steps" into ScriptingConcerning the issue with the Table References, which was discussed in the Q&A
... there seems to be a workaround with Jmp18:
example-of-a-workflow-with-a-for-each-loop.shtml
1) use a workflow step #1 to open/create new tables:
Subset by, open(), Multi File Import ...
2) Select step #1 as Source - Workflow Step in the FOR EACH settings
3) and add as many workflow steps as you want to the For Each branch:
-> for all steps in the For Each loop, Jmp will use the the tables which were opened in step #1.
[independent of the table name which was used when recording the steps!]
Re: Workflow Builder or the "baby steps" into ScriptingThere are 2 modes:
With "Workflow Step", Jmp will automatically replace all table references within the For loop with the data table from the input step, NOTHING to define/change in the individual steps *)
Iteration Variable (item #1, item #2 ,...) and Index Variable (1, 2 , ...) can be used - but are mainly needed for mode that uses the JSL Variable.
*) just try it with:
Print(// Iteration Index , Iteration Variable,
Data Table("xyz") << get name(); );Jmp detects the Data Table ("xyz") in the code and replaces it automatically with the data table from the input step.
Almost too extreme - like indicated in the previous:
even a reference to a summary table will be replaced with a reference to the input table - if the specific step is inside the For Each loop.
