It would be great to design a form in which we could insert custom data as well as built-in data (standard data). For instance, to have the ability to put the description field in a custom form.
Currently the form designer allows us to select only custom data and the project manager has to select a different section in project details to document built-in data. It might cumbersome. A structured presentation would ease the documentation.
I would like this so I can create a custom Project Creation form for all my users. We'd like to be able to not only default settings, but hide those settings so that users don't update those and we can get all the fields we want them to address into one screen.
Would also like to see this expanded so that standard fields could be used in logic, etc. (ex. like Status or Queue Topic), rather than logic being limited to using custom fields on the form, prior to that field.
I think this pretty much goes hand in hand with an idea I recently submitted. Upvoted!
Create a custom field within a custom form that is able to pull system information.
Take as an example the "Project Owner" system field which pulls a list of users within Workfront. Use case: Say that the Purchasing department requests a custom development to be done - The "Project Owner" is assigned to a member of said department and you can assign an "IT Leader" within a custom field so that both functional and technical parties can be accountable.
100% agree! this should absolutely exist. We are finding we are having to create these custom fields and then manage data in two places...quite counter productive when WF is supposed to exist as one version of the truth.
also to add to this, how can we have a pre-populated Dropdown/checkbox /text box any field in a custom form (not hardcoded values)
for example if I want a dropdown of all my existing Programs/Portfolios in my request custom form, then this feature is currently missing
Yes, we really need this for PTO request queues to allow planned start/end dates on a custom form where you can REQUIRE it to entered. Thanks!
Another way this would help is with the Business Case. Currently all the native (aka standard) fields are at the top of the Business Case. We have additional fields we need, so we create a Project Custom Form. We attached the form & it shows in the Business Case, BELOW the native fields.
My organization feels that even though we can now capture our required information, it is disjointed because i cannot inter-twine the custom fields with the native fields.
Upvoted! We frequently run into a situation where certain items under a specific queue topic need one or more system fields to be present and currently the only way to enable this is to enable these system fields for every single queue topic within the same project.
The problem with this is that system fields (besides the title of the item) cannot be made mandatory. If system fields can be added to custom forms and given an option to make them required for that form that would be great!
Thanks for upvoting this idea!
Even though the idea looks very interesting and we will definately look at this possibility in the future. However, as for now I'm setting the status "Not Planned" as it does not fit in the roadmap for the upcoming 12 months.
I would still kindly ask you to continue adding your use cases here so that we can take those into future consideration.
Upvoted! The ability to direct a user to one single form for all relevant updates would significantly improve adoption. The only other option is to duplicate default/standard fields but that can case confusion since fields like status and condition are prominent on the top of the page.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.