Build better products with our product team
Add the ability to have conditional formatting on a chart report. Ie: create a bar or column chart and if the count of any of the columns is over a specific number, the color automatically changes to red.This would be great to easily view KPIs.
Request for Feature Enhancement (RFE) Summary: Download folder without all hierarchy folders Use-case: folder download in AEM assets Current/Experienced Behavior: all hierarchy folder is reconstructed when we download a folder Improved/Expected Behavior: if we have a long hierarchy, in download process, hierarchy is not needed. We loose time to rich the assets after download Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloudservice Customer-name/Organization name: Louis Vuitton Screenshot (if applicable): Code package (if applicable):
Allow hiding milestones when they are no longer relevant, without removing them from the milestone path to preserve historic data.Just like the functionality to hide/unhide options in a dropdown field, I suggest implementing a similar feature for milestones. This would keep our milestone paths clear and concise, and eliminate the need to create new milestone paths.Additionally, the milestones view on the project page should be made more flexible as the current layout appears rigid and outdated.
Currently, there is no single place users can go to see their time off based on their schedule AND the time off they have personally opted to take. Displaying the time off from the user's schedule would make it much easier for them to manage their pto.
Description - When can we expect Workfront to have an AI Bot to assist PMs and System Admins with managing projects and instances?Why is this feature important to you - to alleviate the workload on plan license users.How would you like the feature to work - like ChatGPT bots Current Behaviour -
Request for Feature Enhancement (RFE) Summary: As an end user, when I use the download component on a page, then I should be able to see the file size of the document up to 1 decimal point(at least) or a configurable number of decimal points. Use-case: Display exact size of the document to the end user. Current/Experienced Behavior: The file size is rounded to the nearest GB(or KB, MB) Improved/Expected Behavior: The file size should display correct value up to at least 1 decimal. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS 2021.12.6145.20211216T083234Z. WCM Core Components - 2.17.12 Customer-name/Organization name: Abbott Screenshot (if applicable): Code package (if applicable):
I recently learned that the lifespan of my data in the Adobe Target visitor profile is a max of 90 days (default is 14 days). This is too short! I work in a business that drives toward one day a year - we have one transaction per client per year, but their likely-hood to convert similarly year over year is very high. Can this lifespan be extended to a max of at least 12 months (24-36 would be amazing)?
Request for Feature Enhancement (RFE) Summary: Currently when users have to select assets or folders, they need to hover over for the small tick on the left-corner of a folder (in card view). Use-case: The current approach is not user-friendly and time-consuming. For examples, editors have to select 50 assets out of 800 within a folder. Usually the editors use 'card view' which ensures a thumbnail preview of the assets. Editors then have to select each asset by clicking on top-right corner of each one. Current/Experienced Behavior: Currently when users have to select assets or folders, they need to hover over for a small tick on the left-corner of a folder (in card view). Improved/Expected Behavior: More user-friendly way of quickly selecting assets or folders. A big hover-over enabling the selection of assets or folders. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets as a cloud service Customer-name/Organization name: Hugo Boss Screenshot (if applicable): Code package (if applicable):
Background: When an Exclusion is set up there are two options:1. "Add Exclusion" The end result is you get a container that you can drag into in order to correctly exclude an audience.2. "Exclude this Audience" This option adds All Visitors back into the audience and then only removes the audience that you had selected.The first option works as expected and should be left in place. However the second option is confusing and redundant (Everything it does can be accomplished out of the box by only have one “Add Exclusion” option with an audience of choice.)Feature: Please remove this second option from the interface as it is adding a lot of confusion when setting up exclusions.
Missing DOCTYPE declaration on a webpage often disables the Adobe Target library, without which the personalization is not possible on your site pages.Target library at.js requires the HTML5 doctype. The syntax is: <!DOCTYPE html>.HTML DOCTYPE must be the very first thing in your HTML document before the HTML tags. It acts as an instruction to the web browser about the version of the markup language in which the page is written.Initially, the Doctype declaration was used in HTML when it was defined as a language based on SGML and later XML. Since the presence of that declaration was in general a signal that the document author followed the standard practices and then this declaration was used in HTML5 to distinguish between standards-complaint parsing mode and a so-called quirk parsing mode.The HTML5 doctype ensures that the page loads in standard mode. Some JavaScript APIs gets disabled when a site page loads in quirks mode. Target library also depends on some JS APIs which gets disabled with quirks mode. Whether the document is parsed in standard mode or quirks mode, or simply parsing the same way across HTML5 processors, the doctype is a critical component of a quality HTML document.In the past, the declaration was passive – ignored by the browser until you’d validate the document where the validator would use the DOCTYPE declaration to compare your document with the declared Document Type Definition (DTD). But with the technology known as DOCTYPE switching has made using the correct DOCTYPE declaration not only important, but imperative. On finding a correct DOCTYPE in the document, browsers allow page to render in standard mode.The idea here is to -understand how important is DOCTYPE Declaration on a webpage,what makes up a correct declaration, andmost importantly, including the correct DOCTYPE declaration in a page is required to enable Target libraries effectively.Hope this helps!Thanks,Khushboo Kalia
Missing DOCTYPE declaration on a webpage often disables the Adobe Target library, without which the personalization is not possible on your site pages.Target library at.js requires the HTML5 doctype. The syntax is: <!DOCTYPE html>.HTML DOCTYPE must be the very first thing in your HTML document before the HTML tags. It acts as an instruction to the web browser about the version of the markup language in which the page is written.Initially, the Doctype declaration was used in HTML when it was defined as a language based on SGML and later XML. Since the presence of that declaration was, in general, a signal that the document author followed the standard practices and then this declaration was used in HTML5 to distinguish between standards-compliant parsing mode and a so-called quirk parsing mode.The HTML5 doctype ensures that the page loads in standard mode. Some JavaScript APIs gets disabled when a site page loads in quirks mode. Target library also depends on some JS APIs which gets disabled with quirks mode. Whether the document is parsed in standard mode or quirks mode, or simply parsing the same way across HTML5 processors, the doctype is a critical component of a quality HTML document.In the past, the declaration was passive – ignored by the browser until you’d validate the document where the validator would use the DOCTYPE declaration to compare your document with the declared Document Type Definition (DTD). But with the technology known as DOCTYPE switching has made using the correct DOCTYPE declaration not only important, but imperative. On finding a correct DOCTYPE in the document, browsers allow page to render in standard mode.The idea here is to -understand how important is DOCTYPE Declaration on a webpage,what makes up a correct declaration, andmost importantly, including the correct DOCTYPE declaration in a page is required to enable Target libraries effectively.
That will be helpful if there is a feature to upload multiple files in the file resources. There was a solution given in forum - uploading file from ftp then loop back: I want to Upload images to Public resources every morning. Is it possible to automate this process. I achieved this using a workflow - I asked a question in forum and fixed the issues that I faced: Copying file to '/usr/local/neolane/nl6/var/&lt;instance_name&gt;/&lt;file_name.extension&gt;' However, if there is a native method, that will be really helpful as that will reduce human work.Thanks,Somasundaram.
There are use cases where we need to have multiple proofs open at the same time. In the browser, this is not an issue at all, but now that we are doing Interactive proofs, this is becoming an issue. Use cases: User has two monitors and would like to compare versions that way then really tall and thin in one monitorUser is looking at a proof that is similar but not related to the current proof about some global settings for the brand and what was doneThere is an issue with the integration and a proof is create independent of the other versions so both need to be open to compare.They are waiting on a comment from someone else and while waiting they are working on something else. They don't want to lose the proof though so they don't forget about it.I'm sure there are more, but that is all I could think about.
It would make sense and be very helpful if a team that shares a mailbox to monitor emails for their team, could submit those request to Workfront from that shared inbox. Currently, our teams are forwarding the emails to their primary inbox to use the add-in OR manually entering a request into Workfront based on the email received in the shared inbox.
Having the source/reason attributes set to dynamic chat for the updates made by dynamic chat will help us filter on the field values updated specifically by the dynamic chat in the SL/triggers. Currently the source in the field updates made by dynamicChat in activity shows Web Service API, it’d be great if we could say if the values were updated by the dynamicChat specifically. Additionally, it'd also be great if dynamic chat is added as one of the input sources that we could check-mark to block updates in the field management section on the respective fields, if need be. There could be use-cases where we would wanna capture the data from dynamic chat for a new person but not update if there's already a non-empty value present on an existing person in the Marketo.
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