Skip to main content
Version: 7.9

Script Builders

Inductive University

Script Builders

Watch the video

When creating an Event Handler on a component, you can use one of the handy Script Builders instead of writing your own script. In the Component Scripting window, the Script Builders are accessible as tabs along the top. Each tab represents a different kind of action that users can associate with an event. The last tab, Script Editor, lets you write your own event handler. You can also use it to view the script that was generated by the Script Builder, which is a good way to get started learning how to write your own event handlers. The examples in this section use a Button component. If you would like to follow along, drag a Button component on to a window and follow the steps to create the event handler for any of the Script Builders below.

Actions get overwritten when choosing another Script Builder

Only one Script Builder can be used at a time. If you previously picked another action using a different Script Builder, it will get overwritten by enabling another Script Builder. If you need to do more than one action at a time, use the Script Editor to combine scripts, or create your own script.

The Navigation Script Builder has various functions that deal with opening and closing windows.

Open / Swap

Opening is a very straight-forward operation, it simply opens the specified window at the same size it was in the Designer. Simply click on the Open / Swap button, and select a Window from the dropdown list that you want to open. There are options to center that window within the Client, and to close the window that the event was fired from. The opened window can also be opened as an additional instance, meaning there can be multiple copies of the same window. This is useful when opening dynamic popups, so that a couple of popups can be opened, each with different values.

Swapping is the practice of opening another window in the same size, location, and state as the current window, and closing the current window. This gives the appearance of one window simply swapping into another, seamlessly. The Navigation Builder uses the swapWindow version of swapping, but most "by hand" script authors will use the swapTo version. This last version relies on the fact that the windows being swapped are both maximized windows. See the typical navigation strategy section for more information.

You can also pass parameters to the opened or swapped-to window. The names of these parameters must match names of custom properties on the root container of the target window. The values can either be literals or values of other properties from the source window. Passing in properties from the source window use two special characters: '$' and '**'. The '$**' character represents the source component while the '\' character represents the parent. You can use these to construct a path to the property on the window. You can also use the property selector () to the right. To pass parameters in a navigation window, follow the steps below.

  1. Check the Pass Parameters box, and click the green plus button to add a row.
  2. Highlight the empty cell in the Value column of the parameter table, and press the Insert Property button. Select the property you want and press OK.
  3. Choose a custom property from the "Parameter Name" dropdown list. This will be filled with custom properties on the root container of the selected window. You can also type a name in directly.
  4. Press OK on the Component Scripting window to commit the change. For more information on this script, click the link below the image.

Refer to the parameterized windows section for more information.

The image below is the actual Navigation script that was generated by the Script Editor. If you compare the settings in the Navigation tab with the documented code in the Script Editor, you'll notice the Compressor popup window will be opened and centered in the window, and the value of the "compNum" parameter passed.

Forward / Back

The Forward / Back actions give you a simple way of implementing browser-style forward/back buttons in your client. Note, that you must be swapping between windows for this to work, because these functions rely on calls to system.nav.swapTo in order to keep track of what the sequence of recent windows has been.

Closing Windows

The Closing windows action allow for an easy way to have an event handler close the window that it is a part of, or any other window.

Set Tag Value Script Builder

The Set Tag Value Script Builder responds to an event by setting the value of a Tag. You can set the Tag to either a literal value directly typed in, or you can use the Insert Property () button to have the event handler use the value of another property from the same window. Use the steps below to create a Set Tag Value.

  1. Under the Set Tag Value tab, click the Set Tag Value radio button.
  2. Click the Set this Tag button and choose a Tag from the Tag browser list to write to (i.e., WriteableInteger5).
  3. In the To this Value field, enter a number (i.e., 100) or click the property selector icon Alt text to search the window for a property.
  4. Press OK on the Component Scripting window to commit the change. For more information on this script, click the link below the image.

The Set Tag Value script shown below was generated by the Script Editor. Compare the settings in the Set Tag Value tab with the documented code in the Script Editor and you'll see the Tag is set to "WriteableInteger5" and the Tag value is set to "100."

SQL Update Script Builder

The SQL Update Script Builder helps you build an update query using a database browsing interface. Choose a database and area in your target database, and the update query will be built for you. By setting columns as key columns, you can have the filter correctly filter to the right row. You may use either literal values or property values by using the Insert Property () button next to the Update Value text box. You can try this out using one of your existing databases.

  1. Under the SQL Update tab, click the Update Query radio button.
  2. Select a database and choose a table in your database (i.e., equipment_listing). Choose a value in the table on the right (Conveyor Line), and the Script Builder will filter to the correct row in the table ( i.e., 25489). Notice, an update query was immediately created for you below.
  3. To change a value in the database, enter a new value in the Update Value field (i.e., "New Conveyor Line"), and it will replace the previous value (i.e., Conveyor Line) when you execute the action.
  4. Press OK on the Component Scripting window to commit the change. For more information on this script, click the link below the image.

This will normally be used with a dynamic Update Value, and you can change what value(s) are your keys using the add/remove key icon.

The image below shows the SQL Update script that was generated by the Script Editor. If you compare the settings in the SQL Update tab with the documented code in the Script Editor, you'll see your database, table, and column name, including the row id of the searched value. You'll also see the new update value (i.e., New Conveyor Line) that will replace the existing value (i.e., Conveyor Line) when the action is executed. It will replace the name "Conveyor Line" with "New Conveyor Line."

Set Property Script Builder

The Set Property Script Builder will respond to an event by altering a property in the window. You must choose the property to alter, and the value that you wish to assign to it. The new value can be a literal value or the value of any other property on the window by using the Insert Property () button.


The property references here use the same two special characters ('$' and '\') as passing parameters in the navigation section.

  1. Drag a Label components to your window to set the property to.
  2. Open the scripting window on your button component.
  3. In the Set Property tab on your Button, click the Set Component Property radio button.
  4. On the Set this property: field, click on the Insert Property () button to find your new label component, and then select a property (i.e. the Text property) and click OK.
  5. Type something into the To this value: field (i.e., Hello There!), or select another property on the window.
  6. Press OK on the Component Scripting window to commit the change.

This Set Property script was generated by the Script Editor. Compare the settings in the Set Property tab with the documented code in the Script Editor and you'll see the value string "Hello There!" will be written to the Label component when the action executes.

Script Editor Builder

The Script Editor allows you to add more complexity to existing scripts, combine scripts, and even write your own custom scripts. For example, if you need to perform two or more actions at once, (i.e., set a Tag and navigate to another window), you can update the script by combining the two actions in the Script Editor. The Script Editor even gives you the flexibility to create your own code for any action you want to perform on an event handler.

As seen elsewhere on this page, the other builders ultimately generate a script that can be modified from the from the Script Editor Builder.

Advanced Settings

  • Scoping Dropdown - Allows you to specify the scoping of the script. The scoping of event handlers in older versions of Ignition work differently that modern versions. This settings was added as a way to provide backwards compatibility when upgrading. All new scripts should ideally leave the scope set to Standard Scoping, as there is no reason for new scripts to use the Legacy Scoping option.
  • Invoke Later - Provides an opportunity to allow the script to run after other events have finished processing. Most scripts will leave this setting disabled, however if can be useful in some scenarios:

Action Qualifiers

All of the Script Builders allow you to put Security and/or Confirmation qualifiers onto an event handler. These Action Qualifiers are optional.

Security Qualifier

The Security Qualifier lets you restrict the event handler from running if the current user does not have one of the required roles highlighted in the Security qualifier dialog box. The roles listed will be all of the roles within the project's default user source. To setup the required roles for an event handler, select one or use CTRL+click to select multiple roles. Once the roles are selected, they will be highlighted. To deselect roles, use CRTL+click again.

Confirmation Qualifier

The Confirmation Qualifier prompts the user with a popup Yes/No dialogue box confirming you want to perform the action. The action will only be executed if the user chooses Yes. There is a default message, but you can delete it and enter your own message. Check the Require Confirmation box to enable the Confirmation qualifier.