The process of creating and editing a workflow definition file should always be simple and intuitive. That’s why, when we planned the new release of the Workflow Editor (also known as PTFs UI66737 and UI66738), we made Usability the key focus, and we looked closely at the feedback from our users.  

In the latest release of the Workflow Editor, we added the following enhancements:

• New raw text editor within the Workflow Editor
• Ability to create an input properties file at any time during an editing session
• An Expand function to allow users to create more visual space for entering step instructions and template contents.

Let’s take a closer look at these enhancements.

Raw text editor

The addition of a simple text editor (or raw text editor) to the Workflow Editor introduces a new world of possibilities when you edit a workflow definition file. With the simple click of a check box labelled “Edit raw text of the workflow definition,” you can have the Workflow Editor open the XML of the specified workflow definition file in a simple text editor. The text editor provides editing access to the specified file, but without the usual tabbed interface and multi-paned layout of the full function Workflow Editor.

Why would we add a text editor to a sophisticated tool like the Workflow Editor? The main reason is to enable you to correct syntax errors that might otherwise prevent a file from opening in the full function Workflow Editor. As you probably know, if a workflow definition file contains syntax errors, it cannot be opened in the Workflow Editor. By adding a text editor option, we give you the ability to fix those errors first before continuing your work in the Workflow Editor primary interface (the tabbed areas). 

When you open an invalid workflow definition file in the text editor, you will see a message that identifies the error and its line number. As you use the text editor to correct errors, you can click the new Validate button periodically to see whether the contents of the file comply with the workflows XML schema. When you’re done fixing errors, you can open the workflow definition file in the full function Workflow Editor to begin making use of its many functions.  

Create an input properties file whenever you want to

As a workflow author, you can supplement a workflow definition file with an input properties file. This is an optional file that supplies default values for the input variables that are defined in the workflow definition file. By including an input properties file with your workflow, you can save users from having to manually enter data (and possibly errors) when they perform the workflow.

The problem is, sometimes you don’t know that you need an input properties file until after you’ve started developing the workflow.  Previously, it was not possible for you to create an input properties file “on the fly.” If you opened an existing workflow definition file without specifying an input properties file at the start of an editing session, the relevant tab remained grayed out.  

In the latest release of the Workflow Editor, you can create an input properties file whenever you want to---that input properties tab is never grayed out. Whether you’re opening an existing workflow, or creating one from scratch, you can create an input properties file without leaving your editing session. 

More room for your prose

Users have told us that they would like to have more space in the Workflow Editor UI for typing step instructions and creating lots of JCL for template steps. We listened. 

In the latest release of the Workflow Editor, we added the ability to expand the text boxes in places where you might want a little more “real estate” for your writing. Users who are writing a lot of JCL in a file template or an inline step can click the new Expand button to expand the file contents text box to the full size of the Workflow Editor. This same button also makes an appearance in the Instructions tab to finally give you all the space you need to be creative!

Questions and comments

 If you have any questions or comments, please reach out to kberkos@us.ibm.com. Any feedback is always greatly appreciated.