Product Communities

I would like to add usage metrics to Views, Filters, and Groups within the Setup menu. I'm working on cleaning up our Workfront instance and we have a lot of custom views/filters, and groupings made by users over the years and I'd like to see which ones are utilized. With reports I can see metrics like:Total ViewsViews this MonthViews this YearViews last YearViews this Quarter Views last QuarterI was able to clean up a lot of outdated reports and dashboards and I'd like to do the same here as well.Thanks,Ryan

Any time marked as Out of Office on your Outlook calendar should show on your Time Off calendar and vice versa. At the moment users have to track in two places because Outlook is used by the company to see meeting availability and Workfront is used by PMs and Managers to capacity plan.

Likes werden momentan nur als extra Info angezeigt. Es wäre sinnvoll wenn man die Fotos nach Likes sortieren könnte und man sie auf den ersten Blick in der Übersicht sieht. Hintergrund: Ich sende dem Kunden einen Link mit Wasserzeichen von 200 Fotos. Der Kunde LIKED 50 Fotos, die er behalten möchte. Ich sortiere die Fotos sofort nach likes & kann mit dem Bearbeiten beginnen.

Derzeit kann ich einen Link erstellen, und die Fotos so ohne persönlichem Kontakt an die Kunden übergeben. Es gibt aber Schwächen. 1. Die Fotos können nicht in voller GB / Größe vom Kunden heruntergeladen werden. Insofern ist der Link nicht nützlich. 2. Der Download ist nur je Foto einzeln auswählbar. Das nimmt Zeit, man sollte gleich in der Galerie mehrere Fotos auswählen können. Hintergrund: Wenn das funktionieren würde, würde ich mir enorm viel Zeit ersparen. Es wäre alles in einer App erledigt & schön sortiert.  

Ich bearbeite am IPad meine Fotos, leider ist es aber nicht möglich ein Foto zu fixieren, um den gleichen Bildlook erzielen zu können.

When requesters/document reviewers are working with Documents on a project, there are two things they are interested in: 1. Seeing the document (and being able to open the Proof) and 2. Reviewing/replying to Updates about that document.Users express frustration that you have to click between the Details page and the Updates page when working with a Document. The Details page shows them a great thumbnail of the document but then they need to click away from that in order to post an Update or reply to an Update.It would be great if next to the thumbnail, the Updates stream could be visible, with capability to post new Updates or reply to Update threads.

When a document is uploaded to a project space, an update reflects this. However, there is no information provided to indicate which folder or location the document is located. Therefore, the document could be stored in any task, issue or document folder. The information provided in an update should therefore include the location of the document.

When working in an instance with more than one workspace, the reports in the analytics section will only provide an overview of the workspace the report is created in. It would be great to have a cross-workspace report where you can easily combine all the information into a single report, e.g. for people who work in a global / crossdivisional role.

Request for Feature Enhancement (RFE) Summary: There is an OOTB function CQ.I18n.getDictionary() to get translations, but it always gets the whole dictionary to the UI, which puts much load on the visitor's browser. This reuest is to provide a function that retrieves only the requested translations. E.g. it could accept key name(s) and language name as parameters. Use-case: Use localized strings in custom JS code on user-facing pages. Current/Experienced Behavior:   Improved/Expected Behavior:   Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 with SP8 Customer-name/Organization name: Veeam Software Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Rollout and publish the rolledout pages. Use-case: A feature in the OOB toolbox that will enable the authors to rollout a page. As a summary of the rollout we need to display which are all the pages that are affected along with a publish button by the side of the list. Rightnow, the author is unaware of what are the pages that affected by the rollout. Publishing each page after the rollout is very difficult. Current/Experienced Behavior: we dont have an option in the sites.html to rollout a page.  Improved/Expected Behavior: We need to check if the page is a blueprint or not and conditionally display a button that says "rollout and publish". Once rollout operation is completed the author should be able o see a list of pages affected by the rollout and need a publish button so that the rolledout pages can be published without hastle. Environment Details (AEM version/service pack, any other specifics if applicable):  

Request for Feature Enhancement (RFE) Summary: Component specific client-library in ui.frontend project and better dependency management for client libraries. Use-case: 1. Currently, all the code written in ui.frontend will be bundled as 2 client libraries i.e: clientlib-site and vendors. These client libraries will be loaded in all pages. There is no way to selectively load only certain components OOTB. This leads to sub-optimal lighthouse scores because unused CSS and JS code on page. Hence, there has to be modularity in the clientlibs generated from ui.frontend project. This can be achieved through proper webpack configurations 2. Currently there are two ways to load client libraries i) At template level: This is recommended because it ensures all CSS wil be loaded at the top (in head) and all JS will be loaded at the bottom. But this gives rise to unused JS and CSS code on page as there is no option to include only those clientlibs which is needed on a particular page. ii) At

Request for Feature Enhancement (RFE) Summary: When trying to move or rename a not-published page, authors without publish permissions can successfully move/rename the page, but it enters a "Request to complete Move operation" workflow. Authors who depend on using workflows on their pages cannot use a workflow on the page as they normally would until they contact an administrator to intervene. Authors who do not depend on workflows are confused by the workflow.   When trying to delete a not-published page, authors without publish permissions can only kind-of delete a page. The page appears to be deleted in the list of pages and some site navigation, but is not actually deleted. It can still be viewed by going directly to the URL. Its name can never be reused without contacting an administrator for intervention.   Steps to reproduce:   1. Create a new user that has read+write, but not publish access to wknd demo or other site 2. Impersonate this user 3. Create a n

The only class that is specific to the field type is on the input element itself, but I want to style the LABELS of the inputs differently depending on the type. I could probably even manage if I could switch the label in the DOM to come AFTER the input using input[type=...] ~ label... but you know what would be easier??... including a class on the wrapper... PLEASE!! e.g. <div class="mktoFieldWrap MKTO-FIELD-SELECT"> ← ADD A NEW CLASS HERE!!! <label for="foo" id="Lblfoo" class="mktoLabel mktoHasWidth" style="width: 100px;"> Select one:</label> <div class="mktoGutter mktoHasWidth" style="width: 10px;"></div> <select id="foo" name="bar" aria-labelledby="Lblfoo" class="mktoField mktoHasWidth mktoValid" style="width: 150px;" aria-invalid="false"> <option value="">Select...</option> <option value="foo">Foo</option> <option value="bar">Bar</option> </select> <span id="foo" tabindex="-1" class="mktoIn

Would like to enhance the UI of a large dropdown list so users know that it's searchable. For example: pre-populate the beginning drop down field with the words "start typing" (or another indicator) to prompt users to begin typing their choice so they know it's possible to search via text and their only option isn't to to sort through 100s of entries using drop down function only.

Sometimes, we will want a task to have to be approved by any 2 individuals out of a larger group. For example, there are 5 people who can potentially approve a task, and we consider the task to be approved after any 2 of those people (doesn't matter who) have approved.Right now, it seems to be "all or nothing". You can check the box for "Only one approval decision required", or you can uncheck it and then everyone needs to approve. Instead of having this checkbox, it would be great if we could specify the number of decisions required.It would be even better if you could also set this within each approver group. For example, a task needs to be approved by both Team A and by Team B. Team A requires 2 of its people to approve and Team B requires only 1 of it's people to approve. The advantage of this that, when new people join a team, you can just add them to the team, versus adding them as an individual approver on a bunch of tasks.

When creating a Template from a Project, Issues should carry over into the Template, just like Tasks , including assignments.

When looking at a Project's Task list the arrow inside the Name column has a very tiny hit box making it easy to mistakenly click either the Name title label or select the row. Increasing the hit box to make it easier to click the arrow would be idea.

I'm struggling with getting some of my users to use the Work List. I've run into a number of situations where users weren't aware they had any tasks to work on because they didn't specifically have Tasks AND Ready to Start selected.In an example scenario, when Approvals (1), Working On (4), and Ready to Start (4) are checked, only the Approval displays. I was told this is because Tasks would also need to be selected. What I would like to see, and what would be helpful for our users, would be if the filters are arranged into subgroups vs a seemingly random order, for instance:Approvals (8)Tasks (32)Ready to Start (16)Working On (4)Not Ready (4)Complete (8)Requests (12)Ready to Start (1)Working On (4)Not Ready (4)Complete (3)Personal (3)Ready to Start (1)Working On (0)Not Ready (0)Complete (2)

Description - Ability to view the S3 configuration that is set up as destination to Adobe Campaign.Why is this feature important to you - To troubleshoot or even to know which bucket you are sharing segments for Campaign, you can easily find details of the destination account. How would you like the feature to work - When you browse the account, click on edit account details should show the bucket name and folder path. Current Behavior - Not able to see the destination account besides the access key. Understand the access key is associated with a specific bucket, but people don't remember the bucket name by its access key. 

The "handle" to increase the width of a column in a table view is very small and makes it hard to quickly grab and adjust the width of a table's column. Increasing the targetable area would make adjusting the columns much easier.

Looking to see if a indicator can be added as the first column to a rule to show what kind of "Event Type" the rule has. Something on the lines of what Adobe Target currently offers for their different types of activity.Additionally if a filter can also be created to narrow down all page load rules, DCRs etc besides the existing ones (Status:Enabled / Disabled), that would be great.

There is a FUNDAMENTAL NEED to have a year over year percent change column for metrics listed vertically (in the order we want them listed) with current year first, prior year second, % change column third For example: metric name:           Period A current year totals :              Period B prior year totals :             % change differencemetric name:           Period A current year totals :              Period B prior year totals :             % change differencemetric name:           Period A current year totals :              Period B prior year totals :             % change differencemetric name:           Period A current year totals :  &nbsp

Description - WORKSPACES IS VERY USELESS WHEN TRYING TO LOAD LARGE AMOUNTS OF DATA TO BE DELIVERED IN SCHEDULED EMAILSWhy is this feature important to you - THE COMPANY STAKEHOLDERS NEED TO SEE ALL THE DATA  THEY WAY THEY WANT TO SEE IT AND NOT JUST WHAT ADOBE WANTS TO SHOW THEM IN HOW ADOBE WANTS TO SHOW IT IN SCHEDULED EMAILSHow would you like the feature to work - GIVE US THE ABILITY TO RETURN AS MANY ROWS AS WE WANT TO SEE IN WORKSPACE REPORTS SETUP TO DELIVER AS SCHEDULED EMAILS AND/OR GIVE US THE ABILITY TO SORT DATA IN DESCENDING ORDER IN DATA WAREHOUSE.Current Behaviour - WE CAN ONLY RETURN 400 ROWS IN AUTO EMAILED REPORTS. AND TRYING TO SEND DATA WAREHOUSE REPORTS FOR INTERNAL SEARCH TERMS WITH INTERNAL SEARCH COUNTS IS USELESS BECAUSE DATA WAREHOUSE WILL NOT GIVE US THE ABILITITY TO SORT IN DESCENDING ORDER, IT JUST RETURNS UGLY REPORTS AS ZIP FILES THAT THEN HAVE TO BE OPENED AND SORTED MANUALLY.  MY REPORTS GO TO COMPANY OWNERS, THEY PAY A GOOD AMOUNT OF MONEY FOR

Hello Team,We identified that Report filter "does not contain" allows only 1 word. Request you modification in the filter so that it allows multiple option to enter word.Best Regards,Pranav Kulkarni

Description - Ability to send email notifications to the subscribed emails when the data flow run fails or succeeds.  Why is this feature important to you - It is easier to set up alerts for data flow monitoring via email inbox instead of logging to console and check for status. How would you like the feature to work -  Allow the ability to set up an alert based on flow name or by status and subscribe to individual or group email ids. Email notifications should be delivered to their inbox.  Current Behavior - Currently the subscribe option sends alerts to the UI and you need to be logged into AEP to view the alerts.