Trying to find the workflow status in the database?

505 views
339 views

Published on

Our help desk recently fielded a support ticket from a company looking for assistance with their extraction of PSR content. Specifically, they could not identify how to extract the PSR number, the workflow name and workflow state. One can be very quick to jump to the conclusion that workflow states are list items and should reside in the listentry table, but that is not the case.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
505
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Trying to find the workflow status in the database?

  1. 1. Trying to find the workflow status in the database? Hint - Workflow status' aren't list values...
  2. 2. Introduction Our help desk recently fielded a support ticket from a company looking for assistance with their extraction of PSR content. Specifically, they could not identify how to extract the PSR number, the workflow name and workflow state. One can be very quick to jump to the conclusion that workflow states are list items and should reside in the LISTENTRY table, but that is not the case.
  3. 3. Examine PSR Table Let's examine a simple result set with the PSR number, workflow and workflow state by executing: select psr_no, workflow_id, status from psr; As you can see, we have an empty PSR record, which is easy to filter out by adding a where clause to our query. The harder thing to figure out is where to find the human readable versions of workflow_id and status.
  4. 4. Looking to NODETABLE for Help If you think about the Java Client, you'll realize that a workflow state is actually a type (or node), not a simple list value. These exist in NODETABLE, so we can add some joins and pull in the appropriate values: select psr_no as psr, flow.description as workflow, state.description as state from psr left join nodetable state on (state.id=psr.status) left join nodetable flow on (flow.id=psr.workflow_id) where psr_no is not null;
  5. 5. Looking to NODETABLE for Help (cont) Now we can see that the values are being pulled out correctly.
  6. 6. Comparing with Agile
  7. 7. About Us  PLM Mechanic specializes in the technical aspects of Oracle’s Agile PLM solution  We offer the following service: – Agile PLM installations and upgrades – Agile PLM maintenance and help desk functions – Agile PLM hosting – Customization  PLM Mechanic also has several product offerings
  8. 8. Contact Us  Web: http://www.plmmechanic.com  Blog: http://www.plmmechanic.com/blog  Twitter: @PLMMechanic  Email: sales@plmmechanic.com  Phone: 512-827-2262  Fax: 512-582-2932

×