candy2012, I suspect the gap in the documentation is because programmers often forget that people don't know the basic concepts which the programmers learned long ago. In this case, the basic methods of how to make the data be displayed automatically are not documented where we're looking.
How to manually make data appear is documented, but it's outdated. One of the example pages shows fields being created, and the field editing page includes the shortcodes needed to display the data. The current version of Types has replaced that with a Types shortcode generator (an icon at the top of the edit page, in the same row as the image-insertion icon).
But inserting a shortcode in the same post which contains the data is only useful in some situations (ie, providing a fill-in-the-blanks tool so someone doesn't have to edit some messy HTML). How to make a certain custom post type emit data automatically is not pointed out -- at least not well enough. Even in the "Views" documentation, they seem to show how to make a page emit data from Types, but I haven't noticed a way to define how a custom post type should be displayed.
For example, if custom posts are searchable, a search result should find the single entry for a specific house or magazine article (using their Realty and Magazine examples). But how to define the default display for that custom post type is not apparent. We who haven't yet tried it can hope that is because there is an admin menu option which makes such definitions obvious. But it's hard to decide on what technology to use in a site if the needed details are hard to find.
The Views PHP Integration document does say:
Renders a view and returns the HTML output."
That's fine and dandy for a WordPress programmer who knows where to use that. I know plenty of PHP, but for WordPress I know what "the loop" is for, that there seems to be something "single" for posts, and how a plugin hooks in. If there are common places to use that PHP, it would help if those were mentioned.
(Me, I'm pretty sure that I need Types and Views, but I'm waiting for a reply to a question related to subdomain sensitivity which was sent to them recently.)