Workfront Data Dictionary and Data Mart

[#1]

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 function within Forms, but for the entire Workfront database. 

There is nothing currently (I created a ticket in EL and this was confirmed). 

[#2]

Correct me if I'm wrong but would this be different for every company?  The way that we think about and use terminology definitely needs defining but I'm not sure if another org is also doing everything the same way.  We have specific ways that we use statuses, priorities, etc that might differ from others, never mind any sort of custom fields or forms.

[#3]

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.

[#4]

Adobe has extensive information about Workfront documented online, are you saying this information is missing from their documentation?

https://experienceleague.adobe.com/docs/workfront.html?lang=en

[#5]

@Richard__Carlson  you are correct.

I submitted a ticket to WF asking to help locate:

Workfront Data Dictionary and Data Mart

and 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.

[#6]

Chiming in here @Richard__Carlson and @MarkKo3 

Love the thoughts here. 

For clarity on this idea...are you looking for standard "native" Workfront Data insights or a place where you can keep track of all of your custom data? Also..is there a place within existing tool areas where you would expect to see this? 

There is quite a bit of information in the API explorer: https://developersupport.workfront.com/page-api-explorer.html that might meet some of your needs.  Search is by object. This might meet many of this idea viewers' needs but only covers those standard native fields.  Please enrich this idea with more specific details around your needs so we can start to harmonize.

Thank you  

[#7]

@ewanh  For all "native" elements provided within Workfront
I 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, description, etc.

[#8]

Thanks @MarkKo3 and totally agree.  Where would you want to see that information? In Workfront itself?  Linked from the API Explorer?  In our documentation? Don't care where it is as long as it has the elements needed? Or something else?  

Please note I'm asking this to get more clarity for folks to like or not.  Some people are looking for a place to capture custom field information (yes/no is connected to an integration).  Sounds like you are wanting more clarification on existing native fields. If you have more insight into the various elements like "definition, description, etc...", please add here.

Thanks for using the community and starting this conversation. 

[#9]

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.