Alternatives to Object Type Decision (Inheritance split)
In nanoflows, you are not able to use an object type decision. For example, if you have the generalization member, and the specializations student, professor and caretaker, then there is no way to determine with the input parameter member what the specific specialization is, using object type decision (Inheritance split). What are work arounds or alternatives to still achieve the Object Type Decision in a nanoflow?
Instead of using an inheritance split, you can do a db retrieve constraining on ID;
ID of specialization equals the Generalization, so this can be used for a retrieve on specialization level is generalization is know.