Description - We would like to add global custom forms to all projects by default. This would be a setting in the admin project setup section. By adding this capability, I can add company-wide custom forms when a user creates a project. Why is this feature important to you - There is no way to add a mandatory custom form to projects. We use custom forms at the project level to categorize export compliance classification and non-standard identifiers. How would you like the feature to work - Add a Project Setting in the admin setup area where admins can specify default custom forms on project creation and on existing projects. It would also make sense to add this to individual Group's settings, where groups can have default custom forms associated with projects they create instead of having to define templates just to add custom forms to their projects, which would not work if a user does not create a project from a template. Current Behaviour - Must have project creators manually add custom forms and if they do not, the project does not have those custom fields.
Description/Current Behaviour - In Single Line Custom Fields from type number, Workfront is only allowing the decimal separator dot (25.5). If a user enters the number in the European format with a comma as separator (25,5), Workfront is erasing/deleting the comma from the Value. Why is this feature important to you - When you include such a field in your calculations, your result could be wrong because of a deleted decimal separator. Depending of how many decimal numbers you have entered your result could be 100 or 1000 times higher. How would you like the feature to work - There are a few possible ways to solve this. The first possibility is already in place, but in a different area of Workfront. In the Timesheet you can enter the hours with a comma separated and Workfront changes automatically to a value with a dot as separator. So the existing rule of deleting the comma should be upgraded, that the comma is not deleted but rather be changed to a dot. An other option would be that the user how creates the field can set the needed format and that the format is displayed in the field to guide the user in which format he needs to enter the value. A third option would be that the Field is allowing to have both separators in the field and in the background Workfront is standardising the value for further use.
If it was possible to alert on calculated metrics the alerts would be much more useful. Application volumes go up and down depending on so many factors, so it's difficult to set a threshold. Application conversion is pretty consistant on our site, so a drop in conversion gives a much better indication of an issue.
Description - We use A4T and create a report in Adobe Analytics for every A/B test we run. Once concluded we tend to archive activities in order to keep Adobe Target clean and simple to manage, however any report that references the archived test then breaks because the test name changes once archived. Why is this feature important to you - Often we want to look back at reports, only to find that they have broken and we need to rebuild them with the new (archived) test namesHow would you like the feature to work - Tests can be archived without their names changing or for Analytics reports to automatically update to accommodate the new test name
Request for Feature Enhancement (RFE) Summary: We want to publish XF with the on-time function. Please add the necessary items to the XF publishing screen. (Example) On-time/off-time items , etc. Use-case: We want to publish XF with the on-time/off-time function, but the current XF publishing screen does not have the necessary items. Example: An item to specify on-time/off-time, etc. Please add the necessary items to the XF publishing screen. Background -When publishing many products at the same time on the same date and time, many approval flows occur at the same time, processing is queued and there are cases where it is not possible to publish at the specified time. -As a countermeasure, We want to use the on-time function to perform pre-processing. Current/Experienced Behavior: The current XF publishing screen does not have the items required for the on-time/off-time function. Improved/Expected Behavior: Please add the items required for the on-time/off-time function to the XF public screen. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Release 2024.4.16145.20240430T082417Z Customer-name/Organization name: Panasonic Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Provide Composite fields in multifield Use-case: As an CF editor, I want to add different type of values as a combination and I would prefer to use a field like composite multifield (same as we have in component dialogs) Current/Experienced Behavior: Currently no composite field is available for CF Improved/Expected Behavior: Composite multifield allowed for CF Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description - I LOVE (yes, that's uppercase!) the Web SDK "Data Variable" Data Element Type in conjunction with the "Update variable" action. Especially with the new UI, it looks almost exactly like AppMeasurement, even better. What I am missing is a way to initialize the DE in a similar way an "XDM object" can be defined directly in the Data Element section, to set an initial state, and which you can build upon in your rules to temporarily enhance it. After the rules have completed, the initial state is reset. In my current setup with the ACDL (Adobe Client Data Layer), I need a standalone rule that is listening to "all events" and runs before any other ACDL triggered rule that further updates the variable, just to achieve this functionality. Or am I missing a step / functionality? As a workaround, I could likely also create a "custom code" DE instead, that defines the core data structure as JS object, and can then be merged with the variable part and the result used instead. This would remove the need for an additional rule, but would also require you to be savvy enough to write that code yourself. Why is this feature important to you? - It creates the need for unnecessary workarounds to set the globally applied pieces on the DE. How would you like the feature to work? - The XDM object can also be defined in the Data Elements section, why not the variable data element as well?In the DE definition, why not already display the same UI that is presented in the update variable step? Current Behaviour - Cumbersome additional step/rule needed to set commonly used parts on the data element e.g., through a custom rule that runs before the actual page view or interaction rule
Hey all, I think it would be very helpful if filters in Smart Lists could link out to what's being referenced, instead of having to search to find what you're looking for. Basically, just link up what's highlighted in the screenshot. I know this would make my life easier on occasion. 😁 Also, if this has already been proposed, feel free to point me in the direction of that post. I wasn't able to find anything via search! Have a good one!
When templates are deactivated, they still show for non-admin users who the template was shared with. This is very confusing for our users and allows them to choose a deactivated template when creating a project. To prevent this, when I deactivate a template I also have to un-share it will all non-admin users, and this is an extra step that I don't think should happen. If a template is deactivated, I think it shouldn't show up for users.
There is a long-standing frustration with proofs that oftentimes approvers will make a comment in a proof but not make a decision. It would help to not let the person close a proof after making a comment without marking a decision IF they are an approver or reviewer/approver on the proof and are not in a proof where only 1 decision is required and has already been made.
Description - Currently, Launch/Tags does not support a tagging nor folder functionality, especially in big projects leaving it to the implementer to use naming conventions to keep things tidy Why is this feature important to you - especially big projects easily get messy How would you like the feature to work - add a tagging + filtering and/or folder creation possibility, similar to what GTM provides Current Behaviour - nothing similar
Description - The option from the analytics workspace to share a report with anyone has improved the end-user experience, one can easily interrogate the report by using dynamic filters, date range, etc. However, it might also be a good idea to have an option to download the data as CSV or save it as a PDF.Why is this feature important to you - This will improve intuitiveness.How would you like the feature to work - Just the same way as it works within the analytics workspaceCurrent Behaviour - Feature not available
I would like to be able to create a report that only shows data for projects I have favorited. This list would be dynamic as projects are added and removed from favorites over time. I don't own my projects, and I'm a resource on some projects that I'm not interested in tracking in detail. My favorites list is the list of projects I would like to appear in some of my reports.
Request for Feature Enhancement (RFE) Summary: With AEM 6.4 SP8, Adobe introduced restriction that only members of the AEM administrator group could publish to the Brand Portal. This request is to align publishing permission for the Brand Portal with the standard replicate ACL. Use-case: An AEM Assets user--i.e. a designer or a marketer--completes work on an asset and would like to publish the asset to the Brand Portal. The administrator for AEM would like to be able to grant that user the permission to publish their assets to the Brand Portal without making them an administrator (and granting many permissions which are inappropriate for their role). Current/Experienced Behavior: Only members of the AEM administrators group can publish to the Brand Portal Improved/Expected Behavior: Users with replicate permissions on the asset or folder can publish to the Brand Portal Environment Details (AEM version/service pack, any other specifics if applicable): This is applicable since AEM 6.4 SP8 through AEM 6.5 SP11 as well as the current build of AEMaaCS Customer-name/Organization name: Apex Tool Group; Wakefern 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.