Build better products with our product team
We routinely have to do grouping when making our illustations in Adobe Illustrator. That can be over several thousand objects, grouped into bunches of only 50 or less. It would be much more resource-efficient to have a module that can do the grouping of connected or overlapping objekts on the whole page automatically.
When there is more than one user in the same workflow/delivery/object in ACS, either a lock should be added or a notification should be sent. Recently, we have encountered two issues where changes are not saved correctly in live campaigns due to overlapping resources. As a result, changes are not saved properly and the client program is experiencing errors.Below is the error that we get when the workflow/delivery has an error:PGS-220000 PostgreSQL error: ERROR: canceling statement due to user request Multiple users working simultaneously on the same workflow/delivery get aborted, resulting in the client's campaign being delayed, affecting their revenue.
Description: Persistent row (aka job, report) and column filter Why is it important? The DWH export feature is being used for scheduled and ad hoc exports and therefore it's the home for a lot of entries, mixing up all kind of requested exports for all kind of purposes, this also requires "speaking" request names which are sometimes quite long; as there are too many columns, the request names are cropped - too many rows and too many columns requires to (de-)select unnecessary columns and row filters How should the feature work? the UI should remember the filter I selected and columns i (de-)selected Current behavior: If you (de)select particular columns or filters from the right sidebar, right after you added a new job or editing an existing one and get back to the list of all jobs/reports, all jobs/reports and columns are displayed again
Hi there, Our team was surprised to find that there was not a merge profiles function on the tool. This was a feature of Campaign Classic, however we found that there are many data issues as a result of not having that function. We have thousands of duplicate profiles on our org's instance of ACS. The unique identifier was not set as the email originally and now we have the issue of users unsubscribing and still being on the email communications because they have several profiles under the same email address in our system. I had heard rumors that this was going to be an addition to one of the updates, but I have yet to see any official statements on that function. I would think this is a basic need across all organizations. Please let me know if there is any development on this!Thanks,- Mike
It'd be great if there was a built in URL shortener in Adobe Campaign, specifically when using SMS. Since SMS only uses 160 characters, every character is important. It'd be great if there was configuration options as well, to determine level of tracking needed and how many characters would be needed.
It would be great if inside ACS there was the ability to add Superscripts and Subscripts for like trademarks, copyright symbols, etc.
Description - API endpoints to pass email template or email message HTML (and associated metadata) to ACSWhy is this feature important to you - Many companies increasingly use an Email Creation Platform like Stensul for email creation and collaboration, and then want to automatically push the finished html (via API) into Adobe Campaign Standard for deployment.How would you like the feature to work - similar functionality to the Marketo Emails and Email Templates API endpointsCurrent Behaviour - n/a. a user has to copy and paste html into ACS thank you!
Our organization aims to determine the most common times of day when users open messages from specific campaigns. We want to know whether they tend to open them in the morning, early afternoon, late afternoon, or other times.When creating a report, we have Time dimensions available for Day, Hour, Minute, Month, and Quarter. However, the Hour dimension currently only specifies the hour of a particular day (such as 9:00 AM on April 1, 2023), not the hour of a general day (such as 8:00 AM - 8:59 AM)
Right now, if we are on a Task, and we convert that task into a Project, as soon as we do that, the original task is deleted. The request is the following:We are in Project A, and we have Task number 1.We are in Task Number 1 and convert that Task into Project B.The Task number 1 will remain in Project A.User will update the progress/status of the Project B.Automatically update the progress/status of task 1 in Project A. Regards.
DescriptionWhile our users try to adhere to standard naming conventions for Target activities, the names are not fixed and may be adjusted throughout the lifecycle of the activity (Development, QA, Production, Completion). The only permanent identifier seems to be the Activity ID, however it is also useless because you cannot search by it.Why is this feature important to youBeing able to search by Activity ID would also give us a permanent way to refer to activities in other documentation where it would be impractical to keep updating the name.Please note that changing the name of the activity based on the status of the activity before and after launch was a recommended approach from our Adobe consultants. How would you like the feature to workEnter the activity ID in the Target UI activity search box and return the specified activity.Current BehaviourThe search tool only works with activity names at the moment.
Make instances an available metric for data warehouse reporting. If it's in the regular UI it should be in DW too.
Description - Enable / Disable Event Notifications on Subgroups Why is this feature important to you - This will help group admins to customize Event Notifications for all groups they manage, not just the top-level groups. How would you like the feature to work - When the Email Notification is unlocked at the Setup level, the Subgroup level Event Notification would be unlocked as it functions for top-level groups. Current Behaviour - The Event Notification remains locked for subgroups.
Description - On the homepage, the widget names are hard-coded, but different things mean different things to different people. From organization to organization, from role to role, and from functionality. It would be great to be able to customize it and enhance the user experience.Why is this feature important to you - This creates a higher adoptability as the user will be able to understand the views as it relates to their job role and function, My Work, for example, could be priorities. How would you like the feature to work - To be able to customize the naming widget to whatever the user wants to name it, but the ability in settings to be able to see what the original Widget applied (for troubleshooting).Current Behaviour - The name of the widget is hard coded to what has been established by Workfront which doesn't translate as well for all users. We need the ability to customize.
Description:We recently faced an issue with the request conversion to template. After conversion, the relationship was removed either as human error mistakenly or on own. The same was fixed by restoring the relationship. We were wondering if there were any log system to keep notice of changes made in the details section of the project or task. This issue has been repeated twice the last week.Why is this feature important to you:This will prevent accidental changes to requests and projects as well.How would you like the feature to work:Either the changes made by person's name to be shown in the current system activity or separate log for the same.Current Behaviour: There is audit log and system activities for changes. But it does not work on the details section.
Description - OAuth authentication to Adobe Experience Cloud applicationsWhy is this feature important to you - Use OAuth to connect to AEC applications. A JWT private key has an expiration date and needs to be refreshed.How would you like the feature to work - A connection within Workfront to an AEC product (AJO/Target) should us OAuth instead of a private key. OAuth does not use a private key to exchange for a bearer tokenCurrent Behaviour - To obtain a bearer token a private key is required.
Request for Feature Enhancement (RFE) Summary: Cache ContentPolicy lookup in WCMBindingsValuesProvider Use-case: Currently the implementation of WCMBindingsValuesProvider performs a lookup of the policies, but does not store the result. This leads to unnecessary load as this is executed again for every script execution. Current/Experienced Behavior: Lookup is not cached Improved/Expected Behavior: Cache the lookup (same as it is done for Designs) Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.18 Customer-name/Organization name: - Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Ensure AEM Maintenance Update releases respective code artifacts to Stage and Production Environments Use-case: We currently do Stage deployments on a weekly basis and Production deployments on bi-weekly basis. However, the AEM Maintenance Update pushes back the baseline code to last successful deployment for Production to Stage as well. This then requires another Stage.Ideally as the pipeline is able to pick up the last commit id of the deployment to Production, it should also be able to pick up the Commit Id of Stage and deploy the necessary artifacts. This deviates from the usual principle of deploying same artifacts on Stage and Production but helps to keep the system in as-is state before and after Maintenance Updates. Current/Experienced Behavior: The custom code that was only available on Stage gets lost and has to be deployed again. Improved/Expected Behavior: The Production instance should have the last known production deployment artifacts while the Stage instance should similarly have its last deployed artifacts to ensure continuity. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS (AEM Release - 2023.12.14538.20231205T165334Z) Customer-name/Organization name: TA Digital Screenshot (if applicable): AEM Version Updates | Adobe Experience Manager Code package (if applicable): N.A
Zusammenfassung der Funktionsverbesserungsanfrage (RFE): Better differenciation between Asset-Is-Expired and SubAsset-is-ExpiredVisual by not having a red flag for both - and for the filter. Anwendungsfall: The red flag icon on the thumbnail warns that an Asset is expired. This red flag indicates that a file can not be downloaded. BUT this warning is used by the system for two different occasions.AssetExpired and SubAssetExpired.An InDesign file might contain an expired picture.Now that InDesign file will be displayed with a red flag.But the InDesign file itself is not expired and can be downloaded.Therefore i suggest that there needs to be a better differenciation.Visualy as well as for the expiry search filter. Aktuelles/erlebtes Verhalten: If a picture expires that is built into 1000 documents, the expiry filter now lists 1001 expired assets - even there is only a single expired asset and a 1000 assets in which this picture is a dependency.There is no visual differenciation between an expired InDesign and an InDesign that simply contains an expired asset. Users see the red flag and get the impression that the file can not even be downloaded. Verbessertes/erwartetes Verhalten: For the Thumbnails, this can easily be done by having a small change in /libs//dam/gui/coral/components/admin/contentrenderer/card/asset/propertyList.jspThis already checks between the two states:if ((isContextCollection || properties.contains(VIEW_PN_IS_ASSETEXPIRED)) && (isAssetExpired || isSubAssetExpired)) { %> <coral-card-property class="expirystatus" icon="flag" data-is-asset-expired="<%= isAssetExpired %>" data-is-sub-asset-expired="<%= isSubAssetExpired %>" title="<%= xssAPI.encodeForHTMLAttr(i18n.get("Expired")) %>"></coral-card-property> <% } I changed this for my organisation, but i think it would be a great improvement for everybody OOTB. Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): Name des Kunden/der Organisation: medi GmbH & Co. KG Screenshot (sofern zutreffend): Code-Paket (sofern zutreffend):
Currently the Percent Complete roll up at the Program level only takes into account Projects that are in "Current" status. This does not make much sense as you are completely ignoring all projects that have been fully completed and marked as such. If all projects under a program have been marked as complete status, then the Percent Complete at the Program level should show 100%
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.