Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

Jennifer_Dungan
Jennifer_DunganNew Participant

Improvements to Scheduled Project Area (More Info about Last/Next Send datetime, bulk re-send, better inter-linkage with Workspace interface)New

DescriptionToday I received multiple reports from people in my organization complaining that they didn't get their weekly reports mailed to them. It seems that there was an issue listed in the status system which likely caused the issue.  Now, at this point you are thinking this is more of a complaint about the failure... it's not.... what comes next relates directly to improvements that would make all our lives easier. When I checked my Scheduled Projects area... I noticed a few things...there is nothing in my "failed" filter (I assume this is because this relates to flat out failures, not temporary failures?)There is no way to see the "last sent" date/timeThere is no way to tell if the reports are delayed (and will send once the queue catches up) or or today's report failed completelyThere is no way to re-send reports from this interface (an no link to the reports) - so if I need to resend 30 reports, I have to go and find them all individually and send them one at a time To Improve this tool significantly, there should be a way to:Have a column showing the last date/time the report was sent successfully (this will help identify which reports failed)Have a column showing the next data/time the report should be sent (this will help identify IF the report is just delayed, or outright failied)Allow us to select multiple reports using the checkbox selectors, and have an option at the top (along with tag, delete, approve and export to csv) to "resend selected" (this will allow us to bulk resend failed reports easierProvide a way to link directly to the report (for editing), this could possibly show up in the popup window where you can edit the schedule.. but it would improve our ability to find specific reports easier when starting from the scheduler) (on that note, it would also be nice to see links to all the existing schedules/ability to edit your own schedule from the Workspace interface - I still have users who create multiple schedules, but don't have access rights to the Scheduled Reports area, so I have to clean it up for them - not realizing they created multiple schedules)  Why is this feature important to youIt will provide much needed optimization to working with scheduled reports.. More visibility into items that failed / were delayed.. better functionality to resend failed items, and better cross functionality between building/editing reports and editing schedules.  How would you like the feature to workSome features would be pure data, showing in the columns of the Scheduled Project interface... they don't even have to be turned on by default... they can be hidden unless shown by using the Config Columns. Some would be a new functionality to force report re-sends (for one or more items - an important bulk management feature) The last would be improvements on interlinking the Workspace Interface with the Scheduler interface, this would be the hardest to achieve, but would improve visibility, usability and workflows significantly.  Current BehaviourTechnically these would all add on to existing behaviour, and that wouldn't change... these are all net new features.

jaspotterNew Participant

Add additional attribute in the Adobe IO Event Payload for an AEM Page Publish event with the "Destination" information (Publish vs Preview environments)New

Request for Feature Enhancement (RFE) Summary: In AEM we have an out-of-box capability to have AEM OSGI Events sent to Adobe IO: https://developer.adobe.com/events/docs/guides/using/aem/ https://github.com/adobe/aio-lib-java/tree/main/aem/aio_aem_events/src/cs/content/jcr_root/apps/aio-aem-events/osgiconfig/config.author One of these OSGI events is for the Page Publish event in which we can have an external webhook notified when this event in AEM occurs. Additionally we have the Managed Publication feature which allows for content authors to publish a page to a "Destination" such as the Publisher environment or a Preview environment. In my use case I have an external webhook configured to receive Page Publish event. In my test I used the Managed Publication feature to publish the same page first with the "Publish" destination and then again with the "Preview" destination. In both cases my external webhook is receiving the event properly, however the Adobe IO event payload between these two are identical and there is no way to distinguish which environment the page was being published to. I'm proposing that an additional attribute be added to the Adobe IO event body for the Page Publish event which would identify which "Destination" was selected if a content author uses the Managed Publication feature in AEM. The value could perhaps be the value "publish" or "preview" depending on what the author selected, or maybe even the fully qualified URL of the publisher or preview environment in the event body. Based on this attribute in the Adobe IO event payload my external webhook URL I would be able to add additional business logic to treat these two publish events differently based on the "Destination" that was used. Use-case: By having an additional attribute in the Adobe IO event payload we could have an external webhook have additional business logic to handle the "Publish" and "Preview" destination differently.  In my case I have content that I am hosting on AWS and would like to know if an author as published a page to the publish environment or the preview environment to separate them. Current/Experienced Behavior: Currently the Adobe IO AEM page publish event payload sent to the webhook is identical between publishing to publish and preview environments and no way to distinguish the two. Improved/Expected Behavior: By having an additional attribute in the Adobe IO event payload that an author had selected using the Managed Publication feature in AEM my webhook would be able to treat the two page publish events differently by knowing the page to the publisher or preview environment. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Service / Adobe IO  Customer-name/Organization name: Coca-Cola Screenshot (if applicable): Code package (if applicable):