Hello,in the future we want adjust our application to Your new rules validation about "inconsistent flow". For us this issue relates to the database actions. So, when Database query should return single result, we set exit <Results> non-repetitive and it works. But when we use Database/Find model and set exit <Records> non-repetitive then validation throw error "Exit should be repetitive". For example when we find record by id, it's clear that result will be non-repetitive, and for now we had in the wrapper Action or Service exit non-repetitive. Because of the new rules in validation, warning will be throwed. I think there are 3 solutions:1) we handle every exits as repetitive - but it seems that won't be clear enough for developers2) we will add model Collections/First between repetitive source (Find/<Records>) and non-repetitive (Exit) - but i think that this isn't very good solution (to much refactoring - which in fact produces more code)3) Tersus Team will be support non-repetitive exit in Find models :) But I don't know, is it possible?Speaking of DataBase models.Model Database Query has exit <None> and would seems to be that one of exit <None> or <Results> always will exist, but it's not true.Example:We have Customer table which contains 2 columns: Id and Name. We retrieve customer table by Id and return only name. So if customer record has Id but Name is NULL then receives none of outputs. <None> not exists because record by Id exists, <Results>(Name) not exists because Name Is NULL (to avoid this situation we can change query or return data with Id). I wonder if this is expected behaviour? Maybe it's more natural to send such situation to <None> trigger?Best regards,Paweł GocNeoprimus.com
For best results, use the Firefox browser..