T. Rowe Price would like to develop a common access control profile per user group. User groups are defined (loosely) as Administrators, Power Users and Read Only Users for example. Adding a license to the Administrators access group is relatively simple as that license has full access to all directories on the FSU. The other two access groups are harder to maintain due to the strict definitions required for appropriate set up of access by dataset. An administrator must create multiple read only...

Would it be possible to configure a dataset to provide an e-mail notification when it reaches 100% after log processing and transformation? We often perform log processing events over the weekend. This would be helpful for us to understand if processing completed successfully or if an unexpected issue happened over the weekend, causing processing not to complete in the expected timeframe.

We would like to have the ability to override the None default for dimensions to something more meaningful. For example, we have the following referrer #'s: Page ViewsInternal Referrer213,923External Referrer35,718None736 We would like to show it as this: Page ViewsInternal Referrer213,923External Referrer35,718Referrer Not Available736 We probably can perform a bunch of rename dimensions but would prefer to leverage the Default option in transformation configruations.

The Adobe copyright overlays visualizations and pertinent information when analysts are exporting data to PNG for presentations and reports. We are not able to move the Adobe copyright text. We would like to designate a footer area for the Adobe copyright text that always appears below visualizations and pertinent information on the workspace. Basically, the footer area is a read only field where visualizations, tables, etc. can not be placed over. See Incident:101028-000343 for more information...

When selections are in use from the sidebar panel and the workspace is submitted to run in compute in background mode, the query re-starts when the completed workspace (or still running workspace) is opened. It appears that the selections panel redefines the query when opening the workspace running in compute in background mode. We would like for the sidebar panel (selections panel) to understand when a workspace is running in compute in background mode. Thus, when the workspace has completed, t...

Currently, you are not able to disable the sidebar panel, only minimize it. We would like to allow analysts to empower themselves in how they navigate through the insight client. Providing this flexiblity, would also provide the administrator with the means to toggle the features on or off depending upon known issues, reported bugs or client satisfaction. In addition, the concept of the sidebar panel could be reserved for power users who are familiar and comfortable with the insight product. The...

When filters are enabled via the filters panel and the workspace is submitted to run in compute in background mode, the query re-starts when the completed workspace (or still running workspace) is opened. It appears that the filters panel redefines the query when opening the workspace running and/or completed in compute in background mode, thus rendinger compute in background functionality obsolete.We would like the functionality for the sidebar panel (filters panel) to understand when a workspa...

When using the compute in background function ... when a metrics legend is available in the sidebar panel for a particular workspace, the workspace considers the metric legend as being its own query. This action causes the workspace to re-start the query, thus rendering compute in background functionality obsolete. We would like to request a change to allow the metrics legend to be used as a display only (read only) thus preventing the workspace from starting the query over again when the worksp...

This is again something we spoke about at Omniture Summit 2011 but wanted to put this out here officially for discussion. Since Insight is a multi-channel product, we have been looking into possible options to incorporate non-web data as a log source. While this is feasible with the current technology, the need for the non-web data to be time-based is a constraint on opportunities and we've had to create false timestamps and sequencing in order for the data to load properly. We'd like to see the...