v9 LiveReports Against Workflow Attributes << One more time... >>

Bob_De_Garmo_(degarmob_(Delete)_2518944)

I know this has been asked before, but I've yet to see a decent answer to it... How can one write an effective report against Workflow Attributes in LL9? Open Text, has anyone solved this one yet? If not, is there a planned solution? I'm held up implementing a Livelink v9 server upgrade until this is resolved...

Find more posts tagged with

Comments

Alex_Kowalenko_(akowalen_(Delete)_2285456)

It depends on what you want...Nevertheless, workflow attribute data are stored in the WFAttrData table for each workflow and sub-workflow and in the WFAttrDataVersions table for each step of each workflow and sub-workflow.The key to accessing values from the attribute tables is using the correct attribute identifier. You can determine this identifier by moving the mouse over the attribute name in the workflow map attributes definition screen and noting the number 'n' in the text "javascript: editAttrSubmit('n')" at the bottom of the page.You relate the sttribute tables to the other workflow tables such as WMap, WSubWork, DTree (for workflow subtypes) and other tables to get your report. (Use the Livelink schema document as a guide)For example, to find the dates and status of all workflows base on a workflow map called "My Workflow" where custom attribute "My Nickname" (with attribute identifier of '2') is equal to 'Alex' you can execute the following SQL query:select subwork_dateinitiated "Initiated", subwork_datecompleted "Competed", subwork_status "Status", subwork_title "Title" from wfattrdata, wsubwork, wmap, dtree where dtree.name = 'My Workflow' and map_mapobjid = dtree.dataid and map_mapid = subwork_mapid and wf_id = subwork_subworkid and wf_attrid = 2 and wf_valstr = 'Alex'

Bob_De_Garmo_(degarmob_(Delete)_2518944)

Okay... I think I understand, and will look at it. This doesn't solve the problem with dynamically obtaining the Attribute Name, but I reckon in reality those don't change very often, so they will need to be hard-coded into the SQL as literal strings.btw: I've not obtained the new schema doc yet, but its on its way according to Gino Marroso.Thanx Alex! I << we >> appreciate your help!!!

Mike_Oliver_(MorningstarUser3_(Delete)_1426757)

We are making a workflow for one of our customers and have to make reports with it. Of course we will export and import the workflow and the attributes will get a different ID. That is the reason we do not want to report on the ID but on the attribute name. We can nowhere find this attribute in the *wonderful* database documentation.Does someone know where to find this?

Bob_De_Garmo_(degarmob_(Delete)_2518944)

Hey Becky... All I can say is Good Luck! The ONLY place I've been able to find the Attribute Names in the database is in the WMap Table, embedded within an Assoc in the Map_InitiateCb column. It would take some seriously magical SQL to extract them out and use the names from there though. And I would think that even if you could do that, the performance would be abysmal.Best suggestion I have is to code your reports with the Attribute IDs, and to check the Attribute IDs once you have imported the map into the customer's server.I have not experimented with it much, so I really do not know if these tend to change a lot...Best regards...

Alex_Kowalenko_(akowalen_(Delete)_2285456)

Attribute definitions are actually stored in documents referred by DTree SubType 128 objects. This of course, does not help the SQL query access method. What's missing is a "CatRegionMap" or similar table for workflow attributes that allows you to map attribute names to ids.By the way you can extract assoc values embedded in table fields through database functions. See an earlier post in this discussion for details at...https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2436834&objAction=view