PowerShell is available for Windows servers by default.
- Consider the shebang in the first line of the job that indicates the PowerShell version in use:
  - the string following string indicates use of powershell.exe from version 5.1:
    - @@setlocal enabledelayedexpansion & @@findstr/v "
    ^@@f
    - ^@@[fs].*&" "%~f0" | powershell.exe -
    &goto:eof
    - NonInteractive -Command - & exit !errorlevel!/b&
  - the following string indicates use of powershellpwsh.exe from version 5.1.the string 6 or 7:
    - @@setlocal enabledelayedexpansion & @@findstr/v "
    ^@@f
    - ^@@[fs].*&" "%~f0" |
    pwsh
    - powershell.exe -NonInteractive -Command -
    &goto:eof indicates use of pwsh.exe from version 6 or 7.
    - & exit !errorlevel!/b&
PowerShell can be installed for Unix environments such as Linux and MacOS.
- Consider modifying the shebang in the first line of the job like this:
  - the string #!/usr/bin/env pwsh can be used assuming that pwsh is the binary of the PowerShell interpreter.

Adding a Schedule

If the workflow runs fine you can automate execution by adding a schedule, see JS7 - Schedules.

Assign the newly created workflow to your schedule.
The list of workflow variables will be displayed similarly to adding an ad hoc order.

Image Added

Using the Run-time button brings up the popup window to specify start time rules:

Adding a schedule requires to assign a working day calendar, see JS7 - Calendars and Schedules.
For the start time add a period with a single start at midnight of your time zone.
- The workflow's Cycle Instruction will rule the point in time during the day when the order will start on the given days.
Optionally add a Restriction to limit execution of the workflow to certain days, for example Mon-Fri.

Image Added

Backup

...