Skip to content

Prepare script applications and initialization files

Name script applications after the event or interface that calls them so they are easier to identify and maintain. For example: ScriptBeforeUpload.exe, ScriptAfterUpload.exe, ScriptButton1.bat.

Name script files clearly based on their purpose. For example: Extract_Notify.script. Naming conventions help identify scripts in Script management, while initialization and configuration files define which script is used for each event.

Info

If both an .exe file and a .bat file with the same base name exist in the script directory, Octoplant runs the .exe file.

Use initialization files

Use an initialization (.ini) file to map script applications to component types or use cases.

  • Name the .ini file after the script application, for example: ScriptBeforeEdit.exe → ScriptBeforeEdit.ini.
  • Use a [General] section with keys such as:
    • default for the default script application
    • {ComponentTypeID} for type-specific script application.

Example

[General]
default = ScriptBeforeEdit.exe
DC14F6773F0B4705886A3457646C92B6 = RSLogix5000_OldEditor.exe

Related topics