Build better products with our product team
Hi Team,There is no way to know which user made latest changes to "resources" while we create a development build. Please add a "Modified By" field as wellWould request your team to add it.Best ,
Request for Feature Enhancement (RFE) Summary: When using property predicates in the search rail, it shouldn't matter what listOrder they are assigned and that listOrder shouldn't change how the query. Currently, some listOrders make the query search on every property and other listOrders correctly searches for the term on the property it points to. Obviously the location of the search facet in the search rail should not change the query. For example, a listOrder of 35 gives this query: xpath: /jcr:root/content/dam//element(*, dam:Asset)[(jcr:contains(jcr:content/metadata/@nord.row.item.brand, 'nike'))] and searches for "nike" in the jcr:content/metadata/nord.row.item.brand metadata field. However, change the listOrder of the search facet to 36 and the query changes to: xpath: /jcr:root/content/dam//element(*, dam:Asset)[(jcr:contains(., 'nike'))] and search on ALL metadata fields for "nike." This is obviously a bug, but the support team told me to open an enhancement ticket - you can find the ticket under: CQ-4332860. Additionally, if you check both the case insensitive and partial search options, the search doesn't work at all for property predicate fields. I believe this is already an acknowledge bug though. Use-case: Clients would like to search for metadata using the property predicate and only have results for that metadata property Current/Experienced Behavior: Currently, some listOrders make the query search on every property and other listOrders correctly searches for the term on the property it points to. Obviously the location of the search facet in the search rail should not change the query. For example, a listOrder of 35 gives this query: xpath: /jcr:root/content/dam//element(*, dam:Asset)[(jcr:contains(jcr:content/metadata/@nord.row.item.brand, 'nike'))] and searches for "nike" in the jcr:content/metadata/nord.row.item.brand metadata field. However, change the listOrder of the search facet to 36 and the query changes to: xpath: /jcr:root/content/dam//element(*, dam:Asset)[(jcr:contains(., 'nike'))] and search on ALL metadata fields for "nike." This is obviously a bug, but the support team told me to open an enhancement ticket Improved/Expected Behavior: The property predicate only returns results for the metadata field it points to. Environment Details (AEM version/service pack, any other specifics if applicable): It's been so long that we have tired to get this bug fixed I'm not even sure when we first noticed it. I believe it was around 6.5 when we switched from using the fulltext predicate to the property predicate more to get Customer-name/Organization name: Freedom Marketing. We have seen this in all of our clients on 6.5. Screenshot (if applicable): Please see ticket CQ-4332860 for screenshots and query examples Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: The rich text editor clears content out if pasting content in while a table is present in the RTE. Use-case: Improve user experience when building Adaptive Forms Current/Experienced Behavior: Steps to reproduce: 1. Create adaptive form.2. Add "Text" component.3. Click the pencil icon to change the bar to the edit bar.4. Click the maximize icon to access the full wysiwyg editor.5. Add a table with some data.6. Paste some information into any part of the component. The result I get is the table is removed. However, by clicking the undo button, the table appears again with the pasted content. It is almost like something extra is running after the paste that triggers the removal of the table and the editor sees that as another step that was taken by the user. Improved/Expected Behavior: Pasting content should not remove existing content Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.9 Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
The proofHQ settings has no way to batch user settings which makes it nearly impossible to manage system level settings for which kinds of proofs users get when you have many users.
It would be great if we could have a checkbox option that would allow certain users, usually the final reviewer/approver or original requestor to approve the final, clean, approved proof/file. Currently, you only have the option to disable this feature completely.We'd like to automate the ability to deliver final, hi-res files to the requestor, but not have them download files that haven't gone through the review process.
LOVE the ability to add images/screenshots to Updates, but it would be great to then have the option (checkbox?) to also sync the image file to the Documents Tab.Our design team just wrote their update back to our production team and attached the image file requested there. The next step in the process is to have our PM team send to the submitter for review - what needs to happen now is our PM has to download the image locally and upload to the Documents tab - would be great if the designer had the option to already do this, however it is not needed at all times especially where someone is using a screenshot as an illustrative point.
Currently in the New Workfront Experience there is no place for request and review users to see updates they have been tagged in and documents they need to approve in one place. In Workfront Classic, request and review users have a tab in the global navigation bar called My Updates. This is where they go to see their pending document approvals and recent updates they've been tagged in. They have the ability to approve or reject documents from this page AND they have the ability to reply to updates from this page. They can also see which projects the approvals and updates are associated with. I'm very concerned that this is not currently a feature in the NWE. I've considered workarounds, but something like a dashboard is not going to be clean and organized, and users won't have the ability to reply to updates or approve documents from a dashboard. When it comes to Home, at least for request and review level users, they can only see document approvals from this page which only applies to our review users and is only a small piece of what they need to see. I'd appreciate your vote to bring something like the Classic My Updates tab to the New Workfront Experience. Thank you, Sydney
Add Grouping/Filter/Sort options to the Approvals Dashboard Users have requested to group proofs requiring their approval by Project, Project OwnerFilters to filter out ‚Äòlocked’ proofs, proofs for ‚Äòcompleted/cancelled/deleted’ projectsSort options by date
We recently attempted to use the Cumulative Sum function in Adobe and discovered it basically doesn't work.the idea would be update the Cumulative Sum function to dynamically adjust to the report that end user is reporting.so if the dimension in the table are based on Day, then the cumulative function would just sum what is in the table. Similarly to how the Column Sum function works.the order should should adjust for however the table is sorted - so if we sort by day, then the Column Cumulative Sum would sort by day. If the table was sorted by visitors then the Column Cumulative Sum would sort by Visitorsthis should also work acrossDayeVarssPropsSegmentsas long as all of the appropriate details are available in the table I'm working in Workspace.
I was just notified today via a support ticket that you can no longer set a default Sort Order in a custom view. I have no idea why this option would be removed and I think it needs to be put back ASAP.
Please increase the SAML certificate expiration to 5 years. This duration is widely excepted.
We've consolidated all threads related to setting default options into this thread, including:All settings: https://forums.adobe.com/ideas/10122Report suite: https://forums.adobe.com/ideas/10194Default metrics: https://forums.adobe.com/ideas/10528Freeform settings: https://forums.adobe.com/ideas/9151Color palette: https://forums.adobe.com/ideas/10666Anomaly detection on/off: the start of this thread___Original ask for Anomaly detection on/off:It's fantastic to have gotten anomaly detection in Workspace in today's release. One point of feedback however would be that the function should be off by default when adding a new metric, with an option to turn it on.The reason we believe this is, workspace is used by a variety of end users throughout our organization (from technical to non-technical). For some of the non-technical users seeing an exclamation mark or anomaly has the potential to cause confusion and spurious concern. We therefore believe that having the default as off, would allow the anomaly detection to be more appropriately managed and used within our organization.Thanks in advance,Rory
Trivial quality-of-life request: currently, when editing a form field's label in HTML inside the Forms 2.0 editor, the focus in the form editor goes back to the field in question after updating the label. This behavior does not occur if the user is editing visibility rules; rather, once an update has been made, focus returns to the very top of the form. Could this please be updated to act the same way as label changes? This can be rather annoying on longer and more complex forms.
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.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK