GET

Get Component Metadata from Runtime

Get Component Metadata from Runtime and write it to the Out-Folder. OPtionally you can specify a template to render information about all components.

bc COMP GET /c 54222e4e-e9c1-490b-... -t compList.csv

COMP GET Arguments

The command uses a resolved list of components and recurses over parent(s) and children to:

1. store all metadata in the <OutDir>\MetaData folder

2. store human-readable and re-usbale Component information like SQL statements, Scripts, profiles in <OutDir>\Componentsfolder

3. Optionally, specify a template to render the list of all components.

Visual Studio Code shows Components rendered using /t compList.CSV

Find orphaned components

comList.CSV reports the number of parents and children of each component. Components with 0 parents could be orphaned. For Processes it can be ok to have zero parents, a mapping with zero parents is simply not referenced: orphaned and subject for deletion.

Component Folder Structure

It is vital that you maintain a good folder structure. The COMP GET command tells you where all child and parent components are located.

If you look carefully at the image above, you will see that my process references a script in 99 - ParkingLot folder. This was definitely not my intention.

Components unleashed

If you want to see your raw script, Json profiles or SQL statements, the Components folder is right for you.

The RAW Groovy script as a file in the file-system.

Metadata as XML files

If you want to know where you have used a document property, you may want to search all your Metadata XML files.