Request for Feature Enhancement (RFE) Summary: Enable the Copyright page display in AEM Assets without overriding the XMP web statement property Use-case: Right now, if we want to enable the custom coypright page to display whenever a licensed asset is going to be downloaded, the XMP web statement property is being overriden by the content path to the copyright page. Current/Experienced Behavior: Right now, if we want to enable the custom coypright page to display whenever a licensed asset is going to be downloaded, the XMP web statement property is being overriden by the content path to the copyright page. Improved/Expected Behavior: We don't want the web statement property to be overriden becauase we are losing important info Environment Details (AEM version/service pack, any other specifics if applicable): AEMACS Customer-name/Organization name: Accenture Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Support for NginX as a dispatcher Use-case: Any AEM setup where a dispatcher is used. NginX outperforms Apache: NginX is faster than Apache, has a smaller codebase and can handle more request than Apache with less load on the machine. It would be beneficial for both the Adobe's server (because NginX is lighter for the machine) and the client (because NginX can handle requests faster). Current/Experienced Behavior: No NginX support Improved/Expected Behavior: NginX support Environment Details (AEM version/service pack, any other specifics if applicable): any AEM version Customer-name/Organization name: National Lottery Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: When setting an Experience Fragment in a blueprint, live copies will not automatically pick the correct corresponding language version of the Experience Fragment. This makes our author's output slower on Experience Fragments. And it increases the risk of human error/inconsistency significantly. Use-case: A multilingual setup making use of Experience Fragments. Each Experience Fragment has a Blueprint (en) and a language copy. And in Sites, a Blueprint (en) and live copies in the same languages. Current/Experienced Behavior: When an author creates or updates pages in Sites blueprint, and we synchronize those changes into the live copies, the Experience Fragments in those pages have to be adapted manually to the correct laguage. This means authors cannot manage Experience Fragments from the Blueprint in a multilingual setup. It means an Author is forced to go an manually pick the correct Experience Fragment in each language, whereas it as simple as chaning the language part from the pointer to the correct language, e.g Experience-fragments/en/test/master -> Experience-fragments/nl/test/master In our multilingual setup: this step is repeated for all the languages, because we use a language copy structure inside Experience Fragments, the action is very simple, but repetitive and error-prone. Authors need to repeat the same change in the Blueprint and each Live Copy individually, which results in loss of time on repetitve tasks and the introduction of possible errors. Improved/Expected Behavior: Pointers to Experience fragments are automatically translated in "Sites" when sites and Experience fragments both use the same language structure. Environment Details (AEM version/service pack, any other specifics if applicable): 6.5.8.0 Customer-name/Organization name: National Lottery Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Modify the License checker functionality for Assets since node is granite hidden folder ((granite:InternalArea)) Use-case: Checking license of an asset in the DAM Current/Experienced Behavior: can easily get to required data but can't because it is in a hidden folder Improved/Expected Behavior: change either folder permissions so it is easily accessed or move license checker functionalty to a new, accessible folder. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Assets as a cloud service Customer-name/Organization name: Mark Edelstein/Accenture Screenshot (if applicable): Code package (if applicable):
Other software applications I use (locally or cloud based) have the ability to pop up a notification on my desktop when an action or notification for me is ready. In an effort to reduce my creative team's reliance on email and since they spend most of their time in Adobe software I'm looking for a similar solution for WF. It would be very effective if WF notifications could pop up on their desktop over all applications I have open (in the top right corner of my screen). Similar to how the mobile app notification feature works (it's great by the way). I'm thinking of this in a similar fashion to instant messaging (AOL, gchat, Lync/Skype, etc.). It should be interactive so I can launch in to a WF browser by clicking on it. Thanks for your consideration!
Project owner to receive an email notification or at least a Workfront notification when a new Document version is uploaded to an existing document.
I would like to be able to report on checkbox fields to count and chart selections with the same ease as any of the other field types. There are discussions going back years with this issue and the best solutions have been: Use advanced text mode for each checkbox option (poor report-building experience that, for someone like me, often means needing to hire a consultant).Create a yes/no question for each checkbox option (very poor user experience for both building and filling out the form).If the parsing code is applied at the Workfront system level, this could save administrator time exponentially. It also aligns with system user experience for pretty much any other form-building system out there (Google, Microsoft, SurveyMonkey, etc.).
Description - Adding the feature to throttle the amount per hour.Why is this feature important to you - I fell like this is a base feature that every email provider has out of the box...How would you like the feature to work - Easy, We just want to type in the number of emails that will get sent every hour. Or we just tell you how many hours we want to spread the send out.Current Behaviour - Expressions (Not easy for someone that has never worked with them) and Workflow. Reporting that many email at once is a nightmare.
When you select an existing custom field from the library while creating a custom form, you see the notice: This field is being used on other forms. Changing it here will also change it on those forms. Since we have a request & project copy of nearly every custom form, so we see this message all the time. The problem is that we don't know where the field being used! It would be so helpful if you could find out which forms are using that field without having to save and exit or leave the page. I'd love to see something like "hover to see which forms are also using this field" or even just have the full list of forms using it displayed right there in the message (bonus points if the list is collapsible). We have older forms with fields that are inactive, but we still need to keep them to avoid losing historic data. I'd hate to accidentally change a field being used on another form and lose all that data. Creating new versions of the field can also be cumbersome, since you can't have two fields with the same name. Sometimes there are only so many ways to ask a question, and then we have to get creative with letter cases & the limited punctuation allowed (which is inefficient and doesn't always look professional).
Current functionality is that work that is assigned to a user that does not match the intended job role; the work still appears in the Unassigned work swim lane of the Workload Balancer. It would be great if the system knew the work was assigned and treated as such.
Description - Date Warehouse is the best way to obtain large reports from Adobe Analytics. The lack of presets is quite a restriction to fully utilize this toolWhy is this feature important to you - I want to combine large datasets from Adobe in Power BI. I want this to be automated, but the lack of date presets limits my ability to do so. How would you like the feature to work - Add all the date presets available in Workspace to Data Warehouse- last quarter, last 3 months, this year, etc etc. Current Behaviour - Very few date presets are available.
Request for Feature Enhancement (RFE) Summary: Optimize "orderable" folders feature Use-case: User orderable folder feature for 700+ folders Current/Experienced Behavior: Right now, we are not using the "orderable" features for folders since we were told that there's going to be performance implications Improved/Expected Behavior: Be able to use the orderable features to a lot of folders in the hierarchy without any performance implications Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description:I would like to be able to limit a users access to a single workspace project and report suite. I would not want this user to be able to see other workspace projects from the menu or create a new one. Why is this feature important to youWe would like to provide access to some of our vendors to be able to use a workspace project. Their permission is limited to a single VRS with only a few dimensions available, but they can do breakdowns, make visualization, edit the time window, etc. The issue is they can go to the workspace project list and see what others have created. We would want to prevent this and just have them see the one workspace we determine. How would you like the feature to workThis should live in the admin section Current BehaviourAll users can see all shared workspace projects
Situation, after applying filters on WB resources are listed simply alphabetically. It would be helpful if I could sort them e.g. based on their remaining availability for today, or some other field of choice.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.