With TPM it is possible to import SPBs with the TCM integration, Software Package Editor or manually from the Web UI. I wanted to add another.
What happens if you have a bunch of SPBs that you want to import and you do not want to use the integration? Use the SPE or Web UI? That would take forever!
So I thought I would whip up a quick automation package to do just that. Click here to download the automation package.
The package is made up of 3 workflows
Function: Retrieves a list of all SPBs based on the FileRepository rootPath and the RelSearchPath
if you enter "/" (no quotes) this will search the rootPath of the file repository and all sub-directories for spb files
if you enter "/ActivePerl" (no quotes) this will search the rootPath of the file repository and all sub-directories under ActivePerl for spb files
Function: Retrieves various package attributes used to define the Software Module to TPM.
Funtion: Using the variables passed in from GBS_GetSpbVariables.wkf, creates a XML file in the same directory as the SPB and then uses the built-in workflow called DcmXmlImport to import the XML file.
It is also possible to just run GBS_GetSpbVariables.wkf if there is only one SPB to define. Just pass the required fields into the workflow execution and only that SPB will be defined
With this template, it is very easy to make some changes that would suit your environment. Any comments or feedback is appriciated.