Build better products with our product team
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.
We need a way to create recurring tasks that have a pre-set the duration AND planned hours. You can do duration in "simple" mode and planned hours in "Effort driven" mode, but there isn't a way to create multiple tasks at the same time with both set duration & planned hours-- they come up blank (simple) or you can't change them (effort driven).
The functionality for setting up recurring tasks initially is easy to understand and set up, but the way the tasks are labeled is a chore. If I have a user who processes DCM tickets every day, I end up having them look like this: DCM Tickets 1DCM Tickets 2DCM Tickets 3 In a user report, the task names above are not helpful. Would it be possible to use the date guidelines set to create some sort of naming convention? I am basically looking for overall improvement in how recurring tasks are executed in the system.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK