This is a known issue that is to be fixed in v1.3 release of the core.
Revision History
1/9/2012- Initial release