Workfront doesn't decide, that's determined by the user themselves. From the Work List on the Home screen, one of the things they can do when they have a work item selected is say 'Add to My Priority' for up to 20 items.

In my instance, this is a column calculation and grouping calculation that produce the correct weighted averages expected. You can use valueexpression in the aggregator portion of your text mode, though it does require some fiddling. Here's a tutorial with some other examples that sound more like yo...

The shortest solution would be to add one more field: Deliverable Types Needed that's required and have your 6 options in that selection menu. Then hide/unhide your fields in the screenshot based on what the user said was needed. Required field logic would function more smoothly then as well. That w...

In our instance, I ultimately disabled auto-provisioning for a host of security, duplicate-account prevention and general chaos-prevention. I don't know if your instance is a size where cloning existing user accounts is a feasible method of creation, but the accidental side-benefit of disabling auto...

Funny enough, I was asked about trying to mirror something similar just the other day.  With respect to the 'Talk to me about' field, you are correct that it's a giant open-text field you could put data like that in. I would caution that it's also user-editable, and it may not be obviously intuitive...

Hi James, The column you want is 'setMyInfo'.  The Kick-Start functionality is for the creation of new records only, it cannot modify data that's on already existing records.  The best resources for learning the import templates are either the API Explorer, or by exporting the existing data and revi...

Ultimately, this issue is a large part of why I disabled auto-provisioning in our instance. Too much chaos, and too many panicked users that thought their entire account had been wiped out. Until I finally gave up though, my best option was to have a report that automatically emailed me any newly pr...

You can get part of the way there with automation, though not 100%. What I do is create an Update module that says 'take the data from the legacy field, and put it in the new field' but I wrap the value in a parseNumber() formula first, and then tell Fusion to remove the value from the legacy field ...

Ooh boy, that's a painful one! I've been through that before myself. Assuming you have too much data to simply copy/paste, then Fusion or Doug's solution below are your main options. If Fusion is available to you, I can give some notes on how I set my scenario up when it was my turn for that cleanup...

Your options partly depend on the nature of the data in the existing field, and how many records already contain data in it. I'm also assuming that simply renaming your field's form display name, or re-labeling report column headers to clarify isn't an option here?  When I've had minimal records tha...