Hi,
Thanks for all the answers - i actually did not think of the solution using formats but that can surely be a good way to realize some of our needs. However, there are, as you mention (but i forgot to), much more complex needs that need a more complex solution and it is here that the "meta table" (not sure this is the right name for it though, hope you know what i mean anyway) comes handy. Using this by importing it in a pre-step before executing the code looks like a good technical/structural solution. The main issue here is that i believe there could/should be a generic way to design such a table which we, in order to prevent reinvention of the wheel, would be really interested in.
Some of the logic (no bore-to-death try attempted) we are looking to solve are for instance also:
if 0 GT (inputOne - inputTwo) LT 1024
then TheOutPut = oneMoreVariable * 1.5;
else if 2048 GT (inputOne - inputTwo) LT 4096
then TheOutPut = oneMoreVariable * 1.66;
which is a more challenging and complex due to the need to represent combinations of expressions in the metadata. This can surely be done, and since there are no rocket science related expressions - rather just simple expressions stacked together, this should be possible to realize in a meta table.
Just a clarification, i am by no means writing here to avoid doing the work myself, i´m just curious if there are any general approaches for dealing with this type of data-driven design since i feel there are a lot of mistakes possible to make when trying to design this table.
Kind regards,