Select to view content in your preferred language

How to access and include extended properties information in dashboards?

253
3
Jump to solution
02-29-2024 08:55 AM
Ulises
by
Occasional Contributor III

We are transitioning to Workflow Manager for Server.  Since there is no reports functionality as in classic we are not sure how to access the data to prepared and show information using dashboards, especially in real time.  How to include extended properties data and other information from the workflow service so it can be use in dashboards???

 

Any help is greatly appreciated.

 

Ulises Feliciano Troche
0 Kudos
1 Solution

Accepted Solutions
Ulises
by
Occasional Contributor III

Just in case this can be useful to others...

I managed to found a workaround for this...create yet another extended property to capture the user that runs the steps nearly at the end of the workflow.  Looks like a lot of my requirements will probably be somehow related to try extended properties even for data that already exists in a table or view.

Ulises Feliciano Troche

View solution in original post

0 Kudos
3 Replies
OscarZepeda4
New Contributor

When you create a workflow item in the portal, 1 hosted feature service and 2 views (from said hosted feature service) are created. Within these portal items are a collection of layers and tables that contain a good majority of information about your workflow item and jobs (to include extended property tables). You will need to look at the "jobExtPropertyTableDefinition" table within the main service to identify what additional tables are "extended property tables" as they are labeled under their table id and not the table alias.

0 Kudos
Ulises
by
Occasional Contributor III

Hi @OscarZepeda4, sorry for the delay on this.  Thanks for the feedback.  I found and use the data on the items mentioned but there are still some information I have not been able to access that is important for what we want to do.  We are trying to get the user that complete a job so we can create a filter, among other things, of the number and details of jobs closed by a specific user.  At this point once a job is closed and dismissed it appears unassigned.  Any suggestions are welcome.

Thanks

Ulises Feliciano Troche
0 Kudos
Ulises
by
Occasional Contributor III

Just in case this can be useful to others...

I managed to found a workaround for this...create yet another extended property to capture the user that runs the steps nearly at the end of the workflow.  Looks like a lot of my requirements will probably be somehow related to try extended properties even for data that already exists in a table or view.

Ulises Feliciano Troche
0 Kudos