Imagine you have a bunch of different credits all with different installement plans. So you have yearly, one-time, bi-weekly, monthly and so on payments. If you would store all of these in an ENUM-field and check the field value in a microflow with a decision, the longer the enum is, the more chaotic the microflow.
But if there would be the possiblity to create a table where the microflows are directly mapped to the keys like yearly mapping to Microflow CalculateYearlyRates, one-time to CalculateOneTimeRate and so on, it would be really easy to extend the lists.
Max