In addition to the ability to create Routing Rules at the File, User and Group Level as one can do now, customers would like the ability to create Routing Rules at the Folder level. This would allow admins to have a folder in which more general reports could be contained and they would not have to manage each report individually.
Customers have different use cases. One customer uses Spotfire in house and would like to be able to have a general folder from which reports could be routed and scheduled all the same without one having to manage each report individually.
Another customer uses Spotfire for their customers such that their Library structure has a folder with subfolders for each Customer. They would like to be able to manage reports for a customer as one entity. For example, all the reports for CustomerA would be routed to the same Resource Pool since one could have resource pools setup by customer. Instead they have to manage each report individually for each customer which can get rather unwieldy.
0
Future Consideration
Currently rules can be created at group level or file level,
if users in groups overlaps the rule becomes useless and if I want to direct 1000 analysis to a specific application pool contained in the same folder, I will have to create a rule for each one of these analysis file, so very difficult to maintain...
When customers make the effort to have a performant architecture with load balanced servers, one can feel limited by application pools rules.
For customers using the Spotfire platform in a clinical trial context, the capability to define routing on folder level can also help with compliance challenges like - can we ensure that all traffic related to a specific clinical study (analyses for which are stored in a specific library folder) can be routed through infrastructure located in a specific place (country), similar to Peters last use case above.