We respectfully submit that that is a “nonsense” answer. You simply make a lookup table in your back end code that translates front-end elements into P-codes to be sent to the phones. Otherwise, you’re saying that if we deploy 20 GXP2140s to customer X and 20 GXP2140s to customer Y, and all of X has one VMPK configuration, and customer Y has two different VMPK configurations, that we have to program all 40 phones individually. That is a logistical nightmare.
So, too, is the nightmare of one customer who has more than one kind of phone. You can’t program all GXP2160s to have that customer’s configuration, nor can you do the same for all 2140s or all whatever else.
No, the best solution is to have VMPK configurations at the group template level and spend some time programming it to make it work. You make us do it all the time when you release firmware updates and have P codes that do the same thing on different phones but are literally thousands of numbers apart from each other. Your programmers can do the same.