Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

jeff_bloomer
jeff_bloomerNew Participant

"Global Search and Replace" for SegmentsNew

Description - With as much as I work with segments used multiple times throughout a Workspace report, it would be very helpful to have the ability to select that Segment and then when I need to replace it with a NEW segment, simply perform a "global search and replace" to find the old segment anywhere it is used throughout all panels in the report and replace it with the new segment.Why is this feature important to you - The amount of time I currently have to spend moving through a large report and replacing every instance of a segment I used is very time consuming, and being able to do this would greatly reduce the amount of time it takes to update the report, particularly because it is one I use on a regular basis.How would you like the feature to work - Select the cog/gear on a segment and provide a link to change the segment.  Take the user to an interface to select a different segment and then provide them with the choice to choice one of two checkboxes: replace all instances in the panel, or replace all instances in the entire Workspace report.   Current Behavior - Presently, I have to navigate my entire report and drag the new segment over every instance I want to replace.  This takes a LOT of time, because I can often have multiple instances where I need to replace that segment or multiples throughout my report in multiple panels.  Also, the interface is not always smooth with quickly allowing me to replace a segment.  Sometimes Adobe Analytics gets finicky and only wants to provide me the option to Add in the segment as a new one, because the interface likes to be "temperamental." 🙄

Adep1Employee

Persisted Queries: Use locale param to filter the internal SQL query results in order to improve performanceInvestigating

Request for Feature Enhancement (RFE) Summary: Use locale param to filter the internal SQL query results in order to improve performance Use-case: On any multilanguage project, the same type of content fragments will be potentially created under each language. When a persisted query is executed to retrieve all the content fragments for a specific model, filtering also by dates and locale, the locale is not used on the internal SQL, causing the query to be really slow.Sample internal SQL Query: SELECT main.* FROM [dam:IndexedFragmentData] AS main WHERE ISDESCENDANTNODE(main, '/content/dam') AND main.[@string@model] = '/conf/mysite/settings/dam/cfm/models/news' AND (name() = 'master') AND ((main.[calendar@publicationDate] >= cast('2023-07-05T08:30:57.266Z' AS date) AND main.[calendar@publicationDate] <= cast('2023-07-08T08:30:57.266Z' AS date))) ORDER BY main.[jcr:path] OPTION (INDEX TAG[contentFragments], TRAVERSAL FAIL) As a workaround, we have built a new version of the persisted query where we specify the path to the specific language as a filter, then the query only takes a few milliseconds, but this should be part of the internal functionality when a locale is used, the front might know the language but not the content path. Current/Experienced Behavior: Locale is not used in the internal SQL filter Improved/Expected Behavior: Locale should be used as part of the internal SQL filter Environment Details (AEM version/service pack, any other specifics if applicable): AEM CS 2023.4 Customer-name/Organization name: Real Madrid Club de Futbol Screenshot (if applicable):   Code package (if applicable):  

Rohan_Garg
Rohan_GargNew Participant

Revamp view for Groups search in AEM Instance w.r.t listing of all non-instance based groups synced from IMSInvestigating

Request for Feature Enhancement (RFE) Summary: Currently all the product profiles group from all the instances are visible in one particular instance. If we have 3 environments and 2 run modes (author and publish) this means any particular instance like DEV Author will have 6 Product Profile groups displayed for AEM Users and AEM Administrators. Ideally this is usually not required as the Product Administrators are not interested in other groups. So the groups originating from other product profiles should either be hidden or disabled. Also, if you select any other AEM Users Product Profile Group it displays the list of members along with the option to cancel their group membership and allows you to save and proceed. (This is not allowed as if you see the product profile group again the deleted user is still present)Ideally this option to cancel membership for a user for other instance's product profile group should not be displayed. Use-case: Only the users with product profiles to a particular instance are synced. However, all the groups in IMS are synced to all the AEM instances. This leads to a confusion for a product user as one is not able to determine the instance relevant product profile group. Current/Experienced Behavior: All the Product Profile groups are displayed for all the instances in any given instance. The current product profile group should be highlighted to help narrow down your active product profile. The option to delete/cancel a user's membership to other instance's product profile group is misleading. This option should not be shown. Improved/Expected Behavior: Display only those product profile groups which are relevant to the instance. If displaying other product profile groups, remove the option in UI to cancel the group members. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS Customer-name/Organization name: TA Digital Screenshot (if applicable): Below screenshot shows AEM Users Product Profiles from RDE, DEV, Stage and Prod without highlighting which Product Profile group belongs to our current environment (RDE). The user has to take that info from the IMS Admin Console.     In RDE Instance, I am able to access AEM Users Product Profile group for Prod Environment and access the members. In UI, I am able to delete this membership for a user account. This is not allowed in backend obviously. When you refresh, the deleted user appears again. The option to cancel/delete the membership should not be shown ideally. Code package (if applicable):     @kautuk_sahni