“LabVIEW VI Scripting helps you programmatically generate, edit, and inspect LabVIEW code. It contains several new VI Server classes, properties, and methods so you can create, move, and wire objects; edit the connector pane; create new VIs on the fly; and more. Use LabVIEW VI Scripting to create tools for increasing development efficiency, enforcing coding guidelines, or helping new users.” (Source)

Scripting property/method nodes on the block diagram can have one of the following colours:

(*) Obsolete nodes cannot be created but exist only for backwards compatibility.

A LabVIEW.ini setting that exposes private properties, methods and events in the IDE

  SuperSecretPrivateSpecialStuff=true

A word of caution: Private functions have no or misleading documentation and are subject to change with every new version of LabVIEW.

See also KB: Accessing the Internal/Private Property Type in LabVIEW

A System VI is a VI with an internal flag that causes LabVIEW to treat it as part of its system infrastructure: It will not show up in error list, hierarchy windows, etc. The flag can be read or changed through the private VI Server property VI: Is System VI (IsSystemVI); LabVIEW also provides a private property for listing all System VIs currently in memory. The precise editor behavior is undocumented, so project VIs should not be marked as System VIs: private properties are unsupported and may change between LabVIEW versions.

Version number of the application. In a stand-alone application or shared library, this property returns the version of the LabVIEW Run-Time Engine.

• How to Programmatically Get or Set Custom Conditional Disable Symbols

Enable “VI Scripting” in LabVIEW's options