When loading a page in the interview, all conditions are resolved for each set using individual HTTP requests. This is unsustainable and breaks down if to many conditions are configured (there is a case with 70 conditions resulting in 350 requests.).
A solution would be to collect the requests in the front end and refactor the resolve action in ProjectViewSet to accept and check lists of parameters (probably as POST).
Since the same check is done on each update, the front end could also communicate what value was changed so that only the conditions affected by this value could be checked.
When loading a page in the interview, all conditions are resolved for each set using individual HTTP requests. This is unsustainable and breaks down if to many conditions are configured (there is a case with 70 conditions resulting in 350 requests.).
A solution would be to collect the requests in the front end and refactor the
resolveaction inProjectViewSetto accept and check lists of parameters (probably asPOST).Since the same check is done on each update, the front end could also communicate what value was changed so that only the conditions affected by this value could be checked.