Product ideas | Community
Skip to main content

10000 Ideas

Heather_Kulbacki
Heather_KulbackiNew Participant

Recurring Task EnhancementsDeclined

This time of year I find myself creating a lot(!) of recurring tasks as reminders for weekly, monthly, quarterly events for next year. I suspect more users would take advantage of recurring tasks if they were a bit easier to execute. And I've finally documented a host of enhancements that are needed for recurring tasks as they currently function. During set-up of the taks, I'd like to assign the child tasks to a user without assigning the parent task, there is no reason to assign the parent task to someone when all the child tasks are assigned to them. And that parent task just becomes clutter in their work listAllow choice of child task suffix. Currently the suffix auto-populates as a sequential number. I wind up manually editing every task and changing that number to the planned completion date. I can see others potentially wanting to use something else as the suffix, planned start day perhapsAllow entry of both planned hours and duration while setting up the task (we use the Simple duration type). Currently if you enter planned hours only, those fill into the duration column on the task list and the planned hours are 0. If you enter both planned hours and duration days during setup, the days enter in the duration column, but the planned hours fill in as 0. Then when you manually change all the planned hours to what you want there, the duration auto-chages to a portion of a day equal to the hours you enter. So I wind up manually editing both the duration and the planned hours for every task. You also can't change the duration or planned hours through a bulk edit of the child tasks - so still I wind up manually editing both the duration and the planned hours for every task. Allow setting something other than the start date of recurring tasks as well as a task constraint. For some tasks I want a must finish on task constraint and I'd like to set that as the recurring date. For example I want a 3 day duration that must finish every Friday, so I have to enter the start date as Wednesday. Manually edit the duration after the tasks have created, then bulk edit all the child tasks to change the constraint to must finish on. I've found additional ideas regarding recurring tasks as well: Create recurring tasks via a templateCreate sets of recurring tasksOrganizing recurring tasksDurations and planned hours on recurring tasksCreating recurring tasks on additional schedulesCreate child recurring tasks with custom formsAnother variation on additional schedule options

Update Content Security Policy (CSP) to Support "WalkMe" Integration Following Admin Console MigrationNew

DescriptionAfter migrating to the Admin Console environment, the WalkMe integration used by IPG has lost connectivity to Workfront. WalkMe previously worked in their original environment before the URL was migrated to experience.adobe.com. The issue seems to stem from the current Content Security Policy (CSP) for adobe.com and adobe.net, which is blocking the WalkMe scripts and resources necessary for the tool to function.The WalkMe team has confirmed that specific URLs need to be added to the CSP for the integration to work again.  Why is this feature important to youWalkMe is a crucial tool used by our customers for guiding users through Workfront, providing real-time help and onboarding assistance. Without it, teams are unable to effectively train new users or assist current ones in navigating Workfront, resulting in a negative impact on productivity and user adoption. Restoring this functionality is critical to maintaining seamless operations for large enterprise clients like IPG, who rely on this tool for workflow optimization. How would you like the feature to workAdobe needs to add the necessary WalkMe URLs to the Content Security Policy (CSP) for experience.adobe.com and related domains. This would enable WalkMe's scripts and resources to load correctly, allowing customers to fully utilize the WalkMe integration within Workfront as they did prior to the migration to the Admin Console. The URLs to be added to the CSP are:script-src 'self' *.walkme.com 'unsafe-inline';style-src 'self' *.walkme.com 'unsafe-inline';img-src 'self' *.walkme.com s3.walkmeusercontent.com d3sbxpiag177w8.cloudfront.net data:;font-src 'self' *.walkme.com data:;connect-src 'self' *.walkme.com;frame-src 'self' *.walkme.com blob:;worker-src 'self' blob: *.walkme.com; Current BehaviorCurrently, the WalkMe integration does not work with Workfront after migrating to the Admin Console. The Content Security Policy (CSP) for adobe.com and adobe.net is blocking the necessary scripts and resources from WalkMe, causing the tool to fail. Users are unable to access the WalkMe guides and features that were previously functioning in the original environment before the migration.