Product ideas | Community
Skip to main content

10000 Ideas

J_Mas
J_MasNew Participant

Form-specific choices for checkbox, radio button, and dropdown fields.New

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.

b_hardeeNew Participant

Assets New/View/React UI | Resurrect the Star Rating FeatureInvestigating

Request for Feature Enhancement (RFE) Summary: I know this was previously available as part of the AEM social package and then unsupported with the move to AEMaaCS, but our organization (and I believe most others as well) would greatly benefit from using a native 5-star rating system on our assets, interactive from the card view and sortable in the list view. Use-case: Particularly with our photography assets, we have a process in place to rank images on a 5-point scale from Best to Worst, which directly translates into how people are discovering and using these assets in other marketing materials. Having the stars on the card and properties view--both to actually apply the rating as well as to immediately have the visual cue (like how it's managed in Adobe Bridge)--would be extremely helpful, and would create the ability to filter out lower rankings, sorting assets in the list view according to ranking, etc. It would also be a very intuitive, user-friendly enhancement as a star-rating concept is universally used across all types of technology platforms and industries all over the world.  Current/Experienced Behavior: Our workaround in the Touch UI involves a custom field to capture asset rating data, which is being mapped to the Average Rating field, which then populates star icons on a custom overlay in the card view, and allows for sorting in the list view. The star icons are not clickable to direct select the rating, and going to the custom field in the Properties to select the rating is counter-intuitive to the users. Also, we will not be able to replicate this workaround in the new Assets View UI, which we want to move to and release to the enterprise. Improved/Expected Behavior: Add back the 5-star Asset Rating field. Every asset would have 5 blank star icons in all asset views (like in Adobe Bridge) with the ability to click the star to apply the rating metadata. Bonus: if that metadata were applied in Bridge, it would auto-map into AEM.  Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS, using the Touch UI on Author at an enterprise level (1,300 employees), wanting to upgrade to the newer UI but roadblocked by lack of this feature Customer-name/Organization name: HGA Screenshot (if applicable):   Code package (if applicable):  

AKP_ORGEmployee

Asset should NOT be allowed to publish without mandatory propertiesDeclined

Request for Feature Enhancement (RFE) Summary: AEM Assets metadata schema allows client to configure metadata schema with mandatory properties. Once this schema is applied to folder, then assets inside that that folder is highlighted with banner as REQUIRED METADATA MISSING. Also will NOT be allowed to save metadata without putting mandatory properties. But asset are allowed to publish without mandatory properties. AEM should restrict publishing asset without mandatory property. Use-case: AEM Assets metadata schema allows client to configure metadata schema with mandatory properties. Once this schema is applied to folder, then assets inside that that folder is highlighted with banner as REQUIRED METADATA MISSING. Also will NOT be allowed to save metadata without putting mandatory properties. But asset are allowed to publish without mandatory properties. AEM should restrict publishing asset without mandatory property. Current/Experienced Behavior: Asset are allowed to publish without mandatory properties. Improved/Expected Behavior: As mandatory properties are missing, asset should not be allowed to publish (similar to how metadata save is not allowed without adding mandatory properties). Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service (AEMaaCS) Customer-name/Organization name: Lenovo Screenshot (if applicable):   Code package (if applicable):