Build better products with our product team
Description -In Analysis Workspace when a user without Admin permission and only basic permissions to one report suite clicks the Share | Send file now menu option under the Recipients field they are presented with all users under our org (even old users who have been deleted from our org) which is a security concern. This user without Admin permissions should not see any other user names than their own. It is fine if the user manually enters in other email addresses but this user should not see other unrelated user names in our Adobe org. Why is this feature important to you -Improved security for our org so that non-admin users do not see the names of our other client users who they have no relation to and should not see. Currently we cannot open up access to the Analysis Workspace feature since our client users will be able to see the names of other client users who they are unrelated to which is not acceptable. Each client user only has access their own report suite so they should not see the names of users that have access to other report suites. How would you like the feature to work -This user without Admin permissions should not see any other user names than their own. The user only has access to one report suite so they should not see users related to other report suites or other admin users. It is fine if the user manually enters in other email addresses but this user should not see other unrelated users in our Adobe org. Current Behaviour -In Analysis Workspace in the Share | Send file now menu option under the Recipients field, the user without Admin permission and only basic permissions is presented with the names of all users under our org (even old users who have been deleted from our org).
It should be possible to make the drop-down filter items in workspace update dynamically. For example, if you want all items from the dimension "website country" in the filter, and when new countries sites were added, they should appear automatically in the filter list. This is needed because currently we have to constantly update all filters in all dashboards manually, when new items appear in a dimension. There can be several cases with website countries, languages, user company names etc.For me it would be enough when there is an option like "add all dimension items to filter" when I pull a dimension to the filter box. And then the filter should have a setting like "update automatically". Current behavior is that, when you want to add a new dimension item to an existing filter, you have to search for the dimension, choose all the dimension items again (plus the new one), and replace the existing filter. So it is even not possible to simply add the new item. For our normal Analytics users this is too advanced.
I still find it strange that I can select "In past x period" as a constraint for several filters like Was Delivered Email, but there is no "In past before x period". It would be great if these options can be extended so all relative time constraints can be used.
We create standard sections of our projects that correspond to different stages of the project lifecycle. We would like to set early stages of the project as one status (e.g. "Current") and later stages as another status (e.g. "Planning"). This would significantly help with the ability of firing the right notifications at the right time, executing on early deliverables, while maintaining the ability to build later stage deliverables without disruption. This would help with both waterfall and agile shops.
It would be great to have the ability to view colour separations within workfront proof. Similar to the output preview tool in Adobe Acrobat.
In addition to mixed media in a proof, just having more than one video or interactive element is needed. So as an of example of what our teams want is to have one proof with a video, followed by its script, another video, followed by its script, etc.
When will proof allow mixed media in one proof? (Example: a script word document and video on one proof)We have groups that can't use proof for this reason and this creates a separation between projects and proofs and ability to report.
Description - I would like the ability to view Adobe Analytics widgets/dashboards within our team chat / communication channels so we can improve awareness on trends & KPIs for all team members (product, development, performance, QA). Why is this feature important to you - It allows constant contact between the product and development teams and customer trends & behavior. How would you like the feature to work - A few ideas, one way is to leverage pre-build team workspaces, allow anyone with the workspace link to past it into the chat and return a view of the data currently (free form or chart). Additionally, being able to schedule report / chat posts. The exact integration and capabilities may depend on the chat platform (slack, teams, etc.) Current Behaviour - I can past a workspace link or pdf/excel document. Not all users have access or will open the link, cannot quickly see the data, is less visible does not spark discussion.
We would like the ability to create a logic for a field within a custom form that would determine the tasks that are populated. For instance, we have a field that says "is this project billable?" (yes or no). if "No" is selected, we would like certain tasks to not populate (ie. Creative Review, and Project Cleanup) as those tasks ARE required for all Billable projects, but not our internal (non-billable) clients.Alternatively, it would be also great to have the ability to determine which tasks populate based on which client is selected.Or BOTH of the above, ideally.
It would be great to have the ability to track admin level (global system) settings changes. Although our admin team is only a handful of people, there have been several instances in the past where settings have been changed (most likely by an erroneous click) and no one has known how they were changed. We would like to see settings tracked much like project and task field changes are tracked.
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): Customer-name/Organization name: Abinaya/Perficient Screenshot (if applicable): Code package (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 component level: This ensures that only required CSS/JS will be loaded. If a particular component is not loaded, corresponding CSS/JS will not load. But, with this approach render blocking CSS and JS code is loaded in body tag which is not recommended. Hence there needs to be an approach to fix both of this performance issues. If there can be a way to dynamically load client libs (and its dependencies) based on components present on page, this will highly improve page performance. Current/Experienced Behavior: All ui.frontend code is bundled into 1 single clientlib and is loaded on all pages Single vendor client contains many dependencies which may not be required in all pages Loading clientlibs at template level causes unused JS/CSS to be present on pages. If loaded at component level it causes render blocking calls hampering the performance. Improved/Expected Behavior: ui.frontend should have modular structure and there should be component specific client libs. Vendor clientlib should be generate dynamically to include only necessary dependencies Ability to load only required clientlibs on page at component level. Also these clientlibs need to be loaded in 1 single request. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.x Customer-name/Organization name: Mindtree Screenshot (if applicable): Explanation: Without optimization: Clientlibs loaded at component level. With optimization: I have used an interceptor to group all CSS in head section and all JS to the bottom of the body tag. Code package (if applicable):
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 new page, do not activate 4. Move or rename the page 5. Note the page is moved/renamed, but the page is stuck in a "Request to complete move operation" workflow 6. Create another new page, do not activate 7. Delete the new page, it appears to be deleted 8. Try to create a new page with the same name, observe the name cannot be used 9. Go to the "deleted" page, it is visible when it should be deleted 10. Go to the deleted page in CRXDE as administrator, it is present, but with "deleted" property I have demonstrated those steps in a video here: https://buffalo.box.com/s/94nuwdwmgyctw6fo2sfu2hb4npfze1ti Use-case: Current/Experienced Behavior: Improved/Expected Behavior: Environment Details (AEM version/service pack, any other specifics if applicable): 6.5 SP10 Customer-name/Organization name: University at Buffalo Screenshot (if applicable): Code package (if applicable):
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="mktoInstruction"></span> <div class="mktoClear"></div> </div>
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.
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.
