About the exported spreadsheet
Figure 1. Example exported Excel file
| 1 | The spreadsheet contains a separate worksheet tab for each selected template. The Template Vendor and Title combine to make the worksheet tab name. You can rename and move the worksheet tabs as required.
The top six rows of each worksheet contain data required by the bulk deployment process to define the purpose of each column.
Do not edit these rows in the spreadsheet. To change their content, go back and edit the template The order of the worksheet tabs is important. The bulk deployment job works from left to right through each worksheet, adding all template items before creating links and relations. If an individual template requires something else to already exist in the running station, and a template tab installs that something, make sure the required entity is in a worksheet to the left of the worksheet that requires its existence. |
| 2 | The left-most columns provide information needed to generate a template instance. Metadata and header rows indicate the column positions to configure each template instance. Each of these column headers includes a comment describing the entry for this column. A template instance is defined by filling in a row in the worksheet tab. Additional rows define multiple instances of a template. Values for each column can be required or optional. |
| 3 | Additional template information is included as formula values. |
| 4 | Comments (indicated by a red triangle in the upper right corner of the cell) provide additional information for specific header
cells. Hover the mouse pointer over the cell to show the comments on that cell. If the template has a Template Info value, it is included as a comment on the template description value cell (B1). If the Excel file is encrypted, a Privacy Note label is inserted in cell (A2), with a notice in cell (B2) stating that “This file is encrypted to protect passwords or other
private data. Please maintain the encryption and safeguard the contents while editing.”
|
| 5 | The rest of the header columns define inputs, outputs, relations, configuration properties, and (optional) string tags. |
| 6, 7, 8 | As of
Slot Path Scope. You can define for each template instance a custom value for the Slot Path Scope to be used during the bulk deployment process.
|