Skip to content

Set up Scripting

Requirements

  • License activation: Make sure Scripting is included and activated in your license.
  • User rights: Assign management rights to users who need to create, configure, and run scripts or use script buttons in the UserClient. Implemented scripts run automatically by the predefined triggers. Configured script buttons are available for all users.
  • Authenticity: Verify the origin and integrity of all external scripts and script applications before deployment.
  • Feature activation: Enable Scripting in the AdminClient.
  • Script package: Use the script package to enhance the Scripting functionality. Submit a support ticket to request the script package at myAMDT.

Plan script implementation and execution

  • Execution side: Decide whether the script runs on the server side, client side, or both.
  • Event assignment: Specify which event triggers the script (for example, before or after upload, before compare, or when an editor starts).
  • Multiple scripts: Assign more than one script to the same event if needed. The script that runs depends on the component type ID and the configuration in the initialization file.
  • Automatic or manual execution: Scripts can run automatically based on events or manually through action buttons in the UserClient.

Prepare configuration and execution files

  • Script types: Decide whether to use script files (interpreted at runtime) or compiled script applications (EXE or BAT).
  • Naming: Name script files according to their task, for example, RSLogix5000_OldEditor.script and compiled script applications with reference to the event, for example, ScriptAfterCompare.exe.
  • Parameter files: Store the required parameter and configuration files in the script directories in the AdminClient. Files placed in the automatic client update directory are synchronized to UserClient installations.

Related topics