Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Deliver email to mailable people only when sending by time zonesNew

Hello. When we use an Email Program with time-zone feature enabled, the smart list is calculated at the time of program launch / approval and the emails are sent to everyone at once. Then they are delivered by time zones even to those who has unsubscribed or has been marked as marketing suspended after the email was sent but before it was delivered (this period can be up to 24h long). The support team has advised that this behaviour is expected and as a fix we should adjust the messaging to “unsubscribe will be applied within 24 h”.  I’d like to request a feature to prevent all non-mailable people from delivering a time-zone sent email, including unsubscribed, marketing suspended, email invalid or block listed.  Reasoning:although legally we can protect ourselves with the 24h notice, this still creates a bad customer experience as often these emails are delivered just hours after the unsubscribe request. It can create a feeling of frustration and lead to reporting the sender as spam. among the suspended reasons, there are customer accounts who are going through deployment and either their customer success team or the account admin requested to pause all emails to avoid confusion among users. Delivering the email to them after the request has been processed also creates an unpleasant experience for the customer.  lastly, when setting up monitoring campaigns to review that new exclusion approach works well, we had to review a lot of cases of emails being delivered due to the time-zone functionality as we couldn’t find an easy way to exclude such emails from the report. To sum up, current state: (1) Email is sent to the calculated smart list; (2) A person on the list unsubscribes; (3) The unsubscribed person receives the email.Desired state: (1) Email is sent to the calculated smart list; (2) A person on the list unsubscribes; (3) The unsubscribed person is either marked as bounced, or pending, or some other way to mark a non-delivered email.  

MichaelSMN
MichaelSMNLevel 4

Enforce "Required" fields on custom forms before completion of a taskNew

Idea:   Enforce required fields on custom forms and do not allow a task to be completed before they are populated.      There have been several of these ideas in the past but really wanted to bring this back up in a newer idea forum as this is a huge concern coming from a highly regulated industry.    I would really anticipate that this impacts almost every organization that uses Workfront as this is really expected behavior when you indicate that a field is required.    Idea option 1:   Required * = field must be populated before status can be moved to complete. Idea option 2:  Could we potentially add an option for “Required to close” checkbox when designing a custom form field; a second required checkbox option that drives different types of required action. This would mean you could leave the current structure as is, but simply expand to enforce required nature upon the task completion trigger. Current Functionality:   If a form is not opened to edit mode, the application does not review the attached forms to confirm if fields are required or populated; it simply allows a task to close.     What happens if a field is not populated? Manual processing to locate missing information Bad user experience requiring rework Incomplete and untrusted data Automation potential issues from incomplete fields Audit and process issues Missing sleep due to concern that someone did not fill out a field that is absolutely required!  Just me? Just like all social media content creators love to say…make sure to give this a vote, subscribe and send to everyone you know to get some momentum on this!

MichaelSMN
MichaelSMNLevel 4

Notification option to let assignees know they can start working a task!New

What do we need:Create or update a user notification option that lets assignee(s) know when a task can start work!  (Can Start = True = Notification)                                        My Ask → Please Upvote this idea! There is currently not an option for users or admins to enable a notification to be sent to a user or team that is assigned to a task that lets them know that they can start working on a task; a trigger once the Can Start indicator on a task moves to True.   Users do not receive notifications that let them simply know they can start working on their task.   What’s available today in user notifications?   There is an option for “All predecessors of my tasks are completed” located in the Information about Work Assigned to Me section, but this does not always work and is not always accurate.  This runs simply off directly associated predecessors on a task.  If you manage predecessors at a parent task level, notification will not be sent to your users and affect your teams performance (e.g. Process B (parent task with multiple children tasks) cannot start until Process A is complete).  This notification will trigger only if you have a predecessor assigned to a specific task and does not account for predecessor relationships managed through a parent. Scenario 1 - No Notifications SentScenario 2 - Notifications Sent but not accurate!  

RFE – Columns block: Errors when opening Column properties + inability to move components between Columns/SectionsNew

Request for Feature Enhancement (RFE) Summary: Improve the Columns block so that (1) opening Column properties immediately after adding a Columns block does not cause errors, and (2) components inside Columns can be moved freely between Columns blocks or between Columns and Section containers. Use-case: During authoring, editors frequently add Columns blocks and adjust Column properties before placing content. They also often reorganize page layouts by moving components such as Text or Button between Columns, or between Columns and Section containers. Current/Experienced Behavior: 1. Immediately after adding a Columns block, opening the Column properties before adding any inner content results in an error. 2. Components placed inside a Columns block cannot be moved to another Columns block or to Section containers, limiting layout flexibility and forcing authors to recreate content manually. Improved/Expected Behavior: 1. Column properties should be accessible without error, even when no content has been placed inside Columns yet. 2. Components inside Columns should be draggable and movable across other Columns blocks or Section containers, enabling flexible and efficient layout adjustments. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cloud Service Customer-name/Organization name: asahi kasei Screenshot (if applicable):   Code package (if applicable):