Product ideas | Community
Skip to main content

10000 Ideas

MarlaDrNew Participant

Timesheet Profile Updates - Add option to select 'None'New

Description -We have users who do not need to log time based on their job level. For those users, we didn't apply a timesheet profile. Now we have some users were who logging time but due to recent job role changes are now not required to log time. I went to change their timesheet profile to remove it and with the new UI updates, it does not allow me to do so. It only always you to choose another timesheet profile. How would you like the feature to work - I would like the ability to completely remove or clear a timesheet profile from a user’s profile in the UI. Ideally, there should be an option to select “none” or leave the field blank, so that no timesheet is generated for those users who do not need to log time. Current Behaviour -Currently, the new UI does not allow clearing or removing a timesheet profile from a user’s profile. Instead, it requires assigning a different profile, with no option to set it to “none.” Support has confirmed this is a known limitation affecting multiple customers. They provided a workaround below, but it is more time-consuming and less efficient. Allowing administrators to remove timesheet profiles directly in the UI would simplify the process and improve usability. From Support: Best workaround here would be to create a “No Timesheet Required” profile to act as a replacement for these users. You could do this by creating a dummy timesheet profile (e.g., “No Timesheet Required”) with settings that do not generate timesheets or have no approvers/hours types. Then assign this profile to users who should not log time. You will then want to update your “no logged time” reports to exclude users assigned to this profile.

LyleSt1New Participant

Enable support for modern package managers (Yarn or PNPM) in the Frontend Deployment Pipeline of Cloud ManagerInvestigating

Request for Feature Enhancement (RFE) Summary: lease enable support for modern package managers in the Frontend Deployment Pipeline. Currently the pipeline only supports NPM, which although widely adopted is also generally known as the slowest solution for package management within the nodejs ecosystem. Consider support for yarn or pnpm, both of which outperform NPM from a CI/CD perspective. Use-case: We currently use Yarn on Managed Services to deploy full stack code. However, when migrating to Cloud Services and wanting to take advantage of the Front End (FED) pipeline, NPM is assumed and only the version can be altered via pipeline variables. We use Yarn as it has additional features and builds/deploys faster than NPM. Similarly, pnmp and Yarn PnP deploy about twice as fast as npm in our benchmark tests. Current/Experienced Behavior: Customers must use NPM and package-lock.json as the deployment package manager Improved/Expected Behavior: Customers can customize the FED deployment pipline to usee the package manager of their choice. This could be either an explicit selection, a pipeline variable, or the pipeline could lockfile detection (npm uses package-lock.json, yarn uses yarn.lock, pnpm uses pnpm-lock.yaml) Environment Details (AEM version/service pack, any other specifics if applicable): This request is for AEM Cloud Service, current version. Customer-name/Organization name: Toyota Motors North America (TMNA) Screenshot (if applicable)     Code package (if applicable):  

BrentHat
BrentHatNew Participant

Better planned hours management in new Priorities viewNew

The new Priorities view has really caught on with our team. The GUI is attractive and the recent release brings a lot of functionality that helps the team have a singular place to go in order to manage work assigned to them. But it could be perfect! Please add the same "edit allocations" functionality as is available in the Workload Balancer (within the Resource Management section) that allows a user to specify planned hours for a task on a day-to-day, week-to-week, or month-to-month basis. Currently, the Priorities view only allows a user to change the total planned hours of a task over the entire duration of the task.The ability for a working team member to specify the exact amount of hours they will spend on the remainder of a task gives managers a more specific view from week to week. We do not have access restrictions of the Workload Balancer on our team and have found it very useful to use during our meetings when discussing what will be worked on during a given week and each member has the autonomy to update the planned hours for all tasks that are either in progress or about to start. This granularity that the Workload Balancer provides would make the Priorities view the ONLY view that a team would need in order to make quick, simple changes without having to jump to a different part of Workfront. Perhaps the Log Time pop-up (image attached) could be used to enter in allocations? Thanks! 

LucyLuz
LucyLuzNew Participant

Proofing Tool - PDF OutputNew

Description - The Print Summary PDF download within Workfront’s Proofing tool creates a flat image of the proof with any comments and markups, and is used if the marked up proof needs to be circulated outside of the proofing tool itself. The reason the originally uploaded pdf with any markups made in the proofing tool needs to be extracted from Workfront, rather than viewed in the tool itself by the agencies making amends as a result of these mark ups, is the agencies often use other Adobe products and comparison tools which contain scripted (coded) elements to compare the original pdf to the marked up pdf, and amend original files where possible in a more automated way. Given Workfront is an Adobe product, it would be preferable to have a high quality Adobe PDF output which is compatible with other Adobe products to ensure consistency and ease of use. The rasterising of the marked up proof and addition of wide margins / summary page changes the structure of the file so much from the original that it makes it impossible to be run through scripting tools when comparing to the original document / pdf. Why is this feature important to you - Having integrated Workfront into the organisation, we now have major issues in our in-house agency being able to use the system fully in the way we intended them to, i.e. collaborating with comms teams via the system, being able to download a marked up PDF once this has gone through the system, and then re-upload the amended document. We’d also like the agency to be able to use their comparison tools and quality check tools in order to negate risk in sending customer communications out incorrectly, and keep their working processes as automated as possible. How would you like the feature to work - If a pdf is uploaded as a document to Workfront, then made into a proof, then circulated to reviewers & approvers for comment, we would like these comments to be applied to the original pdf as if they had been made by the reviewer in Adobe Acrobat or Reader, and make these comments available on the (original) downloaded pdf, without changing the way the original file looks or inflating the filesize (the print summary PDF screenshot / rasterization process can inflate the filesize by upwards of 20x). Ultimately we need multiple reviewers to be able to comment / collaborate / review one file in a similar way to how several users can on a shared PDF in document cloud, but from within the WF application and also allowing them the ability to record an approval decision. Current Behaviour - As it stands, the proofing tool produces a flat image file containing mark ups. Our agencies cannot work with this in terms of using it in their comparison tool and quality checking tools. The PDF print summary therefore cannot be used due to it not being the original Adobe PDF. As such, users now have to use a workaround process in which they go offline and mark up the original PDF to send to the agency, even though they use the proofing tool for reviewer comment and approval.

Alex_Di
Alex_DiNew Participant

When the Project Owner sets a task status from Complete Pending Approval to New or In Progress, clear assigned user(s) complete checkmarkNew

Description - When a project owner is reviewing a project and find a task marked as Complete Pending Approval and review to find the task needs to have more work done on it, but they are not one of the approvers, when they change the status of the task to either In Progress or New, the user assigned to the task gets no notification and the task does not show on their My Work.  This is because the assigned user still has the checkmark of complete on the task.  This makes the project owner take additional steps of having to tag the assigned person to let them know they have to click the "not done yet" or unassign the person and reassign them to the task.  Why is this feature important to you - This causes confusion for the project owner and if they forget to tag the assigned user or do the unassign reassign steps the task will be delayed.  How would you like the feature to work - When the status of a task is changed from Complete or Complete Pending Approval to either New or In Progress the "done" indication for the assigned user should be removed and the task should appear on their My Work.  Current Behavior - When a user marks a task as "work on it" then completes the task, it marks them as "done" and adds a Checkmark next to their icon that shows they are assigned to the task. If the task is then moved back to in progress by someone else, the checkmark remains and since the user completed what they needed to do.