Hi
Yeah that’s true.
All object instances that your orchestration refers to directly or indirectly (as through other objects) must be serializable for your orchestration state to be persisted.
So there are two solutions for that
1.You can have a nonserializable object declared inside an atomic transaction. You can do this because atomic scopes do not contain persistence points.
2. You can serialize your own classes if you mark them with [Serializable] attribute
Best reagdrs,
Nandika