Skip to main content

Filter by idea status

10000+ Ideas

DavidLu17Level 3

Rearrange segment tiles and dropdowns on top of Analytics Project panelNew

Often when composing a new panel, I add multiple segments, then later realize that it would be best to display them in hierarchical order from left to right, especially putting fixed segments on the left, and dropdowns on the right. But they appear only in the order in which you add them, and can't be moved, with one exception: a Date Range dropdown can be dragged to the end in the blank "add segment" spot and then appears as a new, duplicate segment, so you can then delete the original and keep the date range on the end. It would be nice to be able to do this with other segments, but when I attempt it, I get an endless activity spinner. Better yet would be the ability to rearrange them all however you like.This feature would be especially useful in cases where I created dropdowns with many entries, which are tedious to redo, so I try to copy panels from other reports that already have them and then edit as needed. See the attached images for a use case.   1. Painstakingly created long dropdowns for Product Category and Product Code, either in situ here, or in this case, in a panel copied from another project.2. In this project, the whole panel should be filtered for Product Division (a static segment, not a dropdown), so I add this on the end. I would like to move it to the far left.The desired order would be Product Division | Product Category | Product Code Name | Date Range3. Existing Date Range dropdown can be dragged onto the empty, end position (Drag a Segment here box), creating a duplicate.4. Deleting the original Date Range leaves the new one at the far right, as desired (5) but this operation cannot be repeated with other segments or dropdowns, only Date Range. Would be even better to be able to reorder them at will by dragging, as you can with table columns.

Enable quick filter to find "shared system-wide" in reportsNew

Description - It would be useful/nice if the funnel quick search button above reports could filter for all words seen on the reports. Currently it seems to do so only for some.  Scenario - I have created a Dashboards report, in which there are these two columns: Shared With, and Shared System-wide (both native fields found in the Columns portion of the report builder). Some of these dashboards are shared system-wide. For these ones, under the Shared With column, I can see one of the line items saying "System-Wide"; on the other column is says "True". If I use the little funnel filter above the report, I can filter for the word True and the relevant dashboards show up. If I filter for the words Sytem-Wide, the filter returns zero results. It should return the same number of rows as the previous search/filter. Why is this feature important to you - it's impractical, and inconsistent. I found this one behaviour in which the filter returns zero results on something listed within the cells of the report, but I am not sure what it is not being read. The other thing is that now I can't remove the Shared System-wide column, even though I have the information already listed in another way in the Share With column: my report shows duplication of data and that's not a best practice. How would you like the feature to work - I would like the funnel search/filter option to work on all words/information listed within the report, not just some. 

Provide a "upgrade.log" in cloudmanager with timestamp, version before and after the upgrade, identity triggering the upgrade, nlink to release notes, and notes (eg. ticket though which an upgrade was requested),New

Request for Feature Enhancement (RFE) Summary: In order to troubleshoot issues effectively each AEMaaCS should expose an upgrade log so development team can debug issues effectively (i.e. there was no feature deployment and something stopped working all of a sudden).   Information I'd like see inside:- timestamp- AEMaaCS version/release prior to and after the (up|down)grade - who (or what; mind that RO/RV is out there) scheduled/triggered a deployment- is given version already deployed or a deployment has to take place to enforce that- notes (i.e. if the upgrade was requested via support ticket then I'd love to see a reference to that)   Moreover it'd be great if such a log is available via Cloud Manager API (1 per environment). Use-case: Identifying if, why and though whom an upgrade was executed (also to analyze why some feature "suddenly fails") .If a feature fails to work through an upgrade - this is impossible to determine or debug. Current/Experienced Behavior: If a feature fails to work through an upgrade - this is impossible to determine or debug. There is no way to identify an environment has been upgraded, when , for what reason and by whom. Improved/Expected Behavior: Ability to review the upgrades, eg. through an "upgrade log" (available for download and "Tail"):* timestamp * version before  the upgrade * versions after the upgrade * identity/person/process triggering the upgrade * link to release notes * notes (eg. ticket though which an upgrade was requested), Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

AEMaaCS version information: being able to determine current version, latest version and being able to upgrade envrionments (dev) though CLINew

Request for Feature Enhancement (RFE) Summary: At the time of writing AEMaaCS environment API [1] does not allow me to: inspect which version of AEMaaCS given environment runs check if the version I have is the latest upgrade the environment programmatically. The only way to do it is via Cloud Manager Web UI (non PROD envs) or support ticket (STAGE/PROD). The latter may not be something Adobe considers doable (due to RO/RV), but we'd love to see such a feature for lower level environments. We has dozens of dev environments spread across multiple programs, so it is cumbersome to keep them in sync [1] https://developer.adobe.com/experience-cloud/cloud-manager/reference/api/#tag/Environments Use-case: enable to "automate upgrades" and across many  programs and environments (customers with up to 10 programs) - and to understand current and latest available verison. Current/Experienced Behavior: API and CLI do not provide information on * current AEM version of environment * latest available version provided for the environment * ability to execute upgrade though API/CLI Improved/Expected Behavior: API and CLI should offer the option to request * current AEM version of environment * latest available version provided for the environment *  execution of an upgrade (add upgrade flag and execute full-stack-pieline)  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):