Using the Path Builder
The path builder creates the actual definition for your best practice. By creating a path, using the Workbench Path Language, that evaluates to a true or false, we can analyze any SSIS package to see if the rule created applies. In the following example, we will create a rule that checks to make sure the user did not enter the value "Description" for a connection's Description property. Let's take a look:
For more information on the Workbench Path Language syntax used within the Path Builder, please click here.
1. From the User-Defined Best Practice creator page, click on the "Path Builder" button next to path evaluator.
This will open the view below. Note the text box at the top that contains "./ ". That is the field for your path. You have a list of Operators, Selectors, and other miscellaneous commands to choose from. If at any point you want to start over, click the Reset button.
2. Select a technology type on the left hand side.
This will bring you to a screen for that technology type, there you must pick and specify your solutions/items
3. Use the Object Type Filters, and then click on the type you want to create a rule on in the Object Browser. This populates the middle field with that object's properties and path.
Here, we have selected the package itself from the Object Type Filters and a Flat File Connection from the Object Browser. This populates the middle pane with the path and properties of the connection manager.
4. Click on the property you want to check to generate the path.
Here, click on the property "Description."
5. Drag the path into the Path Text Box and remove the name
6. Click Preview to ensure your rule validates against the current package.
Note that your rule should validate true for it to throw a violation of the best practice. Therefore, for our purposes, our rule looks for connections where the description has a value of "Description".
7. Click the back arrow to review your Object Type Filter and Rule Path in the User-Defined Best Practice creator.