Build better products with our product team
Please allow programs to be shared between workspaces. In a global deployment where you have content creators and content distributors in different workspaces, it would be very helpful in these environments to have a workspace to create a test programs and then have them shared among the workspaces where content is being delivered.
Description -When you go to the profile and select one profile and go to Events tab. We see events old events first, if we have bunch of events it is very difficult and time consuming to see the latest events.Why is this feature important to you - To save time when we want to see the profile events.How would you like the feature to work - we should have sorting feature on events and pagination as well .Current Behaviour -When you go to the profile and select one profile and go to Events tab. We see events old events first, if we have bunch of events it is very difficult and time consuming to see the latest events.
One of the biggest complaints from our PMs is that there is no easy way to ensure that users stop logging time to a task after it is "Completed". We will have situations were at the end of the month a person it needing to update their timesheet and they are entering hours beyond the date the task was closed. So it becomes a 'dumping ground' for hours. We have created exception reports to help the PMs monitor when someone is logging time to a Task beyond the Actual Completion Date, however, it's just extra overhead for them that takes time away from more important PM functions. They would really like it if they have an way to stop this from happening; they already have enough reports to monitor. There is one option that they can attempt to stop this, but it requires that they update the Sharing Option for each person assigned to the Task to un-check the "log time" option, which is also very time consuming depending on the number of Tasks that need to be updated and the number of people assigned. So this isn't perceived by them as a "easy" solution for obvious reasons.
I have good experience on SharePoint and other CMS's, one thing I noticed when I compare AEM with others, the Recycle Bin is not available in AEM.If content authors accidentally delete any pages or assets, then it is difficult to get it back, sometimes they need to depend on developers to get it back and it is time consuming process, are there any plans to implement the same in future releases?
I would love to see the new form designer incorporate some better cues to show logic connections. The new form just has the D for display logic or S for skip logic (and filled in or not filled in based on end of connections); however, this does not solve for seeing which fields are connected to each other. Previously there was color-coding, which was sometimes hard to distinguish but was still very helpful. I would love to see some sort of boxes with colors and/or numbers to show which fields are connected so we don't have to attempt to click into several fields and scroll to additional settings at the bottom to find out what each field is connected to. We also could easily see before which fields were VERY connected (i.e. had several other fields connected to them, so we knew we needed to be extra careful). Now we have to click into each to find these. This is important because the new form builder will now be the only option. We have many large forms with a lot of logic built in that are working great for us; however, they now take much longer to edit due to the new builder's logic designation. There is also a lot more risk for adjusting a field that is tightly woven into the rest of the form due to logic. Thank you! Brittany
emails are unique acorss the systems whereas $$USER.name may not be. Also, since name may include umlauts/accents that variable is not ideal. I want to filter (report/view) based on the current user's email address because on our case the address is stored in custom field when we don't find the user; if the user later were added to WF I'd like to have a report to show those items where the custom field has their email address
We work very closely with our Data teams and use a lot of various API connections pushing and pulling data from Marketo. One of the annoying hurdles is that when an error occurs and I get told "there was an error in Program 3387", there's no way to search by Program ID.This would be insanely helpful instead of having to go through every program individually. Maybe there is a way currently?
Description - Something that is in my opinion quite a waste of time is that with every save on a data element, rule or extension, it is closed and one has to reopen it. Why is this feature important to you - Efficiency, would save a lot of time when you are knee-deep in Launch and won't have to navigate back into the previous component. Works that way in every other desktop app How would you like the feature to work - Click "Save to library" without closing the element Current Behaviour - edit data element - Save to library - where was I?! - ... - start filtering until found - open again - edit - save - back to where was I
Description - On a custom form, checkboxes, radio buttons, and dropdowns all have an option to "Hide Choice". This feature allows admins to hide specific choices on the form. For instance, a field called "Pets" might have 3 choices: "Bird", "Cat", "Dog". By selecting the "Hide Choice" option next to the choice "Cat", an admin can hide that choice from displaying to users of the form. However, hiding the choice of "Cat" will hide it on ALL forms that use the "Pets" field. It would be beneficial to have the hidden choices be specific to the form where the setting is changed, rather than on all forms that reference that field.Why is this feature important to you - Currently, if the same field is used on different forms, that field will display the same choices on all forms. Often a form might be designed with a specific audience in mind. Being able to customize the field choices for the specific audience would make the form more user-friendly, while also saving the admin time (by not having to create different fields for different forms, and not having to reference multiple fields when running reports).How would you like the feature to work - When an admin is creating a custom form, they will add the checkbox, radio button, or dropdown field as normal. All choices would display by default (as they currently do). However if/when the admin chooses to hide a choice, that setting would be saved only on the current form being edited. If the admin were to edit an additional form that includes the same field, all choices for the field would be displayed by default unless the admin were to hide a choice on that additional form. If the admin did choose to hide a choice on the additional form, that hidden choice would be saved only on that additional form.For example, if there was a form titled "Household" it might have a field called "Pets" with choices of "Bird", "Cat", "Dog", "Goat, "Horse", "Rabbit". Since the form is specific to a household, the admin could choose to hide the choices of "Goat", "Horse", and "Rabbit". Then on another form titled "Barnyard", the admin could reuse the same "Pets" field, but hide the choices of "Bird", "Cat", and "Dog". By doing so, all pet choices across both forms would save in the same field, however only the relevant choices would be available on their specific forms. When running a report, the admin would only need to reference a single "Pets" field, rather than having to reference a "Household Pets" field and a "Barnyard Pets" field.Current Behavior - Currently, selecting the "Hide Choice" option will hide the specific choice on all forms that reference the field. If an admin wants to display different choices on different forms, they need to create a completely distinct field, essentially duplicating the field in question. This is not ideal as it can become cumbersome to maintain both from a form/field standpoint, and from a reporting standpoint.
Description -I would like the ability to change retry parameters directly in O365 modules, including number of retries and period of time between retries.Why is this feature important to you -Currently, adding this type of error handling involves adding at least two modules per retry, becoming large and difficult to manage very quickly, especially if I need to make changes to the module's behaviour and then copy this multiple times in the case there is a connection error while making the request.How would you like the feature to work -Have retry behaviour parameters built into the existing module, even under a form of 'advanced settings'. Alternatively, Adobe could have pre-configured settings for this, to make the current module operation more robust, without any more visible complexity for users.Current Behaviour -It isn't uncommon, even in fully working systems, for Microsoft Graph API to return 504 errors when sending requests. Especially if you are doing operations in excel across a number of rows. At the moment under Error Handling I have been putting a sleep and copy of the module below in order to reduce the occurrence of these issues stopping the whole flow, and allow each scenario flow to complete before the next one starts (which I can't properly achieve with the current 'break' error handler).
Request for Feature Enhancement (RFE) Summary: Developers should have a read-only view of CRX/DE for debugging purposes Use-case: Debug deployment issues, check paths and properties Current/Experienced Behavior: Currently AEMaaCS has repository browser but it has limitations - It is sometimes not showing few paths/folders even though it is there in author/publisher. It requires separate access via developer console and not all developers may have access to that. Improved/Expected Behavior: Simplifies read-only view of crx/de is a better way to provide access to author and publish repository. Developers should even have this in production so that issue resolution for production content issues or code deployment issues can be expedited. Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS author and publish environments Customer-name/Organization name: GSPANN Technologies Screenshot (if applicable): Code package (if applicable):
Description - Add a comment block/section to each filter condition.Why is this feature important to you - It would provide clarity when looking at a filter with many different conditions.How would you like the feature to work - An optional comment block be added to each condition within a filter. Building off this, an option to also toggle them on or off within each individual filter as some don't have many conditions.Current Behavior - Filter has a label that generally describes filter behavior but not each individual condition.
Description - We would like for there to be an external license level that does not get access to any systemwide shared objects. Why is this feature important to you - We have the need to give external users, like vendors, access to the system so that they can access projects. However, any license we use gives them access to systemwide shared objects. These systemwide shared objects make sense internally (all users need access), but out external users should not have access to these objects. How would you like the feature to work - Either create a new license level that limits systemwide shared objects, or a settings on licenses where you can limit system wide shared objects. Current Behaviour - all license types get access to systemwide shared objects.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK