Creating a blue-steps File And Adding Your Custom Step.

Once you have created a custom step and installed the classfile in the correct location, the last step is to tell Blue to load your step.

Sam Taggart
6 steps
54 seconds

Scribe for Windows

Notepad.exe

Windows Terminal Host

Pick an app

Windows Explorer

Why is this all necessary? Why can't blue just autodiscover my custom step?\ \ It could, however the order in which steps execute is important. For example if you are resizing things and rearranging the block diagram, you probably want to resize them first and then rearrange them last after they are already at the correct size.\ \ Because of this, you have to not just provide the custom step class, but also tell Blue where it falls in the order of all the steps.

To make everything easier, you can use G-CLI to create a template file.\ \ Running `g-cli blue -- --create template` in Git Bash or Powershell will create an example file for you in the correct location.

Now go find the template file and open it in notepad.

You'll see it is JSON. There are 3 separate arrays One for each type of step. For this guide we created a VIStep, so we need to add our custom step to the list of VI Steps.\ The best place to do that is typically right before arranging the FP and BD.

Insert your step right before arrange FP (or wherever makes sense) being careful to make sure it exactly matches your class name and click save as.

Save the file in the same directory (\~/.blue) but without the .template extension ie name it blue-steps.json

In Git Bash or powershell run `g-cli blue -- --list` to view the list of steps. Your new custom step should show up in the list.\ \ At this point Blue is ready to load and run your step. Use Blue however you normally would (Tools Menu, QD shortcut, or CLI).