Build better products with our product team
Description -Why is this feature important to you - we currently review ad copy spreadsheets that are very long in width, but readability is limited with the 400% zoom. We don't want to change the spreadsheet to accomodate Workfront's proofing tool. Instead, we take the review out of Workfront proof if the reviewers can't zoom into the copy large enough for readabilityHow would you like the feature to work - unlimited zoom. The file itself can be the limit to how far we can zoom in, but text based files shouldn't have any real limitCurrent Behaviour - The copy is too small to read on some long spreadsheets at 400% zoom.
By default, all dimensions are included when using Attribution IQ in Adobe Workspace. This includes the Date dimensions. However, I would like there to be an option to disable the modelling for the Date dimensions. This is because the current behaviour when adding a Date dimension (e.g. day) to a metric with a First Touch model is that conversions are attributed to the first day within the lookback window that a touchpoint occurred. For example, if my organisation uses a first touch attribution model, and I want to show the daily trend for conversions attributed to the Organic Search channel in the past week, then I cannot do this. Instead, they are plotted in the previous 37 days (depending on when the first touch for the channel occurred. I believe a visualisation which plotted the success events on the day they occurred, whilst still using a First Touch model, would be more inutitive.
Why is this feature important to you To combine offline geo data with online website behavioure.g we could create calculated metrics such as “Visits per populus” or “Registrations per populus” for each country/region/city and view this in Adobe Analytics. How would you like the feature to work -Country, City, Region to be added to the list of dimensions supported by Adobe data sources. Current BehaviourThese dimensions are not supported by Adobe data sources NB - Using Geo Zip to populate the Zip Code dimension leads to the collection of personal data in the UK so could not be used to satisfy this use case.
Why is this feature important to you? I want to have a geo variable for UK users that can be classified and also used in data sources. This will allow us to combine our offline geographic segments with onsite behavioural data. It will also enable us to create calculated metrics such as "registration per local authority" so that we can analyse regional performance in Adobe Analytics. Using Geo Zip to populate the Zip Code dimension does satisfy these requirement except that it captures full UK postcode (e.g. HP22 5UY). This is considered personal information because some postcodes contain only one address. We do not want to to collect and store this information as it may contravene the Data Protection Act 2018. However, if the last two characters were removed such that we only captured "4 digit" postcodes (aka Postal Sector, e.g. "HP22 5"), then these are sufficiently anonymous. How would you like the feature to work?An additional option in Report Suite Settings > General Account Settings.If the Zip Option is set to "use geo", then provide an additional configuration for UK postcodes ( 1. Use Full Postcode, 2. Remove Last Character, 3. Remove Last Two Characters, 4. Remove Last Three Characters).Current Behaviour?If a Geo Zip setting is enabled in Zip settings, then the Zip Code dimension is populated with a Full Postcode. Other NotesNB - I have considered the argument that because the postcode data is captured via IP address that it is too inaccurate to truly be personal data (insofar that you're not actually capturing someone's postcode but the nearest ping tower - or whatever Safari has produce). But I do not feel this would cover us in all situations. Separately, some of our use cases could be met if this other feature was implemented instead but on the other hand the idea was first raised 10 years ago (!)https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-ideas/out-of-the-box-reports-should-have-the-capability-of-being/idi-p/338900
Within the New Workfront Experience (NWE), the Description field under Teams is extremely small and causes issues with those who use that field to add long hyperlinks for users to click on. The UI of this is poor, it should be a more prominent, much larger field.Steps to Duplicate:1. Log into workfront classic 2. Navigate to a team and edit the teams description 3. Grab any link and paste the URL in the description 4. Stop editing and view the description 5. Notice how big a field description is, how it's obvious to the user6. Switch to NWE and navigate to the same team description7. Notice the hyperlinks are there but the area for this field is extremely small and you have to scroll down to see the full description.
Please make the carrot next to the column name BIGGER. We are constantly try to collapse all but click the column name instead! In most cases this is the task name column and then the tasks get sorted alphabetically when we want them collapsed!
Business Need: Blueprints is great. Love it. But I don't want all of my Workers and Planners trying to shake up our business and creating unnecessary work for our System AdminsCurrent State: Blueprints shows up on the lower bar of the main menu (non-layout template manipulated)Desired Functionality: Blueprint should either be able to be added or removed like most features via layout templates or have a toggle that admins can manage to remove it or add it via layout templates.
Our teams are loving the pin feature however are pinning multiple pins within the same category which results in what looks like duplicative pins thus, clicking into each pin and defeating the purpose of the pin naming. It would be ideal to allow for a renaming or nickname of the pin as part of the pinning feature.
It would be great if I could assign multiple teams to the same task. Currently, I allow my supervisors (resource managers) for their own teams chose who in their team is assigned a task, or someone in that team can take ownership of a task. I have tasks that require input from multiple teams, but I can't assign more than one team to the same task, so for those tasks it's not "business as usual", and I can't allow all the resource managers to chose whom to assign to a task...
How difficult would it be to enable the system to calculate availability using a User's schedule and factor in a User's FTE? Current resource management functionality only factors in FTE when calculating availability if 'The Default Schedule' is selected. This setting is configured via Setup / Resource Management.To account for General Admin time, we set User FTE to .7 which reduces their availability by 30%. When majority of our users were US based and we had a single schedule to account for US/company holidays, availability was calculated by using the "Default Schedule" and factored in the .7 FTE setting assigned to our users.Over time, we've onboarded Global users in Latin America, Canada, India, EMEA, and Asia Pacific. Due to each region having country/area specific holidays, we created multiple region specific schedules.Unfortunately, when setup is changed to calculate availability using the 'User's Schedule,' it no longer factors in User FTE into the calculation. This is problematic because we can no longer easily take 30% off each users availability. The workaround would be to create a General Admin project, add all users to the schedule and then create 30% artificial demand.
Description - Please change the Proof desktop viewer so that it stops trying to update itself. Why is this feature important to you - Our company IT has barred us from being able to install apps on our laptops and everything must go through the Software Center. If for any reason we're able to successfully install the app, IT also has Symantec Endpoint Protection set up to bar the app from successfully running. How would you like the feature to work - We would like the app to stop trying to install itself. We'd also like a heads up from the Proof team whenever the app is updated. Current Behaviour - Every time the desktop Proof viewer is closed, the last act from the application is to check to see if there is a new version, and if there is, it tries to install it. If it successfully installs, the symantec endpoint protection stops the app from running. Our users assume that the app doesn't work, and this causes poor user adoption.
Description - SharePoint integration - incomplete results when searching for applicable SharePoint site Why is this feature important to you - SAIF uses SharePoint throughout many of it's workflows, and this is a hinderance as we cannot find the SharePoint site we need quickly How would you like the feature to work - We'd like the results to not be phantom results, and we'd like to see more than 100 results when searched. Current Behaviour - When we search for the SharePoint site that we need to access, while inside the SharePoint functionality within "docs" in a project - and search for the SharePoint site we need, multiple results are returned, and it appears some of those results are "phantom". Note: this is captured in this open idea as well: https://experienceleaguecommunities.adobe.com/t5/workfront-ideas/improve-sharepoint-graph-api-experience/idi-p/557242 Detailed Description The “Graph API” was recently updated from the previous legacy SharePoint integration. (An update in Workfront) Following the update, a piece of functionality in Workfront was impacted: the ability to search for files or folders in Workfront, but searching in SharePoint. It returns only 100 results (despite having potentially 1000s of results); when those results are returned, it points to “phantom” files that do not exist. For example, a search for “Adobe” rendered 3 results – the results are the exact match of the search term. In this example, 2 of the 3 results are empty – only one folder has data. The Workfront ticket, #344237 describes this issue we are seeing at SAIF. This same ticket also has an additional failure: when SAIF peoples are moving files and folders (inside of Workfront) to different SharePoint folder, or if the file has it’s named changed, then the Workfront metadata is lost for that file. This represents a substantive impact to our users’ workflows.
Using AEM along with Translation project to send pages/assets for translation, We can configure Translation rules to exclude/Include paths with /content/dam/ path allowed. Ex:- My DAM structure is "/content/dam/XYZ/global", "/content/dam/XYZ/us", "/content/dam/XYZ/uk" "/content/dam/XYZ/de" etc.. I have image component which will be used by authors in different sections of the page and browse images from the above paths. Here I want to exclude images from "/content/dam/XYZ/global" but take images from other locales for translation while they submit pages for translation. I have posted similar question earlier to questions section and was asked to submit the "support ticket", hope this is the right place to submit this. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/skip-assets-from-asset-translation-job/qaq-p/377318
Description - Monthly we run capacity reports based on Planner in attempt to determine if we have enough in-house capacity for Creative job roles. No matter how we filter, we still see projects listed even if a job role isn't associated with the project.Why is this feature important to you - Without the ability to filter out these projects that aren't relevant to the job role, we run into the row limit outrageously fast. Ultimately we're stuck with exporting over a dozen permutations of our filters each time we want to run our capacity planning protocol. I confirmed with Support that there is no good filter to ignore rows of 0s.How would you like the feature to work - Offer a toggle switch to include/exclude rows of 0 data.Current Behaviour - After exporting data to Excel, we have to manually exclude rows of 0 planned hours.
Description - When creating/ updating a custom form, it would be great if it was possible to be able to change a field type (for instance, from a Drop-down field to a Checkbox or Radio Button field). This would be so helpful because you wouldn't have to reenter all the information again and rebuild all the logic/ loig dependencies that might be associated with the fieldWhy is this feature important to you - Time saver, wouldn't have to duplicate work, allow for custom forms/ custom fields to be more easily updated How would you like the feature to work - Ability to change type of custom field to another type without have to reenter data and reset logicCurrent Behavior - Currently, when you change a field type you have to start from scratch and rebuild the entire field and reenter all the logic associated with that custom field
In some instances, work from a timeline task on a project with a default schedule set to exclude weekends shows up in WLB with time assigned to over the weekend. This causes a discrepancy between the project schedule and the WLB resourcing. I understand that for some reason this is intentionally set up this way, but there should then at least be a setting in the WLB to exclude scheduling work over the weekend.
Description: Would like to be able to take a card on a board and convert into a project similar to the way we convert a request to a project with a template. It seems like this would have already been a feature.Why is this feature important to you - Create efficiencies and decrease manual processes. How would you like the feature to work - The same way a request gets converted into a project. Current Behavior - If there is a card on a board and it is determined it should be its own project, you have to manually create a project and then close the card. @suzyf @rudyha1 @hollyse @annapu
In a Workfront Kanban board, the API calls for 50 items to be displayed when the board loads. In order for more items to display, a person needs to select "Show more work items" each time that the page is reloaded. I would like the API to call for a higher number of items (potentially 100) each time the board loads. This will help team members using the board from needing to click "Show more items" each time the board loads.
Ability to Change primary assignments on objects
Description - Provide an ability to move issues to ProjectsWhy is this feature important to you - It provides an adiditonal way to keep work movingHow would you like the feature to work - Exact same functionality available on webCurrent Behaviour - Functionality not available
Integrate Planned Hours and Actual Hours fields with the task/issue percentage complete bar and iteration burn down chart. This is important because it would show meaningful data metrics as opposed to hypothetical, relative, manually-set percentages complete. When the Planned Hours and Actual Hours fields are added to the task and issue cards, as the task and issue owners update the actual hours spent, the percentage complete bar is automatically updated based on the initial Planned Hours. Optimally, there would be 3 standard Agile task and issue fields to accurately show the effort against the work and to capacity plan:Planned HoursActual Hours SpentHours Remaining The current behavior relies on the task or issue owner to calculate the percentage complete based on what they think or feel.
Hi, it would be great if we could pull a similar report as the Email Link Click report, but for landing pages. so we could see the # of clicks on each link on our landing pages. We can currently pull one-by-one using smartlists, but it only shows the people we have in our Marketo system, not the gross # of clicks like we could see in an Email Link Click report.
Zusammenfassung der Funktionsverbesserungsanfrage (RFE): The expired assets predicate in the search filter currently only has one feature. Asset is already expired.Yet there are much more interesting things related to the expiry, that could be shown.Here are some examples for more interesting search filter regarding the expiry: Expired: The asset itself is expired(Ignore Dependencies) Has expired dependencies: The asset contains expired assets (Don't show expired assets, but instead those assets that contain an expired asset) Will expire: The asset will expire till (dateselect)+ usefull quickoptions: within the next 1 week, 1 month, 1year etc.)Be careful using those on sites / print projects that will be used for a longer period of time, since the printed media can't be "unpublished" but have to be destroyed, removed etc.) Will not expire: Show only assets that are free of an expiry restrictionI call it the "care free" option. Assetts can be used without having any fear that they will depublish themself / printed items do not have to be destroyed because one asset is no longer licensed Anwendungsfall: A user that wants to produce a print medium has to check if the assets that went into the print medium are not restricted with an expiry date. A cataloge might contain up to 800 assets. The cataloge will be printed with a circulation of 10k pieces. Currently, a user would have to check each individual asset to see whether it expires before the estimated time at which the print copies will be replaced by a newer one. Or a user builds an asset into a site, just to see that the asset depublished itself one week after the site launched because the expiry was overlooked. Aktuelles/erlebtes Verhalten: The expiry search predicate is built to make only visible what is already expired (what can not be used). In addition it makes it not easily distinguishable if the expiry flag is set because an asset itself is expired or if it contains a expired asset. Verbessertes/erwartetes Verhalten: Add additional functions as written in the RFE.Two checkboxes for expired, one for assets and another for dependenciesCheckboxes that look into the future and give the user a option to check if the asset will expire within a range or has an expiry at all. Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): 2023.8.13323.20230831T134651Z Name des Kunden/der Organisation: medi GmbH & Co. KG Screenshot (sofern zutreffend): Code-Paket (sofern zutreffend):
Request for Feature Enhancement (RFE) Summary: Support for multiple SMTP configurations Use-case: Many client work in multi-tenant set-up. Very often they need different SMTP configurations to send emails. Current/Experienced Behavior: Only one SMTP server can be configured by Day CQ mail service Improved/Expected Behavior: A factory configuration is available for SMTP configs. One can pick one dynamically and send emails Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Brillio Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Trigger dispatcher cache flush agent on receive in local AaaCS SDK Use-case: Developers needs the replication behavior similar to that of a server for validating caching use cases. Current/Experienced Behavior: An (enabled) Dispatcher flush agent is not trigger on receive events. Thus, .stat files are not touched and the caching behavior cannot be mimicked for entire flow Improved/Expected Behavior: Trigger dispatcher cache flush agent on receive in local AaaCS SDK Environment Details (AEM version/service pack, any other specifics if applicable): AaaCS local SDK Customer-name/Organization name: Brillio 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.
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.
