Skip to main content

Ideas

Filter by idea status

10000+ Ideas

J_Mas
J_MasLevel 5

Minimum and Maximum number of required choices for Checkbox and Dropdown fieldsNew

Description - Checkbox and Dropdown fields currently allow for the entry of single or multiple values by the end user. In these instances it would be beneficial for the admin to set a minimum and maximum number of required choices.Why is this feature important to you - Having more control over the type and quantity of information being entered into Workfront will give better accuracy over the data / reporting coming out of Workfront. There are many occasions where we may want a user to indicate more than one choice, but not be able to select every choice in the list.How would you like the feature to work - When creating or editing a Checkbox or Dropdown field, the admin would see two additional options: "Set minimum number of choices" and "Set maximum number of choices". Each option (respectively) would allow the admin to set a minimum number of selectable choices, and/or a maximum number of selectable choices.For example, an admin might build a Checkbox field which states "Indicate between 2 and 3 OKR's which will be addressed by this project." The admin could supply a list of 6 OKR's, and check off the minimum and maximum choices option, setting the minimum to 2 and the maximum to 3. When a user is presented with the field on a custom form, they would be required to check off at least 2 choices, and would not be able to check off more than 3 choices.Current Behavior - When creating a Checkbox field, any (all) choices are able to be selected. No additional customization is possible. When creating a Dropdown field, a single choice is selectable by default but the admin can enable the option to "Allow more than one option to be selected."

BenjaminPerezAdobe Employee

Product Enhancement Request - CJA ConfigurationNew

Business Requirement/Justification: For a Financial Organization, Security and Governance is a critical component in any solution that deals with its Customer data.To comply with internal Governance policies, we have different teams managing “User Access” and “Any Product Configuration and usage” activities.The Governance team which manages “User Access” do not have the technical knowledge on AEP or CJA to carry out activities like “Creating Connections” and “Data Views”.The team who has the knowledge of AEP and CJA are not authorized to deal with “User Access Management” activities as it is against our Governance policy. But for CJA, these two activities are coupled together and Only Product Admin has the ability to “Creating Connections” and “Data Views” along with an ability to “Grant New User Access or Remove Exiting” and “Create Product Profiles”.Hence, we want to decouple these 2 broad activities and let regular Product Users have the ability to “Create Connections and Data Views” (and manage the access within the Product Profiles) and limit any “User Management” privileges.Impact: If core AEP/CJA team is given access to Product Admin access. We run the risk of not being compliant with our Governance Policies and Process.If not, We will continue to have delays and ongoing challenges to get any Connections and Data Views configured. (THIS IS CURRENTLYT ONE OF THE LIMITING FACTOR TO IMPROVE ADOPTION OF THE SOLUTION.)Currently, this is done in working sessions/meetings were the CJA user guides Governance team member to carry out certain activities.This is not scalable and not efficient approach, as it is difficult to have required team’s availability and requires multiple people to do the same job.

JoshuaLeLevel 2

Workfront- Ability to easily add/ delete a line item in a report w/o having to leverage an objectNew

Description - Currently based on the system's structure, in order for our team to pull in a detailed calendar/ tracker view for planning, we have to indicate those line items/ details on a planning project form. This is a confusing and extra clicks for the team from the current process of being able to easily add / delete line items to a tracker view. This is to also address the valid business needs where things change last minute and the team needs to easily be able to action. Why is this feature important to you - This will increase adoption & overall efficiency for our teams as they work compared to their current/ previous process prior to Workfront How would you like the feature to work - User should be able to see an option to add / delete directly on the report to add additional line items OR there should be a new feature launched in WF that allows for the ability to create and easily maintain trackers similar to Smartsheets, google docs, etc. This would allow the teams to pull in more work streams/ processes into a single tool. Current Behavior - Currently based on the system's structure, in order for our team to pull in a detailed calendar/ tracker view for planning, we have to indicate those line items/ details on a planning project form. Teams can only edit inline on the report but not add/ delete from that view.  See screen shots for new process within Workfront. 

Andrew_Wathen_
Community Advisor
Andrew_Wathen_Community Advisor

Virtual Report Suite Curation: Impact on user created components prevents useNew

My organisation has been trying to move to using curated Virtual Report Suites.  However, we have had to abandon these plans because of the following 2 main problems:1) Segments can either be shared to everyone or no one2) Users who create segments metrics are unable to see what they createDetails of the issues encountered...There are now 3 administrative capabilities relating to segments:User admin control over creation of segmentsSharing of segments (e.g. clicking “share”)Customization of Virtual Report Suite Components (VRS Curation)Unfortunately, they interact with each other in bizarre and contradictory ways.  However, all the problems seem to stem from the “Customization of Virtual Report Suite Components” capability.Issues observed:The sharing of segments becomes all or nothing.          This is because:Any segment that has been included in VRS curation become visible to all users of that virtual report suite (even if the segment is not “shared”)Shared segments that are not included in VRS curation cannot be seen by any usersThis means:Either everyone gets a segment, or no one gets a segmentThe segment “share” functionality in analytics becomes completely redundantUsers who have been granted access to create segments suffer a poor/degraded experienceWhen a user creates a segment it is not a curated segment within the virtual report suite and is therefore blocked from appearing in the left-hand rail.This break a well establish workflow leading to much confusion as segments do not appear where users expect them.(Note: users aren't actually blocked from using segments they've created as they still have the capability within the panels to create segments in the project.)