Request for Feature Enhancement (RFE) Summary: Delete page in author should auto unpublish the page. Use-case: Content authors who are new to AEM are deleting the pages without unpublishing them, assuming it will reflect the on actual site. Page is deleted in author but not in publish or in live site. Current/Experienced Behavior: Deleting page on author stays on author without unpublishing it. Improved/Expected Behavior: Expected it to auto publish the page if author deletes the page. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description - Would like a stopwatch or timer feature available in WF (available in multiple locations). Why is this feature important to you - Our developers and editorial staff are requesting this and think it's a huge miss that WF doesn't have this feature when SO many other PM sites have it. How would you like the feature to work - Start, stop, pause, record to timesheet features Current Behaviour - Our time is using their phones or purchased stop watches to do this and want it within WF.
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.
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.
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 we 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):
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.
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.