Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Expose Resource Availability Data Through the Workfront MCP ServerNew

SummaryOur team uses Claude connected to the Workfront MCP server to answer resourcing questions in natural language. Planned Hours are fully and reliably queryable today. Remaining Available Hours — the metric the Resource Planner itself calculates (schedule capacity minus time off minus existing commitments) — is not exposed through any MCP tool, and cannot be reliably reconstructed from what is exposed. We're requesting this data be made queryable so a team's full capacity picture (Planned + Available) can be surfaced through natural-language requests, not only through the Resource Planner UI.What Works TodayPlanned Hours are cleanly queryable via the insights_find_workfront_data tool, using fields such as assignment.assignment_workRequired and task-level planned hours, grouped or filtered by user, project, or date range. This lets Claude answer questions like "how many planned hours does each person on this team have this month" accurately and immediately.The GapThe Resource Planner's own Available Hours (AVL) value — schedule capacity minus time off minus hours already budgeted across all of a user's projects — is not exposed as a field through insights_search_fields or any other MCP tool we've found. The raw inputs needed to approximate it are also incomplete: user.user_workHoursPerDay and schedule.schedule_hasNonWorkDays are queryable, but time off is only exposed as a boolean flag (user.user_hasReservedTimes), not as actual date ranges or hours. There is no queryable list of a user's specific time-off periods or schedule exceptions. As a result, Claude cannot reliably reconstruct "remaining availability" even by combining multiple queries — any approximation would overstate availability for anyone with time off on the books, since those dates aren't visible to any tool.What We're RequestingPreferred: expose the Resource Planner's calculated Available Hours (AVL) value itself as a queryable field — per user, role, or project, scoped by date range — mirroring what already displays in the Resource Planner UI. Minimum viable alternative: expose the underlying time-off / schedule exception data (specific dates and hours per user) as queryable fields, so Available Hours can be reliably approximated by combining it with the Planned Hours data that is already accessible.Why This MattersCapacity planning conversations need both halves of the picture — what's already committed, and what's actually left. Today, getting the Available Hours half requires manually opening the Resource Planner and checking user-by-user, project-by-project, which doesn't scale and can't be surfaced through natural-language tools like Claude. Closing this gap would let our team ask capacity questions the same way we already ask planned-hours questions — directly, without a manual UI detour.

Section Headers & Table Of Contents - Possible ways to improveNew

Both the Section Headers and Table Of Contents have been good additions for making reports easier to read and navigate through - though have got a couple of thoughts on how they might be able to be improved further. 1) Add the full set of right-click functionality to Section Headers - At present, the only way that the Section Header visual can be interacted with is changing the text; the right-click menu that exists with other visualisation types isn’t there. However, I think it would be good to change this for two main reasons. ‘Edit description’ - This could be used to enable the adding of a short description or subtitle, between the main title and the line underneath the visualisation. ‘Get visualisation link’ - It would be good to be able to link directly to a Section Header. As a user who often adds an Introduction or Contents section to tell users what they can find in a report, it’s nice to add links in, but currently you have to link to any other visual that’s close to the Section Header instead. Although doing this ‘Contents’ part does overlap with the Table Of Contents feature, I find a) many more ‘casual’ users are still unaware it exists, and b) this written text is far easier to quickly understand due to the next point… This right-click menu exists on other visualisation types, but not Section Header. Distinguish Section Headers in the Table Of Contents - In the below image of the Table Of Contents on the left, you can’t instantly see which lines are Section Headers. As a result it’s a lot more tricky to find what you’re looking for and understand what’s in the panel. Some possible changes (as per the right) that could improve this may be adding bold text to Section Headers, indenting any text that isn’t a Section Header, or even adding in icons to distinguish the visualisation type next to each line. At the moment I often find myself adding colons to the text of these visuals only, or adding extra Section Headers with ‘-’ as the title to create a space, as something of a workaround to get them to be somewhat visually identifiable. The left image shows how the current Table Of Contents displays, while the right image shows how this could look using bold text for Section Headers or indented text for other visuals. With these changes though, hopefully it would make dashboards easier to read and navigate. 

新しいEメールデザイナと旧EメールエディタのAPIについてNew

Marketoのメールアセット一覧とメールコンテンツ取得に関して、現在の検証結果として下記だが、v2仕様は公開情報となっていない。また、メールアセット一覧取得に関して、v1で旧エディタでの作成分と新エディタ作成分(ただしレスポンス内容の不足あり)という状況だが、この状態が正式仕様となるのかも公開情報となっていない。 APIを利用したシステム構築を行ううえで正式な仕様情報がなく、設計が困難なため早期に仕様の確定および公式情報として公開を頂きたい。 《検証結果》■メールアセット一覧取得 v1:旧エディタに加え、新エディタで作成したアセットも取得可能。ただし新エディタ分は、一部Subjectが含まれないなどレスポンス内容に不足が見受けられます。   (https://developer.adobe.com/marketo-apis/api/asset#operation/getEmailUsingGET) v2:新エディタで作成したアセットのみ取得可能。   (https://developer.adobe.com/marketo-apis/api/asset#operation/filterContentUsingGET_email)■メールコンテンツ取得 v1:旧エディタ作成メールのみ取得可能   (https://developer.adobe.com/marketo-apis/api/asset#operation/getEmailFullContentUsingGET) v2:新エディタ作成メールのみ取得可能   (https://developer.adobe.com/marketo-apis/api/asset#operation/getContentUsingGET_email)

tamaruLevel 1

Request for product feature improvements regarding asset uploadsNew

Request for Feature Enhancement (RFE) Summary:​ <Issue> An issue occurred where the publishing operation failed on the holding company's corporate website. <Cause> The cause was that a file uploaded to Assets did not comply with the naming conventions. However, the current version of AEM Assets allows files that do not adhere to naming conventions to be uploaded without displaying any error messages or warnings. <Request for Improvement> We would like a feature that checks file naming conventions during upload, displays an error or warning for non-compliant files, and controls the upload process. We believe this will help prevent issues upon publication and reduce the operational workload. Use-case:​ A specification that checks naming conventions during file upload, displays an error or warning for non-compliant files, and controls the upload process. Current/Experienced Behavior:​ With the current version of AEM Assets, it is possible to upload files with names that do not comply with naming conventions, and no error messages or warnings are displayed when doing so. Improved/Expected Behavior:​ We would like a feature that checks file naming conventions during upload, displays an error or warning for non-compliant files, and allows for control over the upload process. We believe this will help prevent issues upon publication and reduce the operational burden. Environment Details (AEM version/service pack, any other specifics if applicable):​ asahi-kasei-corporation-program-prod Customer-name/Organization name:​ Asahi Kasei Corporation Screenshot (if applicable):​ Code package (if applicable):​

ncdd23Level 2

Autosave/Drafts for Requests being Created within a ProjectNew

Description - After a thorough implementation, we decided to use the Request Queues built directly in the projects. The functionality is great. We have a project template set up with Queue Topics, Groups, Forms etc. The issue is that when creating requests directly in a project there is no Autosave or Drafting functionality that we know of. Our users are becoming increasingly agitated by having complex requests easily deleted at the unfortunate click out of the request window or accidental refresh of the page.   Why is this feature SO VERY important to you - Our current solution is to submit requests without auto-routing to a traffic team so the work can be saved. Leading to needing to save as you go, something that is antiquated in this day and age, especially knowing that autosave exists in many other places in Workfront, including the Global Request Queues area.   How would you like the feature to work - simply autosave as you go with a Drafts section built into the Request area of the Project. Or a new section called Request Drafts. Draft autosaves until the Submit Request button is clicked.    Current Behaviour - User begins a request, fills out info and has to Submit the Request in order to save it and continue working on the request, and they must click save as they progress. If users haven't submitted the request yet or haven't recently saved, it is very common for users to accidentally click out of the window, closing the request and clearing all the info. Leading them to have to painstakingly recreate the request they could have spent many hours on.   Please prioritize this, WF.