Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

FrederikWerner
FrederikWernerNew Participant

Bring the Page Summary report to Analysis WorkspaceInvestigating

Hello fellow Adobe-pros,With the new Workspace landing page beta, it is quite apparent that Reports & Analytics will become more and more obsolete. And I'm a big fan of that! But still, there are some things that I would love to have in Workspace to make life a lot easier for our business users.One of those features is the Page Summary report in R&A: For business users who just want a quick overview over a certain page (or other pathing-enabled prop) this feature is super helpful! We have something similar in Activity Map, which is also quite cool:Luckily, from my point of view, it should be a relatively simple task to bring this to Workspace. As a basic replacement, we would just need a Line Chart, a Flow visualization, and some metrics in a dedicated panel. I'm thinking of something similar to the Quick Insights panel, which is super user-friendly:We could reuse a lot here. The Metrics selector wouldn't even be necessary! What we would need:A dimension item selector that supports drag-and-drop from the component railThe existing segment selectorThe existing date range selectorUpon building the panel, we would get a line chart with the performance of the dimension item over time and a date comparison, a Flow viz with the next and previous item, as well as some standard metrics like Occurrences, Visits, Unique Visitors, Time Spent, Single Access, etc. That would be some awesome value for a first iteration! On a second iteration, we would ideally also have the option to have a tabular representation of the next and previous item. All we need is an automatically created segment in a Freeform Table (see https://www.fullstackanalyst.io/blog/web-analytics/analysis-workspace-hacks-next-and-previous-page-report/?r=el for a way to create that segment out of the Flow viz). To make the metrics section more useful in that second iteration, it should now also include dimension-specific metrics like instances of a certain Evar. A third iteration would go even further. Instead of just a table with the next and previous item, we would get the Pathing IQ feature (https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-ideas/next-and-previous-page-in-workspace-pathing-iq/idi-p/364615) I proposed a while ago. Also, the metrics section would get an awesome overhaul by using an existing feature: tags! In addition to the generic metrics from iteration 1 and instances from iteration 2, we would now also include metrics that have the same tags as the used dimension item. So, if a dimension is tagged with "Marketing", we would pull in all the metrics that are also tagged with "Marketing". That would bring even more context to the analysis and help us to customize the report to our own business needs. Let me know what you think!

maryd51New Participant

Automation of Adobe Target Access Management using UMAPINew

DescriptionAutomation of Adobe Target Access Management using UMAPI Why is this feature important to you:As a Financial Services organization we would like access management of Adobe Target roles to be automated using the Adobe UMAPI.  The automated process helps us to be compliant, with the right monitoring and controls in place and no manual touches. How would you like the feature to workWe would like Adobe Target access management to be fully automated* using the UMAPI same as other Adobe products in our organization such as Analytics, Launch, et al. This would also help us be compliant and remove the vulnerability written against Adobe Target. More than happy to review our current set up with the Product team and support any way we can.  Adobe Team knows how and where to reach Mary Daniel. Current BehaviorAdobe Target has 4 roles.Approver - Can create, edit, and activate or stop activities. Editor - Can create and edit activities before they are live.  Editor cannot approve the launch of an activity. Observer - Can view activities. Observer cannot create or edit them. Publisher - Similar to the Observer role, Publisher can view activities.  Publisher cannot create or edit them. However, the Publisher role has the additional permission to activate activities. My organization uses the Adobe UMAPI to automate access management.  *We use Active Directory Roles in SailPoint to request and manage access.  These roles are aligned with Product Profiles/Workspaces in the Adobe Admin Console.  Once the role is approved/removed in our access management platform for a user, the AD role syncs with the UMAPI and automatically administers the access in the Adobe Admin. When an Adobe Target user is granted a role, irrespective of the whether the user is approved for Editor, Publish, Approver or Observer, the access defaults to Observer in the Admin Console. As result, once the access is administered in the Admin Console, System Admin is then required to follow up with a manual workaround involving switching the user to the correct role approved through our Identify and Access Management.  This has caused a Vulnerability to be written against the product. 

jlanssie-lnlNew Participant

Unable to cancel inheritance on parts of a Content FragmentInvestigating

Request for Feature Enhancement (RFE) Summary: We are not able to cancel inheritance of certain parts of a content fragment. This makes our authors' output three times slower on content fragments. And it increases the risk of human error/inconsistency significantly. Use-case: A multilingual setup where Content Fragments are used in Assets. These Content Fragments each have a Blueprint (en) and have Live Copies, for each language we use (e.g.: nl, fr, de). And each Blueprint Content Fragment, consequently each Live Copy, contains language-specific content and language-agnostic content. Current/Experienced Behavior: Creating Live Copies with synchronization works fine. However, upon synchronization, the Blueprint Content Fragment overwrites the Live Copies entirely. This problem makes the synchronization of Content Fragments with both language specific and language-agnostic content obsolete. The synchronization can only be used safely for the initial creation of the Live Copies. As soon as an Author puts language-specific content in a Live Copy, synchronization (intended for language agnostic content) is no longer possible, because the synchronization will overwrite the language-specific content with content from the Blueprint.   The inability to use synchronization on Content Fragments with both language-specific and language-agnostic content is large. It essentially means Authors need to repeat the same change in the Blueprint and each Live Copy individually. Improved/Expected Behavior: Ability to cancel the inheritance on each field inside a Content Fragment. When an Author does a roll out of the Blueprint Content Fragment, the fields with canceled inheritance (language-specific fields, such as descriptions or titles) are not overwritten.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.8.0 Customer-name/Organization name: National Lottery Screenshot (if applicable):   Code package (if applicable):