It all depends on your business case. You want to make your section in a class visible by the flow action in which you are going to embed it. You could make them both in the same class or reference a different clipboard object to change the class context. Likewise, your flow needs to have visibility into your flow action or you won't be able to reference it. If your flow is a Data- based flow, then you'll probably need the flow action in the same class or a superclass visible from there. If your flow is based off of Work-, you will need to put the flow action there. You definitely want to locate your records in classes where they are reusable, but not so far down the class hierarchy that they are cluttering up superclasses needlessly. To some extent, this will be bounded by the properties you want to use since you can't reference properties outside of the current class hierarchy.