drekbour so sorry for the late response! I see the choice parameter as a parameter with name and value the exact same as String or Text Parameters... I may have a string parameter with name TEST_NAME and the value will be different in every single child job inheriting the template... In fact, I may just want the default value in the template to have a blank value...The choice parameter should be treated the exact same way.. i.e. Parameter Name and the choices are the values which could be different in every single child job but with the same parameter name. The "retain local job parameter values" setting in the template should do just that and allow me to have my own choices in the child jobs...
Imagine a scenario where I have a template to automate the ordering of food from various Takeaways:
Template Name: OrderFood-Template
Parameters: Choice Parameter: Name: MENU
Choice Values: blank
Inheriting child jobs:
McDonalds: Choice Parameter: Name: MENU
Choice Values: McDonalds menu choices
Burger King: Choice Parameter: Name: MENU
Choice Values: Burger King menu choices
KFC: Choice Parameter: Name: MENU
Choice Values: KFC menu choices
The above is just another example scenario... My scenario is that we have a generic deployment job with an ENVIRONMENT choice parameter... the choice parameter has different choices based on the type of deployment..