Create Actions

  1. Go to Configure > Tools > Automations and Collection Extensions > Action Governance > Actions and click Create Action.
  1. Use the appropriate fields to specify a Name, Version, and Description. The Name can be no longer than 60 characters.
  2. Select the Supported OS: Windows, Mac, or Linux.
  3. Click the + next to Build Files, to browse and select the files to be included in the Action. You can only select one file at a time and the maximum file size is 150MB.
    1. As you upload each file, it will go through a scanning process and show one of the following statuses: scanning, success, quarantined, fail
    2. Scanning is in process.
    3. Success the file has passed the scan and successfully uploaded.
    4. If a file's status is quarantined it has not passed scanning. The file should be checked locally for potential viruses.
    5. If a file's status is fail there was an error during the scan or upload. Resubmit the file.
  4. For each file, you can see the Command Type which is either automation or collection extension, File Type which is either exec or support, and if it is an exec whether it runs Sync or Async.
    1. If you need to remove a file, click the trash (bin) icon.
  5. <Optional> You can specify Parameters to be used with the action and Usage Examples to guide the use of those parameters.
    • For every possible parameter option in the Action, you can create a parameter entry. This helps in the creation of Automations by allowing users to see the type of data they will need to provide to run the Action.
    • Parameters have the following fields:
      • Name: The name of the parameter. This can be a descriptive name because it is just guidance for what to pass into the Action.
      • Units: An optional attribute that can describe the units for the value being passed in for this parameter.
      • Required?: If a parameter is required to run the Action, the value of this field should be Required.
      • Description: The description of the parameter containing the purpose of this parameter and any other necessary information about using it
    • You can use Usage Examples to provide guidance on how to construct an Automation for this Action and on the purpose of the Automation.
    • Usage Examples contain the following fields:
      • Action File: The name of file that will be executed when the Automation is run.
      • Arguments: Parameters or command line options that should be provided to the Action by an Automation.
      • Description: The purpose of this example and any other necessary information about how it should be used.
  6. Click Save Action.

  7. Actions are automatically virus scanned. This process can take up to five minutes. If the scan finds issues, you will not be able to save the Action. Contact Lakeside if you are unable to get an Action uploaded. The scanner can be strict to protect our customers.

  8. After the scan is completed, the action will be visible in the Pending Approval tab.

Video: Create an Action