Hi folks! I'm interested in understanding best practices for using rich objects as inputs to flows. Right now my understanding of the options is: • Create flows which subclass a rich object and now I have access to methods/attributes of that object ◦ Con: requires copy-pasting flowspec boilerplate for each new instance you want? • Use strings/enums which map to rich objects as regular Parameters • ? my general goal is to take something like

MyObject

and have that as an input to a flow where I expect the flow logic to stay the same, and

MyObject

to change but because

MyObject

is not neatly serializable, it would be a bit of a pain to create a mapping from JSON ->

MyObject

(and I would lose all of the convenience of the validation/discoverability/autocomplete of that object!)