Product ideas | Community
Skip to main content

Filter by idea status

10000+ Ideas

AJO Dynamic Content Reporting Enhancement RequestInvestigating

Currently in AJO email designer, dynamic content can be applied to different sections of the email creative. So perhaps there are a few variations of the main image, the variations are based on segments (if Segment 1, display content A1; if Segment 2, display content A2, if Segment 3, display content A3, if Segment 4, display content A4). A few different variations of the body text based on other segments (if Segment 1 or 2, display content B1; if Segment 3 or 4, display Content B2).  So as a general ask is how do we report based on dynamic content breakdown; so ideally we want to compare at both the content level as well as the segment level. So how is Segment 1 doing as compared to Segment 2 and Segment 3 and Segment 4 in terms of opens/clicks. And how is Content A1/A2/A3/A4 doing from opens and clicks comparison perspective.  So we would like to see some kind of Segment or Selection Criteria (since it could also be attribute based) + Content version both be recorded as part of the contact history logs (feedback schema).  And ideally we would like to see this kind of reporting in the AJO email reporting interface without having to going to CJA. CJA can perhaps be helpful for more custom reporting if the out of box reporting through AJO email reporting interface is not sufficient. Anybody has any comments/additional ideas about this? Thanks!

Provide the ability to dehibernate AEM Cloud Service Sandbox Environments through the Cloudmanager APINew

  Request for Feature Enhancement (RFE) Summary: I would like to be able to dehibernate my sandbox environments in a script using the Cloudmanger API (and CLI plugin). Use-case: My sandbox environments go down into hibernation daily, and once I get to development, I need to start the first, eating away 10 minutes every day.I would like to send the de-hibernation signals once i open my laptop in the morning - through a script using the Cloudmanager API or the aio cloudmanager plugin. I have tried to use the Call using from the CM-UI, but I did not get a positive response: Request URL: https://dev-console-ns-team-aem-cm-prd-n108153.ethos14-prod-deu6.dev.adobeaemcloud.com/api/releases/ns-team-aem-cm-prd-n108153/dehibernate/cm-p127553-e1403927 Path: /api/releases/ns-team-aem-cm-prd-n108153/dehibernate/cm-p127553-e1403927 Current/Experienced Behavior: Sanboxes are all hybernated, I have to spin them all up one-by-one manually. (this is very time-consuming ... and annoying!) Improved/Expected Behavior: When I open/start my laptop, the Sandboxes get dehybernated automatically through scripted calls. Environment Details (AEM version/service pack, any other specifics if applicable): AEM CloudSerices Cloudmanager (API) Customer-name/Organization name: CDA11DC661266AB70A495F8B@AdobeOrg Screenshot (if applicable):   Code package (if applicable):  

Auto remove resource managers who were deactivated or license reducedNew

Description - It would be amazing that if someone was listed as a resource manager who was deactivated or reduced to a free license would be auto removed from all projects (even templates). Why is this feature important to you - We have so many people in the system, and so many templates for different stakeholders. It is impossible to remember who is listed where all of the time to manually remove these users. This automation would reduce manual efforts and errors! How would you like the feature to work - I would like it once someone is deactivated or reduced license they should be auto-removed as a resource manager on templates at the least, but on projects would be nice too. OR, they should be removed from templates but allowed to stay on the projects and not get errors. Current Behavior - Currently what happens is that the users stay on the project and templates, so when someone goes to add a new template to a project or copy a project (and other similar actions) the person trying to do this gets an error. Many times the project owners are not in the know of all of the people who were removed in a large organization like ours. This function seems to be built for smaller companies where everyone has more insight into where users are. But a company like ours, it is impossible for many project owners to know.  THEN, many project owners do not know how and shouldn't have to fix this one by one. It seems to be such a silly flaw where the system should recognize this and auto remove these resource managers.