The reported behavior is not supported in our current version (2.1.0.2). But we have implemented this now and it will be available in our upcoming release which is planned for roll out by end of this week.