To enhance the flexibility of expressions, it would be incredibly valuable if the input value for an expression could itself be the result of another expression.
For example, we currently have an attribute, "automation_sap_vh_ph", which is simply a concatenation of two other attributes: "vh_string" and "ph_string". To use this in a dataset lookup, I also need to define a separate rule to populate "automation_sap_vh_ph" ahead of time, just to ensure the lookup has a valid value to work with.
Allowing nested expressions would eliminate this extra step and streamline logic. I do understand this could raise performance considerations, as the outer expression would likely need to resolve the inner expression into temporary memory before execution.
Here’s a simplified example of the desired behaviour:
Current:
{automation_sap_vh_ph|dataSetLookup 67e667df138afb001232c8b8key>leadtime}||999
Proposed:
{{vh_string + "-" + ph_string}|dataSetLookup67e667df138afb001232c8b8key>leadtime}||999
Thanks for considering this enhancement—happy to discuss further if helpful.
Comments
Please sign in to leave a comment.
Hi Colin,
Thank you for submitting a feature request! I’ve created a support ticket for it, and our team will pass it along to the developers for consideration.
We’ll keep you updated on the progress as things move forward.
Thanks again for your input!
Best regards,
Jess