When using the 'Record Changes' feature on a Perforce repository, it does not appear to create the workspace being referenced (using the settings specified in the repository definition) when it does not exist, nor does it emit any sort of error or warning indicating that it doesn't exist.

In this regard, it would be ideal if it worked in much the same way as the 'Checkout' feature.