[OutTracker] GetCases Data action: inefficient implementation
Forge component by OutSystems R&D
Application Type


I noticed that the GetCases data action on the RequestList screen does the following:

To me this seems like a bad practice.

This generates n+1 requests,  where n is the number of cases.  This could become very slow very quickly.

Wouldn't it be better to implement this using an Aggregate that can join Case and Ticket on the DB level?

OutTracker is supposed to be a reference implementation of the case management framework.  If users copy this way of working I believe they will have a bad experience with the framework.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.