Build better products with our product team
We’d like the ability to restrict an issue custom form so it can only be used as part of a request queue, not added manually to an issue. It would help enforce the process to require users to use the request queue.
It would be nice if system admins had additional control on the date fields. Some of the enhancements for the date field should include:Limiting dates before the current date or a set number of daysLimiting dates after the current date of a set number of daysCreating date dependencies/rules between dates on the form.
When we do exports, the subject line is not accessible via a workflow.It is a real issue for doing reports.
Since Adobe runs our AEM environment in AWS, we would like Adobe to make use of the AWS security features for my company. Here’s the specifics:We want to use AWS STS to manage access to the companies Cognito service in AWS to get access to a JWT. This is instead of using CryptoSupport.We would like to make use of AWS Secrets Manager and/or AWS Parameter Store to protect sensitive data. We would like to use a Customer Managed Key provided by the customer for Secrets Manager and Parameter Store.Our objective is to not allow developer or Adobe support personnel from seeing any sensitive items like a password, api key, access credentials. Since AWS has services that meet our needs, we would like Adobe to expose those services to us through the AEM authoring / administrative tools.
When we add absolute image url with preset having $, the css file will not load and throw exception from OOB code (com/adobe/granite/ui/clientlibs/script/Utils.java). But by escaping $ we can overcome above issue and load the css file with preset correctly. .load { background:url("https://scene7.image.com/is/image/adobe/someimageutl?\$native\$");}
WHAT WE HAVE In AEM x.x.x version we have mechanism to check duplicate images being uploading in DAM which is supported by unique SHA1 value.This verification process is done during uploading of new Assets. 1. By enabling duplicate OSGI asset service 2. OOTB mechanism is the SHA1 value check. Currently , other way of achieving similarity/ identical is by using Sensei which will be based on tags but this process is again done AFTER successful Asset upload and enabling of SMART tags to specific folders. WHAT WE DO NOT HAVE We do not have mechanism where a Author WHILE uploading can know if there is any similar / identical assets i.e. Assets which have been cropped or change in color shade etc. This should not be related to any property value check or SHA1 value instead check the pixels or any other parameter. AUTHORING Challenges use caseIn our current system we have thousands of pages with images of business leaders with different dimensions / cropped belonging to different departments.The challenge for AUTHORS is if any leader resigns then his/her photo needs to be updated for the corresponding pages which can only be done after uploading a new photo in DAM. There is no way they can identify the pages where this new photo matches and then take necessary actions. The only one way they can achieve is by enabling SMART tags to the folders and then do Asset Search which is again driven by Tags.With our traditional approach of managing sites this is not possible mostly.
Creating adaptive forms via drag and drop bricks with a straight forward visual feedback (a bit like wufoo.com does, but adaptive!) – wouldn’t that be cool ?
Hello Team, We are using AEM 6.4.2 integrated with Dynamic Media. Here to fetch the URL of synced asset we are using com.day.cq.dam.s7dam.common.utils.PublishUtilsImpl.externalizeImageDeliveryAsset() by passing the resource object of the asset. We are seeing the unclosed resource resolver issue in logs. Please suggest. Any other way to fetch the DM published URL if not above? I suspect that in "com.day.cq.dam.scene7.impl.Scene7AEMBridgeImpl" resourceresolver might not be closed after processing. 14.10.2020 02:20:14.950 *WARN* [Apache Sling Resource Resolver Finalizer Thread] org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl Closed unclosed ResourceResolver. The creation stacktrace is available on info log level.14.10.2020 02:20:14.950 *INFO* [Apache Sling Resource Resolver Finalizer Thread] org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl Unclosed ResourceResolver was created here:java.lang.Exception: Opening Stacktraceat org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl$ResolverReference.<init>(CommonResourceResolverFactoryImpl.java:521) [org.apache.sling.resourceresolver:1.5.34]at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.register(CommonResourceResolverFactoryImpl.java:218) [org.apache.sling.resourceresolver:1.5.34]at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.<init>(ResourceResolverImpl.java:101) [org.apache.sling.resourceresolver:1.5.34]at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.<init>(ResourceResolverImpl.java:94) [org.apache.sling.resourceresolver:1.5.34]at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.getResourceResolverInternal(CommonResourceResolverFactoryImpl.java:263) [org.apache.sling.resourceresolver:1.5.34]at org.apache.sling.resourceresolver.impl.ResourceResolverFactoryImpl.getServiceResourceResolver(ResourceResolverFactoryImpl.java:96) [org.apache.sling.resourceresolver:1.5.34]at com.day.cq.dam.scene7.impl.Scene7AEMBridgeImpl.getServiceUserScopedConfigResolver(Scene7AEMBridgeImpl.java:188) [com.day.cq.dam.cq-dam-scene7:5.11.108]at com.day.cq.dam.scene7.impl.Scene7AEMBridgeImpl.getS7configFromResource(Scene7AEMBridgeImpl.java:138) [com.day.cq.dam.cq-dam-scene7:5.11.108]at com.day.cq.dam.scene7.impl.ImageUrlApiImpl.getImageServerDeliveryURL(ImageUrlApiImpl.java:113) [com.day.cq.dam.cq-dam-scene7:5.11.108]at com.day.cq.dam.scene7.impl.ImageUrlApiImpl.getImageServerDeliveryURL(ImageUrlApiImpl.java:82) [com.day.cq.dam.cq-dam-scene7:5.11.108]at com.day.cq.dam.s7dam.common.utils.PublishUtilsImpl.externalizeImageDeliveryAsset(PublishUtilsImpl.java:260) [com.day.cq.dam.cq-dam-s7dam:5.11.168] @kautuk_sahni @vanegi @joerghoh @arunpatidar @dan_klco @hamid1350
Hello,I am trying to install either experience manager or livecycle onto my MacBook Air. I currently use Adobe Acrobat Pro. Can someone please help me?
I recently had the experience of a guest user gaining unauthorized access to my account when I inadvertently forwarded an internal proof notification. Support explained the following: "From what you are saying it sounds like those users are getting your routing link through a forwarded email, and they aren't noticing that it's logging them in as you. The URL attached to those emails is linked to your credentials for that proof, so anyone who follows the link will be entered into the proof as you. There is a setting on each proof to change that behavior by requiring users to log in to the proof, that will prevent people who ended up with your personalized link from making changes as you. This will, however, prevent unlicensed users from accessing the proof. If all of your work is done internally and you don't have to have guest users, and external users access the proof then this would be the best route. If you do need external users to have access then it would be best to not forward notification emails from proof, as they contain that personalized link." Would be possible in a future update to close this loophole by somehow referencing IP Addresses to block this type of access to guest users?
Currently, the X-Unsubscribe (the unsubscribe text link that many inbox providers display next to the email sender information) is set to use a "mailto" instruction. Often, the unsubscribe option is one of the first pieces of content subscribers will see when opening your message and the "mailto" setting means that, when clicked, an automatically generated email notice is sent to Marketo and the reader is unsubscribed from ALL future content. I'd like to suggest that the option be given for programming X-Unsubscribe URL instruction. With this method, when the reader clicks the unsubscribe text they'll be taken to a landing page to process the unsubscribe request. Namely, a Marketo landing page like our Preference Center so the reader can choose to be removed from one or more categories. This would help with attrition rates by allowing an option beyond all or nothing. Many other email service providers already offer this option and I feel strongly Marketo should as well to remain competitive.
Description - Currently, we cannot use h2 and h3 in forms and have them appear on Generated Documents of Record. We have to use panel descriptions for blocks of form inputs, and cannot use in Static Text - they simply do not show and will block out the entire text block. To enable accessible scanning of form, we need to do a workaround of a panel descriptions for the DoR, but then put in the h2 and h3 for the Adaptive Form. Why is this feature important to you - Accessibility! Screenreaders scan by header levelsHow would you like the feature to work - support for <h2> and <h3> codes and other text formatting in static text that will show on DoR so we don't have to generate XDPs for legal static text. Current Behaviour -
Description - While uploading new assets from external system, those assets might contains some metadata properties. While uploading it to AEM, it's auto generating namespace and preserving those metadata. Which we would like to prevent using this feature request if possible, Only registered namespace metadata should preserve.Why is this feature important to you - It's creating issues while doing full text search and also impacting search speed. It certainly improve the system performance.How would you like the feature to work - Post implementation of these restriction that only registered namespace metadata will AEM allow , when we upload any asset from any external system, it will not create unnecessary namespaces automatically into system and also no unknown properties will be part of asset metadata and full text search will work fine.Current Behaviour - Currently if we upload assets from external system , if that assets have any metadata properties, while uploading on AEM , it's creating namespace and preserve those external metadata into the system. Also while searching system is searching assets containing those external metadata, Which causes the issues.
Description - Any component that has a link field, edit dialog and click on the path finder. Search using search term or paste in a path in left rail path field to get to search results. Instead of only pages getting non-page "nodes" in the search resultsHow would you like the feature to work - When searched only pages should appear.Current Behaviour - Instead of only pages, showing non page nodes also. Thanks
Description - When a person is given Developer access they can pull and push to the Adobe Git instance for the program. There should be an option to prevent people with the Developer access to push when there is a customer Git repository that syncs to the Adobe GitWhy is this feature important to you - To prevent a customer Git repo becoming out of sync with the Adobe Git repo, there should be an option to not let people in the Developer role from pushing to the Adobe Git repo. How would you like the feature to work - Add an option to the Developer role to prevent pushing to the Adobe Git repo.Current Behaviour -
Description - We would like to create meta tags (not limited to keywords) on pages through page properties. We would also like to have meta keywords (tags currently in page properties) inherit to child pages or be able to set default tags.Why is this feature important to you - This feature would make tag management simpler and more manageable out of the box.How would you like the feature to work - Add tags through page properties in 2 sections, one for keywords and one for miscellaneous with an option to inherit to prepopulate and customize from there. For example, if a user selects to inherit tags, it would prepopulate with the parent page's mete tags. The user can then add tags or remove tags from their page as needed.Current Behaviour - Custom page properties and Java needs to be developed for this implementation of tag management
Please can you consider adding hour as as an option in the date range builder? (so it is possible to do "start of current hour" minus 1 "hour" etc.) Every other time period is available (e.g. day, week) so it is rather frustrating that we can't use hour - there are so many great things this would allow us to do! :-)
I'd like the ability to "bulk delete" Announcements and Notifications from my "View All Announcements" and "View All Notifications" screens.
When uploading a document, you can request a document approval. This is great! But, you can't assign a deadline to the document approval. We have some projects in which we just want a user to approve a document, without assigning them a formal request. Workfront allows this, but without a due date, there's no way to indicate to the user by when their approval is needed. The workaround is to indicate that detail in a directed update, but this results in the user receiving two email notifcations (one soliciting approval, and another with the directed update.) Document approvals should have deadlines just as request approvals do.
On custom forms, is there any way to create rules around an open field? Meaning using Fusion or some other technology, whatever is written in the field must follow a certain format (i.e. AA-1234)? If they don’t follow the format, it won’t push the request forward.
Description - As per current behaviour, as long as the Virtual Report Suite is Data Warehouse compatible, you would be able to run the request. However, if it is not compatible you will still be able to create the request with this VRS, with failed status and no prior warning.There should be a warning or an error message on selection of Virtual reports which are not DWH compatible. Why is this feature important to you - It is quite misleading as there are several VRS and we won't remember which all are DWH compatible and which are not. How would you like the feature to work - The VRS which are not compatible should either do not appear in the DWH interface OR there should be a warning on selection of the VRS.
We would like all the existing Adobe Analytics dimensions (eVars[1-200], props[1-75], and events[1-1000], list[1-3]) to be automatically mapped using a supported or new schema mixin. In addition, this would be needed for product syntax eVars and events. This is important for existing implementations with a significant number of custom dimensions. It will ensure customers will not have to manually map every single custom dimension via processing rules. In addition, it will allow customers that leverage the raw data feed to use the AEP SDK. At this time, only specific dimensions are automatically supported.https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/adobe-analytics/manually-mapping-variables.html?lang=en#context-data This is already supported for standard dimensions like products, commerce, and page details. https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/adobe-analytics/automatically-mapped-vars.html?lang=en#data-collection For us, the raw data feed is critical for our customer data platform and processing rules are not a viable option. We cannot migrate without this feature.
In Email Insights and anywhere else applicable, there should be an option to display the date in the International Date Format (ISO) standard format i.e. DD/MM/YY. This is in line with W3 and general usability guidelines. See here: https://www.w3.org/QA/Tips/iso-date Marketo users only have the option to use the Americanised MM/DD/YY, which is a counter-intuitive format to all users outside of the U.S. and aren't to usability and accessibility standards. Currently, the Date format showing in Marketo's UI is hard-coded in the software and cannot be changed based on one's region/instance.
As of now ACS provides ability connect to only one report suite on analytics side when you configure the ACS -> Analytics integration. If it's provided to configure more than one report suites, it will help for business using multiple BU's from ACS send data to adobe analytics for further business processes.
Description - Make the Schedule Renewal page use the Analytics page template. Currently, the page design looks like an afterthought.Why is this feature important to you - It allows users to navigate to other parts of Analytics immediately.How would you like the feature to work -E.g. include the top main menu, shortcuts to other parts of Analytics, etc.Current Behaviour - The Schedule Renewal just shows a message to renew the schedule and whether the renewal is successful or not. There are not other calls-to-action.
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.
