Analysis Workspace: User Settings (e.g. setting default options) | Community
Skip to main content
roryo87435806
New Participant
October 21, 2016
Delivered

Analysis Workspace: User Settings (e.g. setting default options)

  • October 21, 2016
  • 19 replies
  • 26834 views

We've consolidated all threads related to setting default options into this thread, including:

___

Original ask for Anomaly detection on/off:

It's fantastic to have gotten anomaly detection in Workspace in today's release. One point of feedback however would be that the function should be off by default when adding a new metric, with an option to turn it on.

The reason we believe this is, workspace is used by a variety of end users throughout our organization (from technical to non-technical). For some of the non-technical users seeing an exclamation mark or anomaly has the potential to cause confusion and spurious concern. We therefore believe that having the default as off, would allow the anomaly detection to be more appropriately managed and used within our organization.

Thanks in advance,

Rory

19 replies

New Participant
October 12, 2021

Need ability to change default metric from Occurrences to Visits.

Employee
March 26, 2021

Part of this request was released today! A new user preference page was added, laying the foundation for user-level settings to be applied across projects. The first set of preferences included on the page are documented here: https://experienceleague.adobe.com/docs/analytics/analyze/analysis-workspace/user-preferences.html

We would like to continue to add preferences to this page in the future. Please share your thoughts on the next preferences that should be considered.

Employee
July 22, 2020

@dominiquep87063 this functionality remains on our backlog for future consideration!

New Participant
July 20, 2020

Hoping everyone is doing well! Is there any update on this work? It would be great to be able to set a default Report Suite. Thanks!

Employee
January 13, 2020

We'd like to do some research on this topic of customizable user settings & defaults. If you are interested in participating, please message me with your name, company and email address. Thanks!

Employee
December 19, 2019

We'd like to do some research on this topic of customizable user settings & defaults. If you are interested in participating, please message me with your name, company and email address. Thanks!

Employee
July 30, 2019

We've consolidated all threads related to setting default options into this thread, including:

Employee
April 20, 2019

Thank you for this context - very helpful.  We certainly do still have places in Workspace that need interaction performance improvements, but to be honest I haven't experienced them in that use case that you specify.  However, if you are seeing them there, then we need to investigate further.  The other good news is within the next few months, we are going to be rolling out some major performance enhancements to the line/area chart, which I believe should help the issues you're seeing (I'll be curious to hear if they do).  Thanks!

Jennifer_Dungan
New Participant
April 20, 2019

Hi Brandon,

Thanks for the update, the ability to change the default preferences would be fantastic.

Also, while performance has gotten much better, I feel that while the data returns for the report, I always found the interface laggy when I had the "searching for anomalies" message. It's a lot better since I got a newer faster machine, but my old machine I really noticed the issue. So it's more about the report / interface performance (slowness trying to scroll the reports, perform additional actions, etc), rather than waiting for the primary report data; especially on larger reports.

Employee
April 19, 2019

Thanks for the feedback - a few updates/notes on this.  We are actively working on providing a bunch of customizable user defaults for Workspace so you could potentially turn off anomaly detection for new projects (along with a bunch of other settings).  We know this functionality is important to you, and are doing our best to prioritize it on the roadmap.

I do have a follow-up question though, just so I'm understanding better.  For time-series data (ie, data shown on a line or area visualization), we make two separate requests - one for the normal data, which normally returns very quickly, and then a second request for the anomalies (when it's saying "searching for anomalies..."), which usually takes a little longer.  We intentionally split the requests so that it wouldn't slow down the initial request.  So I'm curious as to why you feel like this really drags down performance, if it doesn't affect the initial request (it's just extra, and shows up when it's done).  Thanks for your help.