It sounds, on the surface, as though you are trying to combine two separate parts.
Can you take a step back and explain what your requirement is, rather than how you're attempting to do it in BSA? That way someone can tell you the best way to accomplish it in BSA.
For example: I'm using BSA version X, we have a config file used for X, this config file can exist in different directories, we need to do compliance on this config file looking for X, etc.
Ok. This is what I am trying to achieve.
I have a number of web servers each one running a number of web services. Each web service has a web.config file. At the moment, if anyone wants to make a change to the web.config file they log on to the server, take a backup of the file, then make their changes by editing the file in Notepad.
I want to change this process, so anyone who edits a config file does it through BladeLogic (we're using Server Automation v8.3).
Each server contains a large number of web.config files, all in different locations. I want to create a simple process to add, remove or edit content in any config file. Something that allows me to easily see what has been changed and when, and to roll it back if necessary.
in order to rollback, you need to have a snapshot, or you need to use a blpackage to deploy the change(s). otherwise there is no way to rollback after a change.
https://docs.bmc.com/docs/display/bsa83/How+to+pass+local+parameter+values+to+a+compliance+remediation+package has some examples of setting up the PSIs and parts.
so you have your two properties. you create the local parameter instances for each possible value of your path, and then setup discovery to look for /??BLAH??/??FOO?? or whatever the path will be.
from there you can snapshot all of those components and then allow access for manual edits, or you can allow the users to deploy via the blpackage/bldeploy.
i'd also ask why do the users need to manually edit these files?
Thanks Bill, that link provided me with the information I needed. I wasn't creating the instance of my local property correctly on the component template. Once I resolve this I was able to make a component and create a package for any changes that were needed