Import a Local File

ISPW allows users to import local files into ISPW and create new tasks from them. This makes it easy to define applications to ISPW or bring in a new release of vendor software. Import of local files can be done for any application levels that have been configured to reside in a ISPW warehouse. See to the field definitions for additional definitions.

To import a local file

  1. From the Repository Explorer view, right-click the Application node and select Import>Local File. The Import Local File dialog box appears.
  2. Do one of the following:
    • From the From directory list, select the directory from which to import local files to the ISPW warehouse.
    • Click Browse and navigate to the local directory from which to import local folders and/or files to the ISPW warehouse. Any of the following actions can help in this process:
      • Expand the nodes in the left pane and select the checkboxes for the folders that contain the desired files. Then, in the right pane, select the check boxes for the desired local files.
      • Click Filter Types to filter the current selection to display only files of a specific type.
      • Click Select All to select all resources in the directory, then deselect any that are not desired.
      • Click Deselect All to deselect all resources in the directory, then select only the desired resources.

  3. In the Into warehouse path field, enter the ISPW warehouse path, which is the import destination. This path is pre-filled based on the path selected in the Repository Explorer.

    Important

    The ISPW directory structure within the application is based on appending any folders selected in the left pane to the path specified in the Into warehouse path along with any selected files. After import, any new folders automatically reside at the Prod level while the files reside at the Test level to then be processed through the life cycle by the user.

  4. Select or clear the Create top-level folder check box. Select it to create, in the repository, the top-level folder shown in the hierarchy (folder) pane when importing. Clear it to not create the top-level folder shown in the hierarchy pane.
  5. From the Assignment list, select the name of the assignment that contains or will contain this task. If ISPW can determine the assignment based on the context, this field will be prepopulated; even so, the assignment can be changed, if desired. Optionally, do any of the following to select the assignment:
    • Click Filter, if desired, to open the Assignments Filter dialog box and enter criteria to filter the Assignment list.
    • Click New, if desired, to add a new assignment.
  6. Optionally, change the application by selecting from the Application list of the applications in the stream. You can also change the subapplication by selecting from the SubAppl list. The Stream, Application, and SubAppl fields are initially prepopulated based on the context of the ISPW view the action was invoked from. The stream cannot be changed.
  7. From the Path list, select the path. The path is enabled after the type is specified.
  8. If the task should be associated with a release, from the Release list, select from the list the release with which the task should be associated. If ISPW can determine the release based on the context, this field will be prepopulated; even so, the release can be changed, if desired.
    • Select None to not relate assignments to a release.
    • Select Default to associate the task with the default release for the currently selected assignment. If the assignment has a default release, this is the default selection.
    • Optionally, to filter the list of releases, click Filter to open the Releases Filter dialog box and enter criteria to filter the Release list.

    • Optionally, to add a new release, click New.

      Important

      An assignment can have tasks in different releases.

  9. Optionally, select the Import new or changed files only check box to only add and check out new components (that don't already exist in the repository) or changed components (that are different from what exists in the repository). Clear the check box to add and check out all components regardless of whether the components are new or changed in the repository.
  10. Click Finish. The selected files are imported, creating a checked out task at the specified path, assignment, and release for each file.


Important

  • A message appears if an attempt is made to import to a certain level any files with extensions that are not configured to use a warehouse dataset. Before these files can be imported, the ISPW Administrator must add the extensions to the ISPW warehouse dataset. Otherwise the files must be deselected from the import request.
  • If any files have extensions that do not have a corresponding ISPW component type, the Unmatched File Extensions dialog box appears to allow the user to select the component type to use for that extension. For each entry in the File Extension column, select from the Component Type list the component type to be used for files with that extension. Optionally, use the Default component type list to select one component type to use for all of the listed file extensions. After either a default component type is selected or a component type is selected for each entry in the File Extension column, click OK to complete the import.
  • If multiple versions of a warehouse component exist in the ISPW repository, the  Component Versions dialog box appears so the user can select the version to import.
  • If an error occurs during the import process, the Import Local File Results dialog box appears showing the results of the import and the reasons for any failures.
  • Once the component is imported, it resides locally at the TEST level for the owner who did the import. It is not in the ISPW repository until the component is promoted.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*