Virtual Paths / Filepath Aliases

** Raised in response to support request 1092204. From a product perspective, the ability to logically consolidate content located across disparate systems is a very valuable capability. **

Hello Support

We've just started a trial and we're up and running ok. However, there's something I haven't been able to figure out that we've done with other systems.

With the virtual directories, I haven't found a way to create a 'virtual' hierarchy to logically organise the network resources we have mapped. So we end up with a very long flat structure which is going to prove problematic quite quickly.

What I'd like to be able to do is create a virtual hierarchy, such as the below:-

Active Projects
--- Project A
---- UNC Resource A1
---- UNC Resource A2
---- etc
--- Project B
---- UNC Resource B1
---- UNC Resource B2
---- etc

On other systems I could set the 'Name' to 'Active Projects/Project A/UNC Resource 1' and everything up to final directory element (if it didn't exist) would be still be presented for navigation, but would essentially be a 'dummy' directory.

Am I missing something?

Best
- James