Build better products with our product team
Description - Allow hours to be allocated by day, week, month in the allocations of the unassigned hours space in the workload balancer on job role assignments.Why is this feature important to you - Our resource managers need to manage upcoming time that could have tasks with hours that vary by day that need to be marked out on a job role for future assignment.How would you like the feature to work - Just as the assigned area can we have the hours in monthly, daily, weekly view to be able to be edited by doubleclicking or by clicking the three-dot menu and clicking edit allocationsCurrent Behaviour -Currently you can only assign job roles and put total planned hours in, the system will average the time but will not allow you to edit the daily allocations.
Description - The auto collection logic for xdm.timestamp field in the AEP SDK is currently dependent on the user’s local system time. This reliance on system time creates inconsistencies in event tracking and reporting (event timestamps show up way in past or future at times which means they are offset as compared to actual event time). This improvement proposes syncing the xdm.timestamp field to a centralized server-side clock, such as UTC, ensuring uniformity and accuracy in time data.Why is this feature important to you - Accurate and consistent timestamps are crucial for reliable event tracking, analytics, and reporting. Without this feature, data may be skewed due to discrepancies in user device clocks, clock skew or drift, or manual adjustments to system time. This impacts the quality of insights derived from event data. By syncing the timestamp to a server-side clock, the platform ensures more reliable and consistent data, making it easier to correlate events, generate accurate reports, and analyze user behavior.How would you like the feature to work - The xdm.timestamp field should automatically be synced to a server-side clock (e.g., UTC) at the point when an event is logged, regardless of the user's local system time. The SDK should request the server time whenever an event is triggered, and the server will provide an accurate timestamp to be used instead of the device’s local time.In the event of network issues or server downtime, a fallback mechanism could use the local system time to avoid event loss, but with clear flagging of the fallback event for potential time data issues.The feature should be seamless and require no additional action from the user or client-side developers once integrated into the SDK.Current Behaviour - The xdm.timestamp field relies on the local system time of the user's device. This results in discrepancies for reasons like if a user changes the time on their device manually or if there are differences in system clock accuracy. This can lead to inconsistencies in event timing, causing difficulties in correlating data, performing time-based analysis, and generating accurate reports.
This would be helpful to copy a web property from one Launch company to another Launch company in Experience Cloud with different IMS Org Ids.
Be able to set a status in the approval process so that when the project task or issue is approved the predefined status is set.
Description - We have some requests that come in with a lot of documents attached. Many times it's 1-2 but can be up to 20 and the user isn't savvy enough to create a .zip file. The issue is further compounded when we find an error in the documents (i,e. requester uses the wrong logo and all of them need to be redone. Why is this feature important to you - it would increase efficiencies for both the requester and the team working on the request as the documents would need to be viewed one at a time or reviewed to remove duplicates or version after the fact. ASide from reading the whole list and looking at the date uploaded, there's no easy way to clean the files up so the current version is used. How would you like the feature to work - It would be a great feature to provide an error/flag message to the person uploading when the file they are uploading is already in the Documents Section asking them if they want to replace it (automatically creating a new version on top of the old) or provide instructions to drag/drop the new version over the top. Current Behaviour - Massive list of files only in the Document section
Description: The current process of uploading IP BOT rules is manual and repetitive. When updating multiple report suites, each suite must be selected individually. An API or tool that allows for the bulk upload of the latest IP BOT rules to all report suites would save a significant amount of time.Why is this feature important: The current process is both manual and redundant. Even using the 'Control' button to select multiple report suites is time-consuming. A more efficient method for bulk uploads would greatly reduce the time required.How the feature should work: We should be able to add all the latest IPs to the BOT file and then have an option to update all the report suites within the organization.Current Behaviour: The BOT rules must be manually selected and uploaded for each report suite.
DescriptionI would like to be able to choose one or several attributes as Journey Exit Criteria. Why is this feature important to youThis feature is important because I don't necessarily want to create more audiences since it takes more time to do that and I'm also concerned about the audience guardrails.I don't want to have to create a custom event since it's more time consuming and requires different roles/competence/AJO permissions to do. How would you like the feature to workI would like to use attribute as exit criteria by using operators to either say that the attribute should equal a defined value or be more/less than a defined value or be compared to another attribute or to a certain date or time. Also, being able to say that if a profile's attribute changes in any way from the time the profile enters the journey, then the profile should exit the journey.
機能改善要求（RFE）概要： twitter:cardを指定できる機能の追加 ユースケース： X (twitter)で情報を拡散させる際、OGP画像を大きく表示させたい（summary_large_imageを指定したい） 現在／体験した動作： og:imageの画像が表示され、画像が小さく、目立たない 改善／期待される動作： summary_large_imageを指定することにより、画像が大きく表示され、情報拡散に有利 環境の詳細（AEM バージョン／サービスパック、もしあればその他の詳細）： 顧客名／組織名 Maki_yam スクリーンショット（ある場合） コードパッケージ（ある場合）
Request for Feature Enhancement (RFE) Summary: Accurate header/footer and breadcrumb display in page version comparisons Use-case: Comparative display of past and current versions of a page / preview of past versions Current/Experienced Behavior: Header and Footer not displayed. The breadcrumb list is displayed in full path. If this requirement is not met, it is difficult to see what has changed compared to the previous version, which hinders the content update process.Although the function compares differences, the problem is that differences are produced even if the content has not been updated. Improved/Expected Behavior: Headers and footers are displayed correctly. Breadcrumb list displays the correct range. Environment Details (AEM version/service pack, any other specifics if applicable): AEM6.5 ServicePack16 Customer-name/Organization name: Hitachi Construction Machinery Co Ltd Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: If there is a lot of target data, the current default setting will cause problems. Please change the default setting. Default setting of "Include subpages" when creating a launch: ON → OFF Use-case: If ｗｅ accidentally create a launch with the default setting ON ("Include subpages"), the following problems will occur. 1.All source pages related to the launch will become unmovable, causing business problems. 2.2. Processing will not finish because it involves processing a large amount of data. We have a thorough manual to change the default setting from ON to OFF, but we accidentally worked with it ON, which caused major problems. For this reason, we would like to change the default setting to OFF. Current/Experienced Behavior: "Include subpages" default setting: ON Improved/Expected Behavior: "Include subpages" default setting: OFF (If possible, keep it OFF. Do not want it to be possible to change it to ON.) Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2024.5.16461.20240524T172309Z Customer-name/Organization name: Panasonic Screenshot (if applicable): Code package (if applicable):
Description Right now, the "Time on Page" event type is firing even if the page is not in focus e.g., when the user clicked a link that opened in a new tab. It would be great if there was an option that allows to pause the timer to only tick when the page is in focus. Why is this feature important to you This will improve the overall reliability of rules trigger by the Time on Page events, giving a more accurate view on actual user behavior on the page. How would you like the feature to work Add a checkbox that can be used to signal that only active time on the page shall be counted Current Behaviour The timer keeps ticking, even if I temporarily switch to another tab. The dummy code below more or less shows the solution. Have it running in the console and switch between tabs to see how it stops and restarts the timer upon visibilitychange events. // Sample code let timer = 0; // Stores the elapsed time in seconds let intervalId = null; // Stores the interval ID let startTime = null; // Tracks when the timer started // Function to start the timer function startTimer() { if (!intervalId) { startTime = Date.now(); intervalId = setInterval(() => { const currentTime = Date.now(); timer += Math.floor((currentTime - startTime) / 1000); startTime = currentTime; console.log(`Timer running: ${timer} seconds`); }, 1000); // Update every second } } // Function to stop the timer function stopTimer() { if (intervalId) { clearInterval(intervalId); intervalId = null; } } // Event listener for visibility change document.addEventListener("visibilitychange", () => { if (document.visibilityState === "visible") { console.log("Page in focus. Timer started."); startTimer(); } else { console.log("Page out of focus. Timer stopped."); stopTimer(); } }); // Start the timer initially if the page is in focus if (document.visibilityState === "visible") { startTimer(); }
Request for Feature Enhancement (RFE) Summary: Currently Max-length of characters is not available for rich text as that of text field and title field Use-case: Character limit for rich text Current/Experienced Behavior: No Character limit for rich text , we are doing custom validation for character limit but it would be great if we have max-length property to limit character limit as that of title and text fields. Improved/Expected Behavior: User should be able to limit the number of characters in rich text Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: When generating a report on Assets, it is possible to bypass the add details(2/3) step without supplying a date range. However, the validation constraint message only appears after proceeding to the final step(3/3) and creating the report. Ideally, the constraint violation message should appear on the same page as soon as the condition is violated. Use-case: Current/Experienced Behavior: Steps to reproduce: 1. Navigate to AEM Tools> Assets > Reports 2. Click on 'Create' button on right hand top corner. 3. Select any Type of report and click Next 4. On Add Details screen "/ui#/aem/mnt/overlay/dam/gui/content/reports/createreportwizard.html" add required field without choosing any values under 'Adjust Date' click on Next and then create report An error message 'Date Field Error' popup is shown Improved/Expected Behavior: Ideally, the constraint violation message should appear on the same page as soon as the condition is violated. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 , AEMaaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Extend the content fragments console navigation toolbar to provide an option to start a workflow. Use-case: This is a common scenario where content editors do not have permission to use quick publish/publish management, but are forced to use activation workflows to ensure only approved content is published. A new content fragments console does not have an option to start a workflow. Current/Experienced Behavior: After editing a CF in the content fragments console, an editor has to go to the assets view and find the CF to trigger the workflow Improved/Expected Behavior: An editor can start a workflow for content fragments from the content fragment console Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Service Customer-name/Organization name: Philip Morris Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: When a reviewer tries to use Enter to create a line break when adding comments, AEM submits the comment. They actually have to use Shift-Enter to just get a line break, which isn't intuitive. Use-case: Enable reviewers to hit enter to include a line break. Current/Experienced Behavior: Hitting enter submits the comment. Improved/Expected Behavior: Enable reviewers to hit enter to include a line break. Provide either a 'Submit' button, or make the behavior configurable. Environment Details (AEM version/service pack, any other specifics if applicable): https://author-p108955-e1062829.adobeaemcloud.com/ Customer-name/Organization name: Workday Screenshot (if applicable): Code package (if applicable):
I'm sure you've seen in most calendars, when you are in a date far away from today, there is a button to click on that takes you to "today". That isn't there in the calendar that pops up in the due date fields in the tasks. Could that be added? We often have due dates that have been missed, and need to add in a more updated date. If we could have the option to take us to "today" that would save a lot of clicks (and we need to save as many clicks as we can LOL!). Since this is a basic feature of most calendar popups I have seen, hoping it could be an easy add.
We can add a column what shows when a report is created to views and reports, but we can not add a column to show when a Dashboard was created. We need to be able to see when a dashboard was created just like we would for a report, project, etc.
We need to be able to see tasks assigned to a team even after someone has "claimed" it. There is no filter that allows this in the My Work widget and disappears from the Team widget too. Meanwhile, other team members still need to see it and keep it on their radar until it is completed.
In addition to the current character count, we need to be able to limit the number of characters that a user can input to a given custom form field.
Description - Our team tracks all projects by fiscal year rather than the calendar year. Currently, the available views in Workfront do not support this tracking method. Could you please enable or support a product development request with a Gantt chart view that aligns with our fiscal year (October-September)? This adjustment will greatly enhance our project tracking and reporting accuracy. Why is this feature important to you - We work in fiscal year and will help us more accurately track our projects How would you like the feature to work -We would like to be able to customize our fiscal dates in the gantt view Current Behaviour - It only allows for weekly, monthly, quarterly, and yearly
Create a more robust reporting source to identify internal users within my organization who are actively accessing Adobe Analytics. In order to help with account management, having the ability to filter for things such as specific dates without having to select multiple users will bring a greater ease. I think it would be beneficial it the reporting was to how client data is filtered by date and whatever else data is available in the standard Adobe Analytics UI Currently, we have to navigate to the "Last Analytics Access" for any user you want by following these steps: 1. Login to experience cloud, Go to Analytics. 2. In the top toolbar click on Admin. 3. Then click on Analytics users and assets. 4. Here, you can view the list of users. There is a column titled "Last Analytics Access," which indicates the date and time when a particular user last accessed Adobe Analytics. You can sort this column by oldest to newest or newest to older by clicking on it then selecting the users you want by clicking the checkbox next to their name. From there a option appears to export the data.
Description -Moving WorkFront into the Adobe Unified Experience removes all branding from the system. This now looks like a generic system. We used to leverage universal branding for the system, and department specific branding through layout templates so that the interface was recognizable to our users. Since the overall site cannot be branded, it would be nice to brand request forms. Why is this feature important to you -Since the site is not branded anymore, having branding on request forms would help our requestors. These are not everyday users of the system so their knowledge about the system is limited. With the many security and phishing issues out there, branding on the form would help "legitimize" the portal to requestors. How would you like the feature to work -I would like to add a logo at the top of the request form based on the Request Type. Would also be open to the logo being placed under the Request Type so that it appears after you select the request type. Current Behaviour -Currently, we can add some branding/logo within custom forms attached to request queue's but this mean the placement is after the the standard Request Queue fields (Subject, Description, Priority, etc.). The placement of branding/logo should be at the top of any form.
Ability to mark the mentions as Read so we can only see New mentions. Keeps the list cleaner like the notifications list functionality in the top menu bar
Request for Feature Enhancement (RFE) Summary: Have a direct link to the specific topic submitted for review from within the email notification that's sent to the reviewer. Use-case: We ask PMs to review topics, and have received feedback that the current process is confusing for them as they need to navigate within AEM to find the relevant topic to review. Current/Experienced Behavior: The email takes the reviewer to the review inbox Improved/Expected Behavior: Take reviewer directly to the topic that the email was about Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Workday Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Improve UX by adding contextual help/tooltips/instructional help within AEM. Use-case: Technical writers currently find it difficult to know the purpose of many icons, buttons, and menu items when navigating the AEM UI as they don't have any/sufficient tooltips or instructional help. Current/Experienced Behavior: Improved/Expected Behavior: Clarity regarding the purpose and meaning of: Menu items. The distinction between "Experience Fragments", "Assets", and "Content Fragments". Global vs iLX Profile. It would be helpful to have an easily accessible link to Adobe's documentation within AEM. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Workday Screenshot (if applicable): Code package (if applicable):
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
