The Production Manager (Control panel > Process & production) view is the interface where you administrate and manage your packages. You can create “virtual folders” to organize packages in a tree view.
To create a package, simply select a virtual folder and click “New software”. A default package is created named “New Package”. You can only have one package with the same name. If you name a package with a name already in use, the version number will be increased by one (e.g. from version 1 to version 2). You can edit values and properties associated with the package in the package overview tab once you've selected a package from the tree-grid view.
Navigate to the FILES tab. Either add files and folders by clicking “Add” in the menu or drag/drop files and folders from your Windows File Explorer. Drop them on the folder content area in the files grid.
Each file will have a set of properties, and the “attributes” property is used to add an action to the file.
- None. No action
- Execute Once. If it is the first time the package is downloaded on the computer, the file is executed.
- Always execute. Execute the file every time the API checks/updates the package
- TopLevelFile. When files are downloaded at your target machine, the client API will return the full path of the top level file(s). This allows TestStand execution entry point "WATS MES – Test UUTs" (or your custom environment) to automatically execute the file.
The package's folder/file structure is created on the client when the package is downloaded (using the WATS API).
A package may be identified by its unique name or by tags. You may assign any number of tags to a package. These tags can later be used for getting/downloading packages (ex. Download all packages tagged with a PartNumber = 123456).
When a package is selected, the right window will display the tags tab. Add new tags with the "Add tag" in the tag toolbar.
Install Package on root.
When a package is downloaded to the client (using the WATS API), the Package name is used to create the “first” folder below the root folder. E.g: C:\Documents and Settings\All Users\Documents\SoftwareDistribution\New Package. This ensures that no folders will be in conflict and accidentally overwritten.
When toggled, the API will create the subfolders one level below the package to the root folder at the client (don’t use the package name as the first folder).