Closed prestoncabe closed 3 weeks ago
@Preston Cabe Do the years have to be numbers? For the income decision table I switched them to strings and it fixed it. My thinking is that it should be treated as a string since since it's more like a label and we don't need to perform any calculations with it. It's just telling us which FPL year to use. Or should I keep as a number data type and update? 2024-08-21 13:39:39,448 WARN [org.kie.kog.cod.dec.DecisionValidation] (build-28) Columns: [year] relate to FEEL string values which can be enumerated for the inputs; Gap analysis skipped.
@sierscse good point about it being more of a label… i think that’s fine! You might want to make a type for “fplYear” and make enumerated options of “2023” and “2024”.