Create Actions

An Action is a zip file that contains the files you want to run. It must include a metadata file that describes the Action. It can also include various other files, such as executables, bat scripts (which run command line operations), PowerShell scripts, Python scripts, and so on. Actions cannot run on their own. To run an Action, you need to create an Automation (or a Collection Extension) that tells the system what action to run and what files to run in it.

TIP: If you want to enhance security by signing an action with both your own private key and a certificate issued by a trusted certificate authority (CA), see Sign Actions with a Certificate and Private Key.

To create an Action, follow these steps:

  1. In SysTrack Configure, select Automations and Collection Extensions from the left side menu.

  2. Select the Action Governance tab (at the top of the page).

  3. Select the Create Action button.

  4. Complete the fields for Name, Description, Version, and Supported OS.

    NOTE: You can design Actions to run on multiple operating systems. However, the best practice is to create different actions for different operating systems, which makes the purpose of each Action more clear.

  5. Select an executable file. Click the plus (+) sign next to Build Files. Then select a file.

  6. For Command Type, select Automation. (This is the default.)

  7. For File Type, select Exec.

  8. In the Async column, select Sync or Async, depending on whether the file should run synchronously or asynchronously with other files when the action is called.

    TIP: Executable and Support files uploaded to an action are scanned for security. The green Status check mark will display when complete.

  9. If the action requires a support file, click the plus (+) next to Build Files. Then select a file.

  10. For File Type, select Support.

  11. Repeat the preceding two steps for as many Support files as you need.

  12. If you need to specify Parameters for the Exec or Support files, do so now. This information will be passed to the action when it runs.

  13. You can provide optional Usage Examples. This is the information that appears in the Action Documentation frame in the Automations tab.

  14. Click Save Action.