Existing Functionality: In v14.7 SiteCatalyst dashboards, a report detail will only display a max of 30 rows. This is a decrease from the 50 row limit in Legacy Dashboards. The reportlet will no longer span more than a single page.Idea: Increase the number of rows in reportlet details to 50, to match that of existing Legacy Dashboards. Additional functionality would allow users to set the row limit to a max of 200(?), which would then automatically paginate.

Existing Functionality: Currently variables such as s.pageName and s.prop have a 100 character limit. This is extremely limiting when implementing a page naming strategy, particularly when including additional information with the page title. For example, site and country. In global suites, its often important to include additional information such as site, country, or a unique page ID to ensure the page name is unique and allow for additional pathing data.Idea: Increase the character limitation...

Idea: Provide admins and/or users the ability to get a list of reports to which a given global calculated metric is associated. This will help admins determine which reports would be impacted when a global calculated metric is edited or deleted. This will also help users understand how a particular calculated metric is being used and provide context to how users might benefit using the calculate metric in other reports/analyses.

Existing Functionality: Currently when you reposition and move reportlets in a dashboard it can result in other reportlets in that dashboard shifting out of their previous position. This occurs most frequently with larger dashboards that contain a significant number of reportletsIdea: Provide users the ability to lock or pushpin reportlets within a dashboard. This will prevent reportlets from shifting when moving/adding/removing reportlets on a dashboard.

Existing Functionality: Currently users select a date range for each reportlet within a dashboard. Users must edit each reportlet to adjust the date ranges or make all reportlets use the same date range. Idea: Provide users the ability to select a 'global' date range for reporlets in a dashboard. Selecting a single 'global' date range for a dashboard would reflect that selected date range throughout all reportlets in the dashboard. This would greatly reduce the amount of effort with updating or ...

Existing Functionality: Currently users are unable to add the Lifetime Click-through metric to reports, similar to those available for all custom events.Idea: Provide users the ability to add the Lifetime Click-through metric to reports

Existing Functionality: Currently users must go to the Metric Selector window to add/remove metrics by clicking on the 'Showing' link on the report.Idea: Provide users the ability to add/remove metrics from the report details page, without having to go to the Metric Selector window. There are several ways of doing this via a dynamic reporting interface, however; the attached is an example of how it might integrate into the existing interface. In this example, there would be a flyout menu to be a...

Existing Functionality: Currently when users login at http://my.omniture.com, they're directed to the Omniture Suite pinwheel page to select the product they'd like to access.Idea: Provide users the ability to select a product, via a dropdown menu, they would like to access when entering their login credentials. Omniture users often use the same couple of products on a regular basis. This would eliminate the extra page and subsequent click to select the product from the Omniture Suite pinwheel, ...

Existing Functionality: Currently, users are able to select when to check values (month, week, day, hour) to determine if the alerts rule is met. There is no existing functionality to be able to set alerts for a specific granularity or time frame.Idea: Provide users the ability to define a granularity for the alert rule. For example, Check daily values at the end of each Week. If the rule is met on any given day, send the alert. In other words, the rule should match against the daily value and n...

Existing Functionality: Currently, when users wish to remove an active correlation from a report, they must click on the Correlation Filter link under the Configure > Report menu on the report and make changes from the Correlation Filter window.Idea: Provide users the ability to remove active correlations from reports via a single click on the Correlation Filter link under the Configure > Report menu. This functionality would be similar to how users are currently able to remove Filters by clicki...

Existing Functionality: Users often have to set multiple parameters, includes (Contains) and excludes (Does not contain), to get very specific results in reports. For example, the Site Content Pages ranked report. Filtering the report details is often done when trying to display specific results for a Dashboard reportlet. A filter may inadvertently include additional unwanted data when data for new items is captured and displayed under the previously determined filter.Idea: Provide users the fea...

Existing Functionality: Custom events can represent a very large number of actions, from the general to the specific. Without training or documentation, there's no easy way within the interface for Omniture SiteCatalyst users to know what a specific custom event represents.Idea: Provide administrators the ability to add annotations for custom events, which would be displayed within the metrics header of report details via the '?' annotation icon. See the attached image for how its already done f...

Existing Functionality: Currently, when users need to update metrics, filters, or dates on a bookmarked report, they have to recreate and reschedule the report. When managing a significant number of bookmarks and scheduled reports, changes can be very time consuming if updates are required.Idea: Similar to the Edit/View Report functionality on Dashboards, users could Edit a bookmark. Users could make changes to all criteria of an existing bookmarked report without having to recreate and reschedu...