Build better products with our product team
Description – When an account is deactivated, it should be hidden from relevant sections, i.e., Teams, Groups, Reports To, Direct Reports, and any other similar sections/fields.Why is this feature important to you – Automatically hiding them upon deactivation would provide a more accurate representation of active users and present a cleaner UX. It is convenient that accounts are not removed from the system, as it allows for easy reactivation and retains all their previous sections/fields.How would you like the feature to work – I would like to have a filter to exclude deactivated users where filters do not currently exist (see screenshots).Current Behavior – In certain places, it looks as if the users are still active (see screenshots).
Hello friends!I submitted this post before, but it got deleted during the Experience League migration. So here it is again!Right now, there is no easy way to generate a next- or previous page report in Analysis Workspace. It is something that has been requested countless times. We can do a bit with Segments from the Flow Visualization, but that is a very involved process. But since we are able to change Metric calculations with Attribution IQ, why not do something similar with Dimensions as well? I would call this: Pathing IQ!Ideally, we would have the option to change the Pathing logic for any Dimension by clicking the little gear icon, like with metrics:Once opened, we could change the pathing logic like with Metrics. Things we could select there could be items like "Current", "Previous", or "Next". Ideally, we would also have "Entry" and "Exit" in there to clean up the Dimensions list. All would be available for Visit and Visitor levels. It could look like this:Now we could break down one Dimension by another using that changed Pathing logic:So far for my thoughts. What do you think?Best,Frederik
In Workfront when you download a mutli-select excel, the output is sporadic and doesn't export in any realistic manner, like sorting in an ASC fashion. Obviously, there are ways to mitigate this within excel, but it ends up adding time to the admins as most of our end users would not complete the follow up needs to break up fields just to sort in a proper fashion. This really isn't a user friendly approach and would love if Workfront would just export in sorted fashion driven by the report.
Description -Reporting on fields that have display and skip logic in custom forms would be great functionality for system admins. When managing and updating custom forms it can be a challenge to Identify all of the logic that might also need to be reviewed and revised. Currently the only way to review display and skip logic is by color coding in fields that can be time consuming and easy to miss with custom forms that have many fields.
We ran into issues with list imports the other day that was due to a cluster issue in the sydney datacenter where our instance is hosted. We had 4 lists that were "being imported" and never finished even after 4 days. This got me thinking, we have a Campaign Queue, why not have a List Import Queue/History... This could get cumbersome with how some of us use lists (campaign Triggering) but if it is either tabbed or categorized, based on the following it should be easy to filter and troubleshoot:Possible List Actions:List ImportAPI List ImportFlow: AdditionFlow: RemovalHere is a quick and rough mockup -- forgive any inconsistencies, I'm writing in stream of consciousness.StatusActionList Name(With List ID and Link)Program/Location Name (With Program/Location ID and Link)Start Day Date & TimeEnd Date & TimeView list of...In ProcessList ImportLI 10 -- Import to Program(LI124488)EVSP 2017-07 -- My Sponsored Event -- MKTO-SFDC (PG2430)7/11/2017 10:00:007/11/2017 10:03:00Leads ProcessedQueuedAPI List ImportLI 10 -- Import to Program (LI12498)PROB 2017-07 -- My Promotional Outbound Lead Gen Program -- MKTO-SFDC (PG2410)7/10/2017 14:00:007/10/2017 14:05:00Leads ProcessedCompleteFlow: RemovalLI -- My Global Static List (LI1244)Lead Database (ML0)7/9/2017 15:05:007/9/2017 15:05:32Leads ProcessedCompleted With ErrorList ImportLI 10 -- Import to Program (LI124401)EGEB 2017 -- My Ebook Program -- MKTO-SFDC (PG2435)7/8/2017 08:00:007/8/2017 08:00:00Leads ProcessedLeads with ErrorsIn Process / StuckImport to ListLI 10 -- Import to Program (LI124307)EMOP 2017-07 -- Operational Email -- MKTO-SFDC (EBP435)7/7/2017 10:00:00AMLeads Processed to DateCompleteFlow: AdditionLI -- Static List (LI1244)Lead Database (ML0)7/6/2017 15:00:007/6/2017 15:01:32Leads ProcessedLastly, this type of view could be helpful for any asset, program, smartlist etc. Could be more widely applied.If this is already on your docket as part of an upcoming release mentioned at summit -- my bad, but I hope it helps Cheers,David
Description - While creating the proof, even the proof creator should receive the proof notification.Why is this feature important to you - With a personalized proof notification, the evidence maker will be verified.Current Behaviour - Once the proof is created, proof created won't receive the notification
Description - Since there are only limited possibilities to add a description to a field in the form builder, it would be helpful if it were possible to separate text from the actual label. for example Width (in mm).Why is this feature important to you - i am aware of the Instructions parameter, but this assumes that the user hovers over the corresponding icon.How would you like the feature to work - be able to enter bracketsCurrent Behaviour - brackets are not possible for label names
Description - Today, default Component Names in Customer Journey Analytics are based on the XDM display name of the field alone. However, that leads to potentially many components having the same name (1) while coming from very different paths in the Schema (2): This makes it hard to understand which, in this example, Type a component really is. To help this, CJA admins have to chose between two bad options: Leave the XDM Schema unchanged (using descriptive display names which only describe the current node) but having to manually change the component name in every connected Data View Changing the XDM Schema display name for all fields to include more information than actually required to avoid having to change many fields in CJA To help with this issue in CJA while keeping the XDM Schema clean, I propose to make the duplicate check smarter. Today, a number is added to the name to make the name unique. Ideally, in case of a duplicate component name, the display name of the field in question would be prefixed with the display name of the parent node, like the parent shown below: In this example, instead of showing up as "Type (3)", the component would be named "Web interaction Type" (field's display name prefixed with display name of parent node), possibly with a delimiter, like "Web interaction > Type". If that is not enough, more parent nodes could be added until the name is unique or the full tree has been traversed, in which case numbers could be used as a last resort. This small change would help users of CJA understand the context of a component, while making admin's lives easier.
When more than one user is assigned to a task, only the main assignee gets that task shown on their calendar. The secondary has no idea they are assigned. It doesn't show up on boards, calendars etc. Only in the WF project task list itself. Make it so both people can see the task if both of them need to work on it.
I have a big site with multiple of lines of business using a single report suite. And I am very efficient in how I create our processing rules. Nevertheless, the business size translates into a lot of processing rules within which are even more processing rules. I am the only one that creates the rules and I have a good memory. Still, remembering where a given rules is, or if it even exists can be a challenge. Currently I open all the rules (67 of them) then do a Ctrl-f and do a text search for the context variable, adobe variable, or rule name. It would be useful to have a less clunky way to search the processing rule list.This could be a simple as an expand all and collapse all link. Then folks can use a Ctrl-f to find the rule of interest.I have submitted a previous idea about being able to download the rule list. If this is done, one could text search the downloaded file.Or it could be a regular text search box that returns the rule number. In this case you would need to number both the rule and each rule element (The Then Do the Following items). Numbering each rule element would also be useful when working with others (such as adobe customer care) to point them to a specific rule.
Request for Feature Enhancement (RFE) Summary: Enable bulk tagging of pages that are Live Copies Use-case: The client is using MSM to keep thousands of pages in sync with Blueprints. The client wishes to group some Live Copies in Group A and some Live Copies in group B, the obvious grouping method is tagging. However, bulk tagging pages is not possible if the pages are Live Copies. Current/Experienced Behavior: Bulk tagging does not work on Live Copies Improved/Expected Behavior: Bulk tagging works on Live Copies Environment Details (AEM version/service pack, any other specifics if applicable): AEM AMS 6.5.16 Customer-name/Organization name: Toyota Motor Europe Screenshot (if applicable): / Code package (if applicable): /
Currently, when logging into Adobe Analytics, the default landing page is "Reports", referring to the old Reports & Analysis interface.But given that Analysis Workspace is the go-to for reporting, the default landing page should be "Workspace".Please change the default landing page.
Ability to report on issues, tasks, and projects together in one report
Request for Feature Enhancement (RFE) Summary: This is a request to have a scroll bar added to the bottom of the AEM Guides editor repository. Use-case: Some of our DITA assets have long titles that go beyond the maximum width of the repository. When there are multiple search results with such long titles, an author would have to hover over each one until the needed asset is found (imagine having to go thru hundreds of assets!). Current/Experienced Behavior: Some of our DITA assets have long titles that go beyond the maximum width of the repository. When there are multiple search results with such long titles, an author would have to hover over each one until the needed asset is found Improved/Expected Behavior: With a horizontal scroll bar, the author will only need to scroll left or right to be able to see the search result titles in full. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.12. AEM Guide 4.1 Customer-name/Organization name: Verizon Screenshot (if applicable): Code package (if applicable):
Description - A Source Connector for messaging queus Why is this feature important to you - Backend system uses AMQP for eventsHow would you like the feature to work - A Connector to enable consuming AMQP events, as an alternativt to the HTTP Streaming ConnectorCurrent Behaviour - No current support
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.