We need a way to create recurring tasks that have a pre-set the duration AND planned hours. You can do duration in "simple" mode and planned hours in "Effort driven" mode, but there isn't a way to create multiple tasks at the same time with both set duration & planned hours-- they come up blank (simple) or you can't change them (effort driven).
The functionality for setting up recurring tasks initially is easy to understand and set up, but the way the tasks are labeled is a chore. If I have a user who processes DCM tickets every day, I end up having them look like this: DCM Tickets 1DCM Tickets 2DCM Tickets 3 In a user report, the task names above are not helpful. Would it be possible to use the date guidelines set to create some sort of naming convention? I am basically looking for overall improvement in how recurring tasks are executed in the system.
I would like to be able to see within the document details when a decision has been made (approval/approved with changes/reject). Right now we can only see that a document has had a decision made.
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
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 - 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 - 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! :-)
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.