Why can't dynamic filtering at the parameter level be applied to Epic-released templates?

Why can't dynamic filtering at the parameter level be applied to Epic-released templates?

• A. Because Epic-released templates cannot be edited
• B. Because they are not compatible
• C. Because dynamic filtering is not allowed
• D. Because they require extra license

Answer: (A)

Dynamic filtering at the parameter level depends on changing how a template’s inputs are defined so the filter logic can react to those inputs. Epic-released templates are provided as read-only, pre-configured artifacts designed to be used as-is to keep consistency and support intact. Because you can’t edit them, you can’t add or modify parameters to introduce that dynamic filtering, so it can’t be applied to those templates. If you need parameter-level dynamic filtering, you’d work from an editable copy or a custom template and implement the filters there. The other options aren’t the real issue here—they point to problems like compatibility or licensing, but the actual blocker is the inability to modify the vendor-supplied template.

Dynamic filtering at the parameter level depends on changing how a template’s inputs are defined so the filter logic can react to those inputs. Epic-released templates are provided as read-only, pre-configured artifacts designed to be used as-is to keep consistency and support intact. Because you can’t edit them, you can’t add or modify parameters to introduce that dynamic filtering, so it can’t be applied to those templates. If you need parameter-level dynamic filtering, you’d work from an editable copy or a custom template and implement the filters there. The other options aren’t the real issue here—they point to problems like compatibility or licensing, but the actual blocker is the inability to modify the vendor-supplied template.