Skip to main content

Ideas

Filter by idea status

10000+ Ideas

brentradLevel 5

Allowing segment updates to be reflected in other segments that use it as a referenceNew

Description -One feature of the Segment Builder is the ability to use existing segments when building out a new segment. I'll refer to this as a "reference segment".Once the reference segment is dragged into the Segment Builder it becomes "disconnected", and is more like a snapshot of what the reference segment looked like at the time. If an update is made to the reference segment this will not be reflected in any other segments that use it. It would be nice to have an option to "anchor" the reference segment so that any updates made to it are also reflected in other segments. This would preclude the Adobe Analytics user from having to find and update every segment that used the reference segment, and would ensure that changes to the reference segment are immediately reflected across all reports. This feature can be limited to only public segments. There are several risks associated with this idea.Uers may not be aware of how many segments use a particular reference segment as an "anchor", and thus may not truly understand the ripple effect caused by an update. Users would have to be provided with some sort of notification in the Segment Builder that shows both that a segment is being used as an "anchor" (think of a little icon next to the segment name) and which segments are using it as anchor. This option should require permission rights from an adminA change to the reference segment may break the segment logic of other segments, making them no longer work. This could happen if the container types in the reference segment were adjusted. One way to alleviate this would be to disallow the use of anchor segments in some cases, such as in sequential segments. Another option would be to not allow the anchor segment to update in a segment if the segment logic will be broken. The user would then have to be notified of the segments where this occurred so that he or she can make necessary adjustmentsWhy is this feature important to you -My organization often uses several core segments for KPIs, and then creates more nuanced segments based off of these core segments. The number of segments that use the core segments are substantial, meaning that a small change made to a core segment requires updating a large multiple of other segments with the same small change. How would you like the feature to work -When a reference segment is dragged into a new segment in the Segment Builder, a user can click on the gear option and select "Anchor Segment". Any updates made to this reference segment will automatically update this segment as wellThe Segment Builder page for the reference segment should indicate whether the segment is being used as an "Anchor Segments". This can be done using an icon or some similar call outThe Segment Builder page for the reference segment should contain some sort of interface for showing which segments use this segment as an "Anchor Segment"A warning should appear when someone tries to update an "Anchor Segment", telling the user that updates to this segment will impact other segmentsCurrent Behaviour -Dragging an existing segment ("reference segment") into the Segment Builder creates a copy of the existing segment. The reference segment component of the new segment will not update if the reference segment is updated.

amznJWLevel 2

FUSION: Stop Button Outside of the ScenarioNew

Description - Need a way to stop a running scenario from outside of the scenario itself.   Why is this feature important to you - If a scenario is running on a schedule and I need it to stop, I have no way of doing so.  If I open the scenario while it is already running, it is hit or miss as to whether or not it will even display a Stop button.  Even if it does display the Stop button, it never works.  I have literally a 0% success rate of that button ever having stopped a scenario under these conditions.   Additionally, if I have started a Scenario by clicking the Run Once button and the scenario decides to freeze up in my browser (this happens a lot and is becoming more and more frequent), then there is no way to stop it.  I have to wait the full 45 mins for it to time out before I can continue working on it because the stop button won't work after the freeze up and if I refresh the page, I just get a view of the diagram, not the progress of the current cycle and I run into the same situation where it is hit or miss as to whether or not the Stop button will appear and even if it does, it won't actually work.   How would you like the feature to work - When viewing the list of scenarios in Fusion, there should be a Stop button for each scenario that is accessible without actually opening the scenario.  Similar to the toggle switch that controls whether it runs on a schedule or not.  If/when it changes to a Force Stop button, that button should truly function as a force stop, literally killing the process running that scenario immediately without regard to anything it is doing at the time.     Current Behaviour - there is no button like I am describing.

ewong-2Level 2

Adobe ID: Remind User to RegisterNew

Description - For organizations that have migrated to Adobe ID, Workfront no longer provides the functionality to "Reminder User to Register".  When doing so, Workfront will error "We were not able to send the invite email. You can try to resend it later, or talk to your Workfront admin." and will erroneously update the Expiration Date (but no further notifications were delivered).Why is this feature important to you - Our customers often cannot find or lose emails in their inbox.  Ever since we migrated to Adobe ID, we cannot resend the invite email to the address. Further, we cannot delete users.  Nor will Workfront allow us to create another account with an existing email address.  We have to modify the name and email address of the user, then inactivate, then re-create a new user, etc.  This is not an ideal solution and causes our user count to soar as we onboard groups of new customers weekly.How would you like the feature to work - Within the Admin Console (or ideally the "Reminder User to Register" function within Workfront would just work), an option to resend the registration email would be appreciated.  In addition, it would also be great if Adobe/Workfront would restore the ability to permanently remove a user from Workfront.  Current Behaviour - Workfront will error "We were not able to send the invite email. You can try to resend it later, or talk to your Workfront admin." and will erroneously update the Expiration Date (but no further notifications were delivered).