Description - The current ACS APIs available does not provide a way to fetch the deliveries and workflows informationWhy is this feature important to you -1. There are some features like heat map which is available in ACC but not in ACS and it can be built if the workflows execution information can be fetched through API in Firefly project but the API isn't available2. Currently in ACS there's not quite a lot flexibility in terms of what information can be displayed (limited to available dimensions) on Dynamic Reports. A lot of times it's needed to generate a custom report about the deliveries like number of sent, delivered, bounced, opened, clicked messages, etc. and display that on the UI outside ACS similar to dynamic reports. There isn't any API related to Deliveries.How would you like the feature to work - Exposing Deliveries and Workflows data via APICurrent Behaviour - API does not exist for workflows and deliveries.
Content Fragments are now used widely in AEM project majorly in headless and hybrid model. But still there are some features that can be added in content fragment that can make it more valuable:1) Use of Multifield. Currently the multifield works fine when there is one level of child but for some cases we require multlevel multi field that does not work fine as it works in the component level.2) Live Copy Inheritance in Content Fragment is not supported.3) Asset level versioning shows the version number , it should also show the date of version so this will help to track the exact revision as well.4) Dialog level clientlibs instead of override dam.cq one for dialog level events.
Hi,A nice feature to implement will be a standard "trash-bin" functionality for AEM Assets. Right now we have customization (implemented on AEM 6.3) as described herehttps://kbwebconsult.com/2020/07/21/the-enigma-of-aem-apache-sling-filters/ Best,Krass
As different client has different data archival standards, we need to create archival process for various clients. In AEM, since the content goes into the repository, anything that comes inside the repo becomes a data that is moved across environments. Moreover, we need to have a process for content editors for moving archived content to some other tree or space and to keeping the content tree clean and only with needed content. It will be great if you can support an archival strategy OOTB. The features I look for in this feature is1. Easy to manage from authoring experience2. Reduced to a small size3. It should be outside the repository so that we don't need to move that as content in the repo.4. We should be able to search through the metadata5. We should be able to retrieve the content with some action.
I would like to have a report to show how many forms are using 1.0. With the depreciation of forms 1.0, it would be great to be able to see how many forms are 1.0 in an instance. To be able to create a smart list or a report would help.
It would be great if you could set up Smart List Subscriptions to send on a specific date and at a certain time of day.
It would be marvelous to have the ability to create an email message that is specific to one project's tasks (not system-wide events, reminders, or notifications) that is sent to new task assignees.Use case: Our Member Experience (MXP) team reviews member surveys and forwards them on to supervisors all over the organization for additional follow up and collaboration. Each week, MXP Analysts are tracking hundreds of these survey reviews in an Excel spreadsheet, sending an Outlook template email to the necessary supervisors, and collaborating with the supervisors via email. The assignment, tracking, collaboration, and reporting are all disparate and there is no clear visibility even just in the MXP Analyst team.Our thought was to have the MXP Analysts enter a task for the supervisor's review, which would generate a customized email upon assignment (provides unique guidance and input specific to those tasks only), and have the supervisors reply to the email with updates so the Status Updates become the place of collaboration. We would not want to change the global, system-wide settings, just task assignment emails on one particular project.
In order to send a rich push, such as including a JPEG or video file in a push, you need to host the asset internally and place the image path URL into the ACS push campaign. This creates extra steps and requires the user to have a CMS of some sort to host the images you want. ACS should allow users to upload images and video assets into ACS to host for rich push.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.