SOLVED: Issues with Parameterized Fixlets

[jgstew]

According to the documentation here: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/Creating%20parameterized%20fixlets

You should be able to make parameterized fixlets in this formal way and have them either be entered into the fixlet description field, or if not it will fall back to the normal ‘action parameter query’ method.

I can’t seem to get this to happen.

I also marked a parameter as required, and yet, it would allow the action to be taken without providing it.

---

Related:

• Fixlet actions that can support parameters supplied from both API or Console
• Securely creating fixlets to update OS user passwords
• Paramerterized Fixlets - Interactive scripting in BigFix Console Descriptions?
• Data validation on action parameter query
• Change local admin password help?
• Parameterized Fixlets Multilinetext problem
• Copy of a Parameterized Task fails to show Parameter fields

[jgstew]

Also, the relevance used to get the vrt_utils.js library is not well optimized. This is much better: https://bigfix.me/relevance/details/3003679

unique value of values of mime fields whose (name of it = "vrt_utils.js") of fixlets whose ( task flag of it AND "Parameterized Fixlet Library" = name of it ) of bes sites whose( "BES Support" = name of it )

Here is my improved version implimented: https://github.com/jgstew/bigfix-content/blob/master/ParameterizedFixletsDescription.html

[jgstew]

I now have some examples working:

• https://github.com/jgstew/bigfix-content/blob/master/fixlet/Test%20Password%20Entry%20with%20Validation%20with%20verifying%20match%20-%20parameterized%20fixlet%20-%20Universal.bes.xml
• https://github.com/jgstew/bigfix-content/blob/master/fixlet/Test%20Password%20Entry%20with%20Validation%20without%20verifying%20match%20-%20parameterized%20fixlet%20-%20Universal.bes.xml