Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

DasariVidyasagarReddyNew Participant

Deleting a Page : Need an option to update Link references of the deleted pageInvestigating

Request for Feature Enhancement (RFE) Summary: Deleting a Page : Need an option to update Link references of the deleted page Use-case:  Content author Deleting a page. Current/Experienced Behavior: When content author deletes a page from AEM then the deleted page link references don't get removed in the Site core and There is no option to redirect the references to a new page or completely delete the references(hyperlinks). Improved/Expected Behavior:  When we try to delete a page then it gives us the three options ·         link to another item (if the page being deleted has been                     hyperlinked somewhere then it will redirect the deleting                page URL to new location before deleting) ·         To remove the references if the page is hyperlinked                        anywhere on the site ·         Leave links – the links will appear in the Broken Links report Environment Details (AEM version/service pack, any other specifics if applicable):  AEM 6.5 Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

Mylah_DNew Participant

Dynamic Dropdown or Typeahead fields on Custom FormsDelivered

Custom Forms: Custom fields populated from lookup of (internal/external) data sourceIt would greatly enhance usability for both admins and general users if it were possible to create a Typeahead or Dropdown lists that reference internal-to-Workront sources (i.e. csv file uploaded as a Document? an admin-controlled table?) or external data source like gSheet or database. When the user chooses a value from a custom field from multi-choice options presented, the selected value should be used to start a query that looks up related values and returns them in either read-only fields or to another field presenting a subset of list of options (e.g. dropdown or typeahead) Example 1 - Read Only fields returned: If you have a Typeahead field on a form called "State". User types in string "CA" and the field looks up the external datasource column for State to populate typeahead suggestions User Gets typeahead suggestions of "California", "N. Carolina", "S. Carolina"... & selects "California". This executes a query to a "geo" database using California as search parameter to return the related values for Country and Continent. The following 3 fields are populated on the form: State: CaliforniaCountry: USAContinent: N. AmericaExample 2: Custom Dropdown list gets narrowed down by a selection in a previous custom fieldUser chooses from one dropdown list called "Color Family" the value BlueIn a subsequent dropdown list that contains a super-set of all colors, only the following values are presented as options:SkyAzureTealNavyCeruleanCobaltTurquoiseetc... In other words, when presenting dropdown list values, the list would dynamically suppress any values in the big list that aren't associated with the Color Family, Blue. The relationships between color families and colors would be defined in some table internal or external to Workfront.

K6ivupuuNew Participant

Segmenting with list evar occurrencesNew

Description  My use case:I need to segment and select values for only some of our internal marketing ID's (let's say my "wanted" list involves ID's "A", "B" and "C" and my filter is therefore: "equals any of A, B, C"). The filter however will also include ID's that are not in my wanted list (for example "D"), meaning in a built view in my workspace I will see values for A, B, C and D. Cause: This happens because in our implementation, for some cases the same hit triggers several ID's together (in business terms - we are showing several marketing objects simultaneously). For example one hit would have the ID "A" and simultaneously also "D". (I.e. a list evar then has both values)Result: This means my segment returns ID's and values for both, "A, D" and any table I build in an Analytics workspace will have the unwanted values appear as well. Alternatively phrased - a list evar can not be segmented in such a way. Note. There is a solution - I can manually filter them out, but this is manual work and if any of our stakeholder tries to replicate, this creates confusion and questions.Want. I want to be able to build a segment that would understand list variables and not include values that are not in my "wanted" list. Why is this feature important to youTry explaining to a non-analyst Adobe Analytics user, why a custom built segment is not segmenting and values are being shown that should be excluded. Indeed, there is a manual approach, but it has it's own downsides. In the examples that I provide, to illustrate the point, I am using one request examples and as such might not make sense in aggregated perspective. So keep in mind that a large site with a lot of different marketing placements appearing in many different combinations (A with B, A with C, C with X) and thus when you only want data for a particular ID, the current solution will create a lot of data noise.  How would you like the feature to workOn example of a single request. When I build a segment that checks against a list evar in a single occurrence, and the list evar contains ID's "A", "X" and "Z", and I want to return only values (let's say we talk view counts) for "A" in my table/view -  the segment should be able to understand the list variable and selectively return values (view counts) for "A" only and not include values for "X" and whatever else. TLDR: Built segments should understand the elements on the list evar and return wanted values only. Current BehaviourAny segment built to filter list variables, doesn't understand to return values only for the elements in built segments.