NX Open Programmer's Guide > Executing NX Open Automation > Execution Overview
Execution Overview
Overview of the execution modes and methods available for NX Open applications.
Execution Modes
NX Open applications run in three modes: Interactive, Batch, and Remote. See "Execution Modes" for details.
Execution Methods
NX has many customization access points, each needing different information to execute NX Open applications. The table below lists execution methods, whether they support interactive/batch mode, the required NX tool, and whether they can run a Journal and/or a compiled/linked application.
| Method | Execution Mode | Required Tool | Journal Applications | Compiled/Linked Application |
|---|---|---|---|---|
| Journal Manager | Interactive | Gateway | Yes | No |
| Interactive NX File tab→Execute→NX Open | Interactive | Gateway | No | Yes |
| New Menu Item (.men file) | Interactive | Menuscript | Yes | Yes |
| Existing Menu Item (.men file) | Interactive | Menuscript | No | Yes |
| Toolbar Button (.tbr file and interactive) | Interactive | Gateway | Yes | Yes |
| User Tools Dialog (.utd file) | Interactive | Gateway | No | Yes |
| Dialog from a Menu or Toolbar (.dlg file from UI Styler) | Interactive | UI Styler & Menuscript | No | Yes |
| Dialog from a Menu or Toolbar (.dlx file from Block Styler) | Interactive | Block Styler & Menuscript | No | Yes |
| Automatically at NX Startup | Interactive | Gateway | No | Yes |
| Automatically as an NX Application | Interactive | Gateway | No | Yes |
| User Exits | Interactive or Batch | Gateway | Python journals only | Yes |
| Command Line | Batch | Gateway | No | Yes |
| Remote Procedure Call | Interactive or Batch | Gateway & (.NET or Java) | No | Yes |
| Wizard defined by Process Studio (UI Styler and Journal Play steps) | Interactive | Process Studio | Yes | Yes |
| From ufmenu (option 4) | Batch | Gateway | No | Yes |
| From GRIP | Interactive or Batch | GRIP | No | Yes |
Tool Requirements Summary
| Tool | How Purchased | Purpose |
|---|---|---|
| Gateway | Available with any NX seat | Provides the foundation for all NX capabilities |
| Menuscript | Available with any NX seat | Language for defining NX menu and toolbar buttons/commands |
| User Interface Styler (UI Styler) | Add-on module | Interactive tool for defining platform-independent NX dialogs |
| Block Styler | Add-on module | Interactive tool for defining platform-independent NX dialog boxes conforming to new NX UI guidelines |
| Process Studio | Add-on module | Interactive tool for defining workflow processes |
Note: If a compiled/linked application is executed by someone without an NX Open author license, the executable must be signed (see Signing Process). Signing is not required for Journals.
How NX Finds Application Files
Many execution methods require NX to automatically load application files — see "Application Directory Structure".
Related Topics
- Execution Modes
- Environment Variables
- Application Directory Structure
- How to Execute the Open API
- Unload Options
Source: https://docs.sw.siemens.com/en-US/doc/209349590/PL20220512394070742.nxopen_prog_guide/genid_execution_overview_295_2782 · retrieved Tue Jul 07 2026 00:00:00 GMT+0000 (Coordinated Universal Time)