Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

snehR
snehRNew Participant

Ability in AEM dialog to add a property that will create a child node with that name, for example for a fieldsetNew

Description - There should be a way of introducing parent child relationship in AEM component dialogs (like we can in multifield). If there are two instances of one component included in another, the ansence of such a functionality leads to a lot of duplicate code.   Usecase example is for an AEM + Angular code setup. There is a requirement to add a reusable link object/resource, that can be added to many different dialogs under different resource names "primaryCTA", "secondaryCTA", "link" nodes in Banner component, for example. It is as easy as doing a  <sly data-sly-resource="${'primaryCTA' @ resourceType='my-project/components/cta-link'}" /><sly data-sly-resource="${'secondaryCTA' @ resourceType='my-project/components/cta-link'}" /> in HTL. However, we need similar solution with Angular. A dirty way of achieving this to have following in CTA dialog: <primaryCTA jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/container"> <items jcr:primaryType="nt:unstructured"> <id jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="Link id" name="./primaryCTA/id" /> <text jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="Link text" name="./primaryCTA/text" /> <href jcr:primaryType="nt:unstructured" fieldLabel="HREF Link URL" sling:resourceType="granite/ui/components/coral/foundation/form/pathfield" rootPath="/content/" name="./primaryCTA/href" /> </items></primaryCTA><secondaryCTA jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/container"> <items jcr:primaryType="nt:unstructured"> <id jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="Link id" name="./secondaryCTA/id" /> <text jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="Link text" name="./secondaryCTA/text" /> <href jcr:primaryType="nt:unstructured" fieldLabel="HREF Link URL" sling:resourceType="granite/ui/components/coral/foundation/form/pathfield" rootPath="/content/" name="./secondaryCTA/href" /> </items></primaryCTA>  and include it in parent Banner component dialog: <primaryCTA jcr:primaryType="nt:unstructured" jcr:title="Primary CTA" granite:class="field-group-border" sling:resourceType="granite/ui/components/coral/foundation/form/fieldset"> <items jcr:primaryType="nt:unstructured"> <primaryCTA jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/include" path="my-project/components/cta-link/items/primaryCTA" /> </items></primaryCTA><secondaryCTA jcr:primaryType="nt:unstructured" jcr:title="Secondary CTA" granite:class="field-group-border" sling:resourceType="granite/ui/components/coral/foundation/form/fieldset"> <items jcr:primaryType="nt:unstructured"> <secondaryCTA jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/include" path="my-project/components/cta-link/items/secondaryCTA" /> </items></secondaryCTA> But this means duplication of code and not following DRY principles. Also we'd need a dialog for each different name. We need to have a clean way of introducing a node parent on CTA so we can avoid the duplicate code within CTA dialog.   Why is this feature important to you - Clean code and avoids duplicate code   How would you like the feature to work - Through AEM component dialogs with JS libraries and frameworks like Angular and React   Current Behaviour - The feature does not exist

user00169New Participant

dymanic filtering/segmentationNew

Description - In Workspace, be able to create a filter or segment where the items in the dropdown are populated dynamically based on items that received traffic during the selected time period. For example, a browser version dropdown where you could filter a report based on browser versions that received traffic during the selected time period. Then, as browsers are updated and new versions are introduced, the dropdown would automatically contain the newly released browser version number once you received traffic from it. Why is this feature important to you - We receive Company Name info from Demandbase. I want to have a filter/segment where someone can choose a company name and see what that company did on our website. Right now all I can do is drag and drop thousands of company names into a segment, and even then, if we didn't receive traffic from a company during that period, then that company will not be an option within the dropdown. How would you like the feature to work - You actually have this feature sort of today within the Quick Insights panel. There's an Analyze dropdown within it, and one of the dimensions I can choose is Company Name, and then I can expand that out to show company names. But I don't just want it in the Quick Insights panel, I want it in other panels, and without all of the other dimensions, just Company Name.Current Behaviour - manual creation of up to thousands of items in a dropdown

snehR
snehRNew Participant

Ability in AEM dialog to add a property that will create a child node with that name, for example for a fieldsetNew

Description -There should be a way of introducing parent child relationship in AEM component dialogs (like we can in multifield). If there are two instances of one component included in another, the ansence of such a functionality leads to a lot of duplicate code. Usecase example is for an AEM + Angular code setup. There is a requirement to add a reusable link object/resource, that can be added to many different dialogs under different resource names "primaryCTA", "secondaryCTA", "link" nodes in Banner component, for example.It is as easy as doing a <sly data-sly-resource="${'primaryCTA' @ resourceType='my-project/components/cta-link'}" /><sly data-sly-resource="${'secondaryCTA' @ resourceType='my-project/components/cta-link'}" />in HTL. However, we need similar solution with Angular.A dirty way of achieving this to have following in CTA dialog:<primaryCTA jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/container"> <items jcr:primaryType="nt:unstructured"> <id jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="Link id" name="./primaryCTA/id" /> <text jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="Link text" name="./primaryCTA/text" /> <href jcr:primaryType="nt:unstructured" fieldLabel="HREF Link URL" sling:resourceType="granite/ui/components/coral/foundation/form/pathfield" rootPath="/content/" name="./primaryCTA/href" /> </items></primaryCTA><secondaryCTA jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/container"> <items jcr:primaryType="nt:unstructured"> <id jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="Link id" name="./secondaryCTA/id" /> <text jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/form/textfield" fieldLabel="Link text" name="./secondaryCTA/text" /> <href jcr:primaryType="nt:unstructured" fieldLabel="HREF Link URL" sling:resourceType="granite/ui/components/coral/foundation/form/pathfield" rootPath="/content/" name="./secondaryCTA/href" /> </items></primaryCTA> and include it in parent Banner component dialog:<primaryCTA jcr:primaryType="nt:unstructured" jcr:title="Primary CTA" granite:class="field-group-border" sling:resourceType="granite/ui/components/coral/foundation/form/fieldset"> <items jcr:primaryType="nt:unstructured"> <primaryCTA jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/include" path="my-project/components/cta-link/items/primaryCTA" /> </items></primaryCTA><secondaryCTA jcr:primaryType="nt:unstructured" jcr:title="Secondary CTA" granite:class="field-group-border" sling:resourceType="granite/ui/components/coral/foundation/form/fieldset"> <items jcr:primaryType="nt:unstructured"> <secondaryCTA jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/coral/foundation/include" path="my-project/components/cta-link/items/secondaryCTA" /> </items></secondaryCTA>But this means duplication of code and not following DRY principles. Also we'd need a dialog for each different name.We need to have a clean way of introducing a node parent on CTA so we can avoid the duplicate code within CTA dialog. Why is this feature important to you -Clean code and avoids duplicate code How would you like the feature to work -Through AEM component dialogs with JS libraries and frameworks like Angular and React Current Behaviour -The feature does not exist

LionelThEmployee

Deliverability monitoring (canal email)New

Description -An essential information that is currently missing is to be able to monitor the performance of emails by recipient domain.Current reports show performance delivery by delivery (and the list of domains can be customized via the "domain" enumeration).It would be very interesting to have the performances on these domains per day of sending (volume sent, success, number of distinct openings, number of distinct clicks, success rate, distinct open rate, distinct click rate, reactivity rate) with curves showing a history over X days.The calculation of these indicators could consume some resources but the storage of information should be not very voluminous.Why is this feature important to you -For marketing departments, it is essential that they can monitor their deliverability. I have many examples of clients asking me how they can follow it and I have nothing to offer them.How would you like the feature to work -The list of monitored domains must be based on the existing "domain" enumeration.There should be a deliverability section (ex : Home->Deliverability) presenting :- a table showing 1 recipient domain per row, and in column the aggregated data of a day (by default: D-1): volume sent, success, number of distinct openings, number of distinct clicks, success rate, distinct open rate, distinct click rate, reactivity rate.With a control allowing you to select the day to display.- 1 graph per type of data (listed above) with a header list of domains to display on all these graphs (with a checkbox for each) and a drop-down list to choose the period to display.For all graphs displaying volumetry, the scale must be adapted to the strongest volume represented.Thus, for example, the customer will be able to see the evolution of his performance on his Gmail mailings and be able to identify a potential problem.Current Behaviour -None.