Hello - I was curious about the design pattern you follow when you know up front that a w/f will require a CodeActivity class?
In this scenario, do you typically choose to delegate all w/f logic into the CodeActivity class? As opposed to using a mix of ui-based steps with the CodeActivity step?
Delegating as much logic as possible to the CodeActivity class seems to make sense in this scenario because this centralizes the logic and makes it easier to follow and maintain. No guessing is required, as to where the logic resides, or if logic in 1 place is breaking logic in another place?