Share

Applies to 2023.0 Update and later

 
 

Managing scripts

Common tasks working with support and repair scripts and support and repair actions within a script

Note: Working with scripts and script actions is largely identical between repair and support generation. As such, this article covers them both, and any differences, where applicable, are noted.

Jump to:

Working with scripts

Task Steps

Create a new script

From scratch

  1. Open repair or support editor on any part on the platform.
  2. In the context view, click New script.

From an existing script

  1. Open repair or support editor on any part on the platform.
  2. Choose More actions > Duplicate current script.

From a file

  1. Open repair or support editor on any part on the platform.
  2. Choose > Load scipt.
  3. Navigate to the script file (filetype SUPPORT or REPAIR, as applicable) and click Open.

Save changes to a script

Changes are not saved automatically. They are temporary until you save the changes.

Saving to registered scripts

  • In the context view, click Save.

Either method saves changes to the currently selected script.

Registered scripts, or user-defined scripts available for selection in the dropdown menu, are stored in %APPDATA%\netfabb\repairscripts and %APPDATA%\netfabb\supportscripts, respectively. They are simple XML-flavored text files.

Exporting to a file

  • Select the support script to export in the dropdown menu.
  • In the context view, choose More actions > Save current script.
  • Choose More actions > Duplicate current script.

Delete a script

  1. Open repair or support editor on any part on the platform.
  2. Choose a script from the drop-down menu.
  3. Click Delete current script.
Note: Default scripts installed with Netfabb cannot be deleted.

Reorder scripts in the selection

  1. Open the list of scripts. For example, from Prepare > Run script in the main menu, choose Run support script or Run repair script.
  2. Click and drag the entries by their grabber icon, . The position change is saved immediately.
  3. Click Cancel to leave the dialog without further action.

Toggle visibility of built-in and custom scripts

  1. Open the list of scripts. For example, from Prepare > Run script in the main menu, choose Run support script or Run repair script.
  2. Click the buttons at the top-right, for support scripts, for repair scripts, and for default and custom scripts, respectively.
  3. Click Cancel to leave the dialog without further action.
Top

Working with actions

Task Steps

Insert a new action

Select an action from the dropdown menu and click Add.

Delete an action

Right-click the action and choose Delete action, or double-click its red Delete symbol, .

Reorder actions

Click the action you want to move and drag it onto the action you want it to come after.

Note: To move an action to the top, drag it onto the topmost action, putting it in second place. Then drag the topmost action onto the second one.

Now available for repair scripts as well.

Duplicate an action

Right-click the action, then select Copy action. (Repair only)

Execute an individual action in a script

Double-click its green checkmark, . Unlike running the entire script, this runs the action without clearing any existing support.

Export an action in its current configuration

Right-click the action, then choose Export action. Specify a name and location for the export file, then click Save.

Note: The filetype suffix for both individual actions and entire support scripts is SUPPORT. (Repair only)

Import an action

Right-click anywhere in the Support scripts view and choose Import action. Then navigate to and select the SUPPORT file and click Open. (Repair only)

Note: You can import SUPPORT files holding individual actions as well as entire scripts. When a SUPPORT file contains an entire script, ALL of its actions are imported.

Disable/enable an action

Right-click an action and choose Disable action or Enable action, respectively.

This function is useful to compare the effect of similar support actions but with a number of distinct differences that would otherwise be a great hassle to switch forth and back. The state of being enabled or disabled is also maintained during export and import.

Rename an action

Expand the action and click on the text field next to Description. Type the new name, then hit Enter or click somewhere else.

While the action itself cannot be renamed, this adds a descriptive text next to its name that remains visible even when you collapse the action's node in the script tree.

Top

Was this information helpful?