We'd like the ability to evaluate expressions before the pipeline runs. For example, we have a Service that has two manifests (one OCI Helm and one HTTP Helm). We want the user to be able to select the connector they want to use and have the primary manifest pre-populate using some kind of expression but, because expressions aren't evaluated yet, this causes unintended behavior. Primarily, this causes issues with other inputs for these manifests since we are also allowing the end user to select the Chart Version. In this scenario, the version inputs for both the manifests will show up which can cause confusion for our users. We have a workaround currently but, would like to have a way to dynamically evaluate the expressions before the user runs the pipeline and use those expression values to make decisions on whether or not certain other fields should be shown or pre-populated.