Workfront Update a record module--custom fields

[KristenS_WF]

I'm building a scenario--triggered when fields on an issue-based custom form are updated--to change the issue status and record the date of the change in a custom field (DE:TestSubmittedDate).

I decided to try out the newer Update a record module (instead of the Update a record (Legacy) module), and it looks like the only way to map a custom field value is to choose a relevant form from the Attach Custom Form option--is this correct?

I checked the documentation for the module and for the Attach Custom Form option, it reads "Select the custom forms that you want to attach to the new record. After you select the form, enter the data for the fields on that form." (emphasis mine)

Uh... I'm updating an existing record--not creating a new one.  And since the scenario is triggered by changes to the custom form fields, obviously the custom form is already attached.

This doesn't appear to cause problems with my scenario, but the option name and supporting documentation are awkward, at best.

[Sven-iX]

100% agree. It's strange - but it does work fine. Thankfully it doesn't change the position of the existing form.

[JohnJOSullivan]

I've been confused by this as well. What is the value add for these new modules?

[ChrisStephens]

(I suspect) It's so that Fusion doesn't have to download every single custom field to render it available to choose from, which prevents the problem that occurs when there are too many fields in the environment and fusion modules start timing out just trying to open them.

[JohnJOSullivan]

This may be useful for some, but man. Every time Adobe tries to "help" me, it's never a help.

I'm working on an automation for two groups whose forms I'm not familiar with. So now, to get to the fields that I need, I have to look up which forms they're on in Workfront. That's annoying for sure, but this doesn't happen that often.

Okay, I find the forms, attach them...and now the only thing that displays is the field label instead of its name.

So now, how am I supposed to figure out how to map these fields?

We use the same labels for these fields as they display differently due to form logic. But now I can't easily map things unless I now do trial and error. 

Thank GOD I still have the ability to use the legacy modules. I'm planning on storing the legacy versions of these modules on a library scenario. 

This comes on the heels of Adobe "upgrading" our Adobe Admin Console which trashed both Workfront and Workfront Proof. I spent a whole week in troubleshooting and cleanup mode.

Sorry that I'm complaining but I really wish that there would be more improvements which don't make my work life more difficult.

-j

[KristenS_WF]

Yikes!  I noticed the label thing too, but that's really a pain.

If you submit an idea for making the field names display instead of labels, I'd definitely upvote it.

[JohnJOSullivan]

At this point, I'd say that the idea would be to allow legacy connectors for the foreseeable. If no one noticed this during UAT I'd be surprised.

[D____D]

I'm not sure why Adobe did this ... it wasn't broken TBH.