Remove serialization depth limit for unknown output types in graphical workbooks
It is sometimes necessary to access member objects and nested properties of activity output. When the output type is not known, serialization / JSONification occurs with a depth of 1. This obliterates member objects, lists, arrays, hashtables etc.
Please could unknown output types be treated as objects so that their members survive the serialization process?