Build better products with our product team
HI,It will be a great option, if we have possibility to select workload balancer in Percentage (%) also, in addition of Hours.Please vote if you agree.RegardsKundan.
Currently Workload Balancer sorts by Day and Week. Can another option be added to sort by Month?
Hello,This is a request to add a filtering category to the Workload Balancer to sort by Resource Pool.Resource Pools are a feature within Workfront which would be helpful to filter by within the Workload Balancer.Thanks!
The Scheduler/Workload Balancer lacks fundamental functionality. It allows you to filter out only parent tasks. It should allow you to filter out certain tasks all together. Example, I might have a project with 150 tasks. However, I only need to schedule resources against 50 tasks. There should be some kind of attribute that can be set at the task level where the system would include or exclude from the scheduler. Unfortunately, this has been a deal breaker for our department. We are looking outside of Workfront for a scheduling tool.
The ability to filter based on fields within the task object. For example, we want to only see tasks show up in the Working On section that are ready to be started (e.g. a specific approval process id field value).
It would be nice to be able to allow my directors the ability to see the resource management information from the copied URL on their reports.
Currently, we only have the option of using FTE with default schedule or user schedule without FTE. We need the combined functionality of both FTE and user schedule. For example, we want an engineer to be available 75% of his time (30 hours per week) to work on projects, but if he is taking 2 days off on a particular week, his available hours for the week should be 14 hours (30 hours - 16 hours). This functionality would make resource management a lot more easier.
Currently there is no way to adjust the hours from week to week for unassigned roles within the workload balancer. The balancer evenly spreads the planned hours over the duration (not evenly sometimes), but you cannot adjust them to meet the actual cadence of work.As an example, if you have 40 hours with a duration for 10 days (2 weeks). The balancer will spread that as 20 hours the first week and 20 hours the second week. We should be able to adjust that so it is 30 hours the first week and 10 the second (or whatever the correct number would be).It should be the same functionality as working with the assigned resources.
We need the ability to bulk transfer tasks within Workload Balancer by user or job role. We love the flexibility and improved UI of the Workload Balancer, but consistently rely on the Scheduling tab within projects to Assign, Swap and Unassign team members. Our PM's can manage small task transfers by using the "assign this to" button on Workload Balancer, but this is not reasonable for resource changes on an entire project or team. Would love to see this Actions "bulk editing" feature added in a future update!
It would be great if the workload balancer functionality took the place of the scheduling tab within the project. Only the assignment for that project would appear. It would save the PM from having to go to a different place to make changes.
We are currently looking to implement MSI in a synced ENV to reduce the necessity of multiple Marketo instances. We have hit a limitation that where the GUIDs match between the 2 ENV's MSI works correctly, but where the GUIDs do not match, it cannot link the record between D365 and Marketo. We do have a synced custom field (synced between D365 ENVs and Marketo) that could be used as a unique identifier between all 3 ENV's.
Description - A lot of my clients request data obfuscation/encryption rather than deletion, GDPR package could be enhanced with an option to obfuscate rather than delete.Why is this feature important to you - Client's requestHow would you like the feature to work - Add an extra option in the GDPR package to obfuscate data rather than delete.Current Behaviour - GDPR deletes data
The breadcrumbs in the New Workfront Experience are useful, however the lack of distinction between Parent tasks and Child tasks is causing a lot of confusion with users while navigating and working on Projects.In our organisation, we refer to Parent tasks as "Products" and child tasks as "Tasks".When working on a child task having Parent tasks and Child tasks both labelled as "Task" is not helpful. We would like Workfront to allow for the customisation of the labelling of Parent tasks and Child tasks in the Terminology config screen for layout templates.
Hi, It would be nice to have a complete Password management in Campaign Classic:At User Creation:Generate a temporary complex passwordSend the "Create my password" link via emailWhen the User is created:"Forgot my password" featureFrom an admin perspective, re-send the "Create my password" link for 1 or more users at onceAs it is currently a long & manual process. BestFlorian
In preparation for an instance migration, we need to identify all custom forms that utilize display logic within them. Also if the report could indicate the number of logic driven fields there are it would be helpful! Does anyone know if this already exists or is it worthy of an enhanement request. I'd love to hear your thoughts.
Request for Feature Enhancement (RFE) Summary: Functionality to resolve duplicates/unreferenced assets in AEM DAM along with mechanism to set asset name validation while uploading an asset. Use-case: For larger organizations to maintain and better organize AEM DAM, where the number of assets(mostly pdf's) is ever increasing. Current/Experienced Behavior: Custom workflows/maintenance jobs or even need to write python/bash scripts.For any new assets making entry in the system we should make amends in form of asset name validations to prevent malformed names (customization). Improved/Expected Behavior: OOTB functionality to resolve duplicates/unreferenced and to set regex for asset name validation w.r.t the naming convention the organization would be following.. Environment Details (AEM version/service pack, any other specifics if applicable): Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: As a user, I'd like to see my filters "pop-out" instead of remaining static so that I can pinpoint & work faster. Use-case: When searching for assets, filters will be more visible to the user Current/Experienced Behavior: User needs to look carefully for filter list Improved/Expected Behavior: Filters will pop out in a modal or otherwise visible element so that they are easier to see and work with. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 2021.7.5607.20210705T063041Z-210600 Customer-name/Organization name: Accenture Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: As a content author when I move a page that is already published and live, I get the option to adjust/republish in the. wizard. I unselect the republish option and complete the move operation.The expectation is the live page remains unaffected by the move until I choose to (re)publish the page from the new destination. However the page is already deleted from the old location. This leads to unnecessary confusion.Can the experience of this be improved may be with appropriate messaging. Use-case: Content author moving a page Current/Experienced Behavior: Move a page that is already published and live, I get the option to adjust/republish in the wizard. I unselect the republish option and complete the move operation.The expectation is the live page remains unaffected by the move until I choose to (re)publish the page from the new destination. However the page is already deleted from the old location Improved/Expected Behavior: Better messaging about what republishing means before the move operation Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.6 Customer-name/Organization name: Invesco Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Have the option to disable auto-unpublishing of assets when they expire in AEM Use-case: We don't want assets to get unpublished when they expire because it will cause broken images appearing in our website Current/Experienced Behavior: When the out-of-the-box expiration field in AEM is used, an expired asset gets automatically published Improved/Expected Behavior: Have the option to disable auto-unpublishing of assets when they expire in AEM Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Adobe AEM Assets allows user to email the download to another user. The email creates a link to a zip file, sends it from a no-reply address and looks suspicious, like a security breach. No sender information is included in the email. Here are the steps to reproduce: Select 1 or more Assets Click “Download” In the Download dialog, choose “Email” and enter the user’s email address AEM will generate a ZIP file of the asset(s) and email the user. Use-case: Current/Experienced Behavior: The email feature creates a link to a zip file, sends it from a no-reply address and looks suspicious, like a security breach. Improved/Expected Behavior: The email body should include sender's username or email address, so the email can be verified and authenticated by the recipient. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.8 Customer-name/Organization name: Wakefern Food Corp Screenshot (if applicable): Sample email that AEM Assets sends - you can see how suspicious this looks: Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Feature Enhancement - Manage tags in Collections. Currently, in order to manage tags of assets included in a collection, the user needs to open the assets through the folder taxonomy Use-case: We have users of Assets (DAM) who want to manage tags without leaving the collections UI Current/Experienced Behavior: Smart tags can not be managed through the collection UI Improved/Expected Behavior: There is an ability to manage smart tags in the collections UI Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCs Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: In the reprocess function, add an option to just process certain items like presets, metadata, etc Use-case: Select an asset or folder and then hit reprocess. In the reprocessing dialog, the only option is "Full process". It will be good if there is an option to reprocess --- metadata, presets, smart crops Current/Experienced Behavior: Select an asset or folder and then hit reprocess. In the reprocessing dialog, the only option is "Full process". Improved/Expected Behavior: Have an option to select --- metadata, presets, smart crops Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: The existing aem-event-proxy-skyline source code distribution enforces assumptions that are incompatible with many potential use cases, and future development in this direction should relax these constraints on AEM's role as an Adobe I/O event producer. Use-case: * Developers should be empowered to fire custom Adobe I/O events from publishers, directly from custom servlet code. For example, POST requests from customers containing PII that must be sent to an Adobe I/O runtime for correlation with anonymized aggregate metrics from Analytics. * In a a multisite hosting scenario, it is plausible that a Firefly App would be deployed to the organization that is only interested in consuming events originating from a particular regional site, without having to introspect the event payload to determine if the associated request resource actually maps to the appropriate domain. Of course, this is an established pattern for Analytics and Target cloud service integrations in AEM already.* AEM developers working on site functionality should be able to iterate together with Project Firefly developers to evolve event payload formats without being forced to conform to XDM activity stream types. Current/Experienced Behavior: * IMS Configurations cannot be replicated to publishers, even though system user nodes and keystores are replicable.* (Aem-event-proxy) Workspace configuration is not runtime configurable.* (Aem-event-proxy) Adobe I/O integration in publish environment is not supported and not enabled with distributed sources.* (Aem-event-proxy) Only one adobe I/O configuration is supported for the environment* (Aem-event-proxy) For custom events, API client code must flatten complex event payloads to the OSGi event structure, with no synchronous feedback. Improved/Expected Behavior: * All Adobe I/O Configuration and IMS Configuration active in the publish environment should be modifiable at runtime by users authorized to use the Configuration Browser and IMS Technical Accounts consoles, respectively, in the author environment. * AEM should allow users to create multiple Adobe I/O Configurations (and their associated IMS Configurations and CSM registrations) and should support context-aware association to zero-or-more content trees. * CSM registration should be a deterministic activity occurring on the author environment, with the registration status of an Adobe I/O Configuration made visible to the user, and with reasonable ability to change labels and descriptions of the registration to support better management of integrations across the organization.* Due to the synchronous nature of a servlet execution, the API provided by the native integration should support synchronous feedback to the servlet for the backend submission to eventsingress, in case the the request should be reattempted by the client. In other words, the AEM integration should not add an asynchronous layer like Sling Jobs, unless this behavior in the context of AEM is specifically desired by the client. * XDM Schema Event mapping should be a feature available in the API, but not required by the fundamental postEvent method signature. Environment Details (AEM version/service pack, any other specifics if applicable): Skyline Customer-name/Organization name: Bounteous Screenshot (if applicable): Code package (if applicable):
Many customers today need the AEM Versions to be kept and not purge due to legal requirements.At any given point of time , customers may want to restore to any previous versions, can view differences, go in timewarp mode with all the previous versions of a page. Over a period of time , the jcr:VersionStorage can grow to more than 100 million nodes which makes indexing , Inplace Upgrade and overall system performances slow. We need ability in AEM where jcr versions can be offloaded to an offloaded instance / shared mount and all the OOTB functionalities like Restore, TimeWarp, Version history / difference should work AS IS without the need of custom code/ implementation.
Hello,our client is using the Multi-Site Management (MSM) features a lot.In a live copy, only a full page can be synchronized with the source.As rolling out a component to the live copies is possible already, they would like to have a feature for synchronizing a page in the live copy on component level as well.Business Value: This will reduce risks of publishing non-approved content and also will reduce communication effort within the editorial team.Can this be added to AEM?Thanks & Many regardsHendrik
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
