Create a ZIP file from files or folders.
Important: To use this feature, the user must be authenticated with zero trust authentication, which serves the security of the session. Authentication is required only once when you run a Remote Execution step.
- On the page, select Create new job.
Can't find the page in the left menu? That's probably because the
Devices menu is collapsed. Click the arrow to expand it.
- On the Create job page, choose the platform where you want to run automation steps.
- Add the Compress to ZIP step to the list on the left.
- Type the path of a source file or a folder that you want to compress to a ZIP.
- Type the Destination file path on the remote computer.
- Optionally, select the following:
- Include root folder - when selecting a folder as source, this option adds the root folder to the ZIP file as the topmost folder. When you extract the ZIP, its content is automatically copied to that folder. For example, when you select c:\strategy\panning\tools as source, the compressed ZIP will have a tools folder that will contain your compressed files. Without selecting this option, a tools folder will not be created for your compressed files.
- Overwrite existing file - overwrites the ZIP file every time you run this step
- Click Next.
- From the list of Devices define the devices or a group of devices that will receive the script.
You can organize your devices by selecting a grouping option from the top of the list.
- Click Next.
- Name the job in a way that is easy to remember later on.
Optionally, you can schedule jobs up to one year in advance. To do so, toggle
Schedule this job and set the time and date for the job to run. In the
Date and time field, either type a date or click the calendar icon to choose it from a date picker.
Remember: You can select offline devices for scheduled jobs, but when a job runs, devices must be online; otherwise, the job will fail on that device. Scheduled jobs run on each remote device's local time.
- Click Run.
Note: A preset timeout pertains to both the job and the step.A timeout for every step is set to two hours, meaning that GoTo waits two hours for the script to finish on the remote computer. When the script finishes, GoTo starts the next step and waits another two hours for that step to finish. If a step does not finish on a remote computer in two hours, then it times out and the whole job fails.
