Allow Admin to configure whether an Activity EA is “Required” on each Work Request Form (WRF) rather than everywhere.
Currently, if an Admin wants an Activity level EA required on a WRF, the “Required” parameter is set on the EA configuration page under the Activities Extended Attributes list. However, this makes the EA required across every WRF where it appears, and subsequently, every Activity Details page where it displays. This causes issues for multiple user groups that do not occur with a project or task EA.
The first consideration an Admin has to make is a Requester or user that is responsible for filling out a WRFs, frequently skip over EAs that are not required/bolded. Because many Activity EAs “should” be required on some WRFs, but not all, Admin are forced to determine if it is worth making the field required across all forms. An Admin’s options are either to require the user to input a response even though it may only pertain to their situation a small percentage of the time, or the Admin must set a default value to correspond with the highest percentage answer option across every WRF.
As you can imagine, the former leads to frustration from Requesters as they feel they are filling out unnecessary fields. For the ladder, beyond the Admin needing to update every WRF which can easily surpass 250+ unique form, users miss the field because it is already filled in for them. When users miss fields, it causes issues later in the project’s life cycle (especially if the field determines the project’s routing) which causes frustration, delays, and resubmissions.
The second consideration an Admin has to make is the repercussions of needing to make edits on every Activity Details page where new Activity EAs are required. Every instance the EA is displayed, whether historical or new, if a user hits edit, they are required to input a selection for the required field before they can save whatever update they were originally trying to perform. For users who consistently make updates to the Activity Details page, this is beyond frustrating and makes any Admin lose friends very quickly.
*One workaround is to use the Data Loader to backfill all historical data for the new field. This especially useful when trying to convert old EAs to mirrored EAs with share option sets.
Admin should have the ability to set the “Required” parameter when configuring each WRF rather than on the EA configuration page. On the Defaults tab of the WRF setup, have a second column similar to the DCT functionality where you can indicate if the field should be required or not. If the EA is configured to be required via the historical EA config page, the functionality can still perform the same way as it does no. However, if the EA config is not set to required, then the Admin should be able to set the parameter on a per WRF basis.
Customer support service by UserEcho