Build better products with our product team
Description - I would love to see consistency when I'm applying same choices from multi-select dropdown to an item listed in a report (e.g. task). Let's say dropdown has 3 options: 1,2,3. Depending on in which order they will be applied against task they may appear in random order: 1,3,2; 3,2,1; 3,1,2 etc. According to WF support randomness is per design. Why is this feature important to you - Consistency in listing items makes it easier to read field values How would you like the feature to work - Regardless of the order in which I select dropdown values, if I select the same values I would like to see them display consistently, as 1,2,3. Keep it consistent. Current Behaviour - randomness
Description - Our users would like to be able to 'lock' fields on projects and make them only editable by certain users. Right now there doesn't appear to be any functionality that accomplishes this. For example, the PM may want to 'lock' the Duration field so only specified users can update that field. Right now, anyone with Contribute or Manage access to the project is able to adjust those values. Or anyone with View access that has a Task level assignment. These permissions vary from project to project so we would like to be able to set these permissions on the object itself, and not as an Enterprise level rule. Why is this feature important to you - This is important for data integrity. Not all users should have access to edit all fields just because they have access to a project. How would you like the feature to work - I envision some type of 'lock' or 'share' button on the field that allows us to set permissions for that particular field. This would supersede any Project level permissions. Ie: User John has Contribute access to the Project but only has View access to the 'Duration' field.
Hello, This is a feature request to add annotations in all trended displays in AA and CJA. Right now, I believe I can only see annotations in "line" charts. But I can see that it would be also valuable to see annotations in: combo displaysarea displaysbar displaysetc.Sorry if this is in the wrong spot. Will move this if needed.
Request for Feature Enhancement (RFE) Summary: We create a new page under /content/soucedcode/language-masters/en called home . Within this page, we will drag in an Experience Fragment Component with the XFPath. In this scenario, we have XFPath = /content/soucedcode/experience-fragments/language-masters/en/button/masterWhen we language or live copy pages, the XFPaths should be updated as expected, but it is not. Now let's continue with the scenario. Please note that we have the entire structure of the XF created - /content/soucedcode/experience-fragments/language-masters/en/button/master - /content/soucedcode/experience-fragments/language-masters/fr/button/master- /content/soucedcode/experience-fragments/language-masters/es/button/master - /content/soucedcode/experience-fragments/ca/en/button/master - /content/soucedcode/experience-fragments/ca/fr/button/master- /content/soucedcode/experience-fragments/us/es/button/masterNow after when the new page is created in language-masters, we will start performing the language copy /content/soucedcode/language-masters/en/home TO->> - /content/soucedcode/language-masters/fr/home - /content/soucedcode/language-masters/es/homeWe expect the referenced experience fragments to change the references with the correct values below, and it looks like it works as expected from here: - /content/soucedcode/language-masters/fr/home== XFPath: /content/soucedcode/experience-fragments/language-masters/fr/button/master - /content/soucedcode/language-masters/es/home == XFPath: /content/soucedcode/experience-fragments/language-masters/es/button/masterOkay now we are going to roll out the language copies pages to the different countries. Since these language copies are actually live copies within the language folders, the roll out mechanism will work as expected. Target pages: - /content/sourcedcode/ca/fr- /content/sourcedcode/us/es(Expected Results)After the roll out, we expect that the experience fragments should have the XFPaths localized like the configurations below. In a perfect world the Live Copy and Language Copy mechanism should update the XFPaths as expected like what we see below:- /content/sourcedcode/ca/fr/home== XFPath: /content/soucedcode/experience-fragments/ca/fr/button/master- /content/sourcedcode/us/es/home== XFPath: /content/soucedcode/experience-fragments/us/es/button/master(Actual Results)In actual results, we are seeing that the XFPaths are not localized, and is referencing to the language-masters paths: - /content/sourcedcode/ca/fr/home== XFPath: /content/soucedcode/experience-fragments/language-masters/fr/button/master- /content/sourcedcode/us/es/home== XFPath: /content/soucedcode/experience-fragments/language-masters/es/button/master Use-case: We have pages created in language masters which has an experience fragment inside of it. The experience fragment is referencing to the experience fragments language-masters path. When we Roll Out or Language Copy pages, we expect the references to update to the non language-masters structure. Current/Experienced Behavior: (Actual Results)In actual results, we are seeing that the XFPaths are not localized after Roll Out or Language Copy executions. Look at this, this is still referencing to the language-masters paths: - /content/sourcedcode/ca/fr/home== XFPath: /content/soucedcode/experience-fragments/language-masters/fr/button/master- /content/sourcedcode/us/es/home== XFPath: /content/soucedcode/experience-fragments/language-masters/es/button/master Improved/Expected Behavior: (Expected Results)After the Roll Out or Language Copy, we expect that the experience fragments should have the XFPaths localized like the configurations below. In a perfect world the Live Copy and Language Copy mechanism should update the XFPaths as expected like what we see below:- /content/sourcedcode/ca/fr/home== XFPath: /content/soucedcode/experience-fragments/ca/fr/button/master- /content/sourcedcode/us/es/home== XFPath: /content/soucedcode/experience-fragments/us/es/button/master Environment Details (AEM version/service pack, any other specifics if applicable): Latest AEMaaCS and AEM 6.5 SP Packs Customer-name/Organization name: NULL Screenshot (if applicable): Code package (if applicable):
Currently, all feeds must be created through the UI. It takes a lot of man hours to create and validate a new feed. It would be a nice for Adobe to expose an API which we can manage our data feeds programmatically and automatically. Thanks
Certain types of requests (queue topics in some cases) require a document to be included in the request to pass initial assessment in traffic before being approved. The ability to force an attachment of some sort would stop the requester from submitting the request (like you do with required fields) without the attachment and save back and forth time for the request to be approved to begin work or be assigned out to a team.
I saw that someone had this suggestion for Updates (which is great), but I would love to be able to edit the style of text in tasks, issues, project details and custom forms too. It would really help to break up big blocks of instructions and call attention to particularly important information. Caps and punctuation only go so far.
Description - When users copy tasks from an old project with assignments, if they don't choose to carry over the old projects permissions the task in the new project does not give any permissions at all. I would have expected this task to take on the task permissions set on the new project but WF support says this is not the intended behavior.Why is this feature important to you - Our PMs often copy sections of tasks from previous projects to save time, but they do not realize that the new task doesn't give any permissions. When the task assignees try to interact with the task they are met with no access errors.How would you like the feature to work - I would like any task copied from one project (if permission is not selected to copy with it) to take on the task permission set on the new project.Current Behaviour - Currently the task copies over but no permissions are given to the assignees for the task or project
Description - A Project owner gets a notification when a new document is added to their project. Apparently this type of notification does not exist when that document get a new VERSION added. This mean that the Project Owner needs to rely on the person adding the new Version to make a comment in th eupdates feed or some other manual communication to the them so they can stay updated on the activity. It would be nice if the Project owner could have the option to get notifications upon upload of a new Version as well.Why is this feature important to you - Important for communication to keep the flow of work moving.How would you like the feature to work - Just like the notificaiton for new documents being added to a project.Current Behaviour - There is no current behavior.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.