I would imagine best place would be within Workfront itself, so that as elements get added, moved, etc, an internal to Workfront location of this resource could reflect any changes, similar to how the Forms one does.

@ewanh  For all "native" elements provided within WorkfrontI was already provided with that API Explorer link, however does not provide much insightful information -- imagine trying to build a report with a CIO who does not know what data is captured within Workfront, does not have a definition, des...

@Richard__Carlson  you are correct.I submitted a ticket to WF asking to help locate:Workfront Data Dictionary and Data Martand they responded it does not exist and it might be best to create an 'Idea' in Experience League, and so I have created this post requesting them.

At the core of a provided system, there should be baseline definitions of data elements. If an organization chooses to use them differently that is their prerogative. 'Status' does one thing, but yes, how you use it can differ.

We would like to see all fields in Workfront defined and mapped out for reporting and report building purposes.  i.e. clearly lay out what data fields are in Workfront.To facilitate report building discussions, to have available for onboarding, and to define field purposes. Similar to how there is a...

Thank you all! Really looking forward to sharing this presentation, and incorporated ideas and structure, with my WF and PMO teams ... actually, I need to build my WF Governance Team, officially, first... cheers and thanks again!

Hello ... I'm a newish WF Admin, moving over to NE, and in doing so I am reviewing our internal Access Levels, and trying to work out the Next Steps of getting broader institution access to WF, which is quite limited now... I don't know if what is being asked above is the same as this ask, but, I wo...

I totally agree with you @Laurence Jayawardane

Perfect, easy solution. Thanks 