Need help figuring out how to modify an OOB pattern properly that is part of a shared library

[Dukeh1]

Hello,

Thank you for taking a moment to help me. My goal is to modify just the windows server and windows desktop patterns. 

So far I have not found a way to insert my step to map bios version (pattern already pulls data in step 3.3) to a field without having to share to libraries when saving. This at the very least I can tell also adds the pattern step to my windows desktop pattern. Which will not work as the desktop pattern then is referencing the windows server target table, as the step is a running clone of what I just created on the win server pattern. 

I am trying to figure out best practice in doing this simple task, as I am using the operation 'transform table' to source the win bios info and push to the relevant CI table. 

Am I forced to add my own sub pattern or something that is not already a shared library to isolate this change to one CI pattern? 

Any assistance would be greatly appreciated. 

[doug_schulze · Accepted solution]

Since they are shared and its an OOB (library) pattern probably best to just add your updates to an extension section that fits per OS.

[Dukeh1]

At this point I was figuring that might be necessary, but in the effort to not repeat myself, was hoping it was not this big of a nightmare to leverage the Windows - Hardware Information probe steps, since OOB the data is already collected itself. 

For now ill start working on an extension attempt that collects and maps the bios data. Thanks Doug

[Dukeh1]

Final follow up for anyone in this same situation. 

Creating an extension step set is definitely the way to go. The variables pulled from the OOB discovery portion were still all present for me to leverage and setting the value(s) I wanted independently was straight forward.

Thanks again for taking the time Doug.