In Test Conductor, a Test Scenario can check/drive argument values.
We have created our own types package, which contains new simple types like :-

typedef OMBoolean bool_t;

We make these new types available via the drop-down selection list by using the General::Model::CommonTypes property.

I understand that for complex types such as std::list, we need to create serialization/unserialization functions as shown in the sample project, CppListUsage.rpy.

I was surprised when our bool_t didn't work in a Test Scenario. Will we need to create serialization/unserialization functions for all our types even they are merely typedefs of simple, built-in types?

Maybe what I'm asking is where do the the serialization functions that come with Rhapsody live? Then I can use these on my 'typedef'ed versions of these types.

We also have our own types package and it works without any serialization functions.
I'll check next week if we set some special properties.

By the way:
IBM will realize a automatic animation of enumeration and structures in the coming version of Rhapsody