Build better products with our product team
I would love to be able to filter a time off calendar on any team, rather than just on home team. We are an agency and our users are on many client “teams”, and sometimes a project manager may want to see all of the users that are out on a given client team rather than a given home team.
We have one app and several web properties tracked in abobe analytics. We use the LiveStream API to push our app and web data into an external repo. Mobile App ID is, in my opinion, the easiest and quickest way to segment out traffic to/within the app from the web properties.But Mobile App ID is not one of the fields sent in the Livestream API! Please do the engineering work to change that and include mobileappID in the livestream. You may be saying to yourself, now why don’t you just track them in separate report suites.. great question! I didn’t make the decision to combine them in the same suite - that predates my time here.
When exporting a large number of records with a large number of fields, Marketo will often complete the export, with a UI confirmation, but the download will not work. This appears to be a silent failure of the “download now” button. Sometimes large exports download without issue, and other times they don’t download, no matter how long you wait. The UI should provide an error or otherwise indicate when a download can be completed successfully.
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.
In all Sandboxes, prod and test, we sometimes need to clean up the environment. Meaning f ex deleting old Journeys, not used Journeys and Journeys used for testing. Today it is only possible to delete Journeys one by one. It would be better if there where a option where you could select several Journeys and batch delete them with one click. Deleting one by one seems unnecessary and time consuming.
Description - Once an issue has been approved, we convert it into a project, and I would like to lock the comments (updates section) in my issues (nobody can enter a new comment) once it has a resolving project related to it. Why is this feature important to you - once the issue is approved, we follo up everything in the converted project but many time requestor does not know and he/she comment in the issue instead of the project this causes confusion in the Requestor because, he does not know that the latest updates are in the project or the executor do not see the comments because He is now working in the project. It results in lost the conversation chain and often gets missed. How would you like the feature to work - A feature where it detects the issue has a resolving project and lock any new comment. Current behaviour - only technical method to achieve this is by revoking users' sharing permissions from the issues. Yet, this action would result in users being unable to view or access the issue unless they possess system administrator privileges. We still need Requestor has access to the issue, but he should not be able to modify or comment it.
The Problem: Displaying inactive users creates a poor user experience when trying to confirm if object is shared or not. Currently, active users are mixed alphabetically with "No Access" or inactive users, forcing our team to scroll excessively and manually click the "X" to clean up share list. This manual maintenance is a time-sink, diverting our team from their primary goal: supporting our customers.Requested Enhancements: Collapsible or Hide "No Access" View: implement a collapsible section for users with no access, similar to how inherited permissions are handled. Users should have the "choice" to expand this list via a toggle (>) only when needed. Automated Team Offboarding: way to automate the removal of inactive users from Teams. Currently we either have to have team owner go and remove or our ops team need to go into the user and X all the teams they are tied to. Again takes away from our doing our day to day jobs. The Goal: Minimize administrative overhead so our team can focus on customer-facing tasks rather than manual permission management.
I’d like to share feedback regarding the new Feeds UI, as the current default behavior is creating significant usability issues.Right now, the report suite filter defaults to a state where none of the report suites are selected. Because of this, users must manually select every report suite before they can see any feeds. For organizations with a large number of report suites, this becomes extremely time-consuming and makes the interface difficult to use.Ideally, the default behavior should either:- Show feeds for all report suites by default, or- Provide a more practical filtering option, such as filtering by active feeds.The current setup adds unnecessary steps to a workflow that used to be much more efficient and makes managing feeds considerably harder for teams with many report suites.Please consider revisiting the default filtering behavior to improve usability and reduce friction when accessing feeds.
現在、Marketoの標準機能ではSFDC同期時に発生する特定のエラーメッセージ(例:CANNOT_UPDATE_CONVERTED_LEAD など)を直接検知してトリガー(自動通知)に利用することができません。そのため、スマートキャンペーンの「実行結果」タブを定期的に手動確認するかエラー対象を個別に確認・対応するといった運用が必要となり、件数が多い場合は対応工数が大きくなっています。 以下のような機能追加をご検討いただけないでしょうか。 SFDC同期エラー内容(エラーメッセージ/エラーコード)を条件として検知できる仕組み スマートキャンペーンや通知トリガーで使用できる 特定エラー発生時に自動通知が可能になる 同期エラー対象レコードを一括抽出(エクスポート)できる機能 修正後、再アップロード(インポート)することで一括更新できる仕組み 同様の課題を抱えているユーザーも多いと考えられるため、将来の製品改善としてぜひご検討いただけますと幸いです。
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!
Capping Business rules in Admin section is only applied for the highest-priority identity namespace. We have few identities with our Hybrid data modal and would like an option to be align capping with the selected identity.
I wanted to suggest an improvement regarding how we handle delegated issues in Workfront. As it stands, unless a delegate user takes ownership of a project, the delegated issue will only appear in their "my work" widget. This setup isn't quite streamlined enough for our needs. Could we request to have Workfront include delegated tasks in the "my task" widget as well? This adjustment would provide a more cohesive and efficient view, allowing us to better track and manage our responsibilities. Thank you for considering this suggestion. Looking forward to your thoughts on this matter.
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!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.