Attributes, Workflow, and Inheritance

I have created a custom attribute for a workflow. The attribute holds a selected folder objID and an assoc value that will hold the categories and attributes that the folder has (This information will be used to move a document to another folder automatically without the user entering in the category information) . I want to be able to populate that assoc value with the cats and atts of the selected folder from within the attributes page in the workflow.The end result of all of this is to move a new document that has been submitted to the system from a specific unclassified folder to the selected production folder in the final approval step of the workflow. At the beginning steps of the workflow I want the document owners to be able to enter the attribute values for the selected folder that the document is going to be moved to (Similar to how the window pops up to enter the values of the cats and atts when you try to move a document natively in Livelink and select the destination option for the categories).So my question is how can I save, view, and update category data for a specific folder in a workflow attribute and then later apply that data to the document when I am moving it into its destination folder to satisfy the category inheritance?

Find more posts tagged with

Comments

Jeff_Lang_(lang_(Delete)_2245920)

Your new attribute type would have to be a string that appeared as multiple lines to be entered. The lines would hold the nodeID, and then different lines for each category and attribute. You would then need an event script to read the attribute value and apply this information to the document being moved.By the way, most of this functionality will be available in the next major release of Livelink. It will be part of the standard application.

eLink User

Message from <<A HREF="mailto:Bryan.Finney@gianteagle.com">Bryan.Finney@gianteagle.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">RE: RE Attributes, Workflow, and Inheritance

I am not sure how that works because of the caching Livelink uses when the user enters in the attributes during the move process. Each time our workflow runs the categories could be different depending on the location that they user is going to move the document to. So how would I make it flexible and dynamic enough to be able to handle this different scenarios. Also I need to remember that the users I am dealing with are very primitive users that are really just learning how to use the mouse. I need to somewhat be consistent on how they enter data into the system, therefore by showing a multi line text box would probably confuse them. I need to show the same or similar window Livelink shows when attributes are required during the standard move process.

You are saying this functionality will be available in the next major release of Livelink, when might this be? I need to have all of this working by the end of August.

eLink User

Message from Hans Stoop <<A HREF="mailto:hstoop@opentext.com">hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Hi Sharon,

I created a meeting with name 'Search Error'. I made you host of that meeting, so you should be able to see it.

It is at

https://intranet.opentext.com/intranet/llisapi.dll?func=ll&objid=15618208

If you search for objects with name 'Search Error' then this new meeting will be shown. I got the result as shown in the attachment. If I follow the "Search Error' link in the first result (e.g. behind location:) Then I get the error.

Hans

--------
Livelink Appearance: the best way to skin Livelink.
Contact hstoop@opentext.com for more information.

-----Original Message-----
From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: dinsdag 18 juni 2002 14:20
To: eLink Recipient
Subject: RE RE Attributes, Workflow, and Inheritance

RE RE Attributes, Workflow, and Inheritance Posted by eLink on 06/18/2002 08:19 AM
In reply to: RE Attributes, Workflow, and Inheritance Posted by lang (Lang, Jeff) on 06/17/2002 03:33 PM

Message from <Bryan.Finney@gianteagle.com> via eLink

I am not sure how that works because of the caching Livelink uses when the user enters in the attributes during the move process. Each time our workflow runs the categories could be different depending on the location that they user is going to move the document to. So how would I make it flexible and dynamic enough to be able to handle this different scenarios. Also I need to remember that the users I am dealing with are very primitive users that are really just learning how to use the mouse. I need to somewhat be consistent on how they enter data into the system, therefore by showing a multi line text box would probably confuse them. I need to show the same or similar window Livelink shows when attributes are required during the standard move process. You are saying this functionality will be available in the next major release of Livelink, when might this be? I need to have all of this working by the end of August.

Jeff_Lang_(lang_(Delete)_2245920)

Your custom attribute would have to activate a button or link after the destination object is selected. Your attribute code would have to look at that object and determine the categories and attributes that can be filled in. The user should then be forced to click that link or button and fill in the data. That data will then be stored with the attribute for use by an event script.

eLink User

Message from <<A HREF="mailto:Bryan.Finney@gianteagle.com">Bryan.Finney@gianteagle.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">RE: RE RE Attributes, Workflow, and Inheritance

Once I have the attribute values using:
result = llNode.NodeCategoriesGet( thisDapiNode )
What would be the easiest way to get the HTML for each of the attribute types? Is there a function I can use?

Jeff_Lang_(lang_(Delete)_2245920)

Look at the way workflow attributes are displayed. They use the same code as categories. Once you have the schema for the category you can just call the display for it just like workflow attributes do.

eLink User

Message from <<A HREF="mailto:Bryan.Finney@gianteagle.com">Bryan.Finney@gianteagle.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">RE: RE RE Attributes, Workflow, and Inheritance

I have a list of assoc's that store the attribute information in a single workflow attribute field. I can now move a document from one location to another in a general callback script and applied the cats and atts to the document from the destination location. Now I need to be able to update the cats and atts based on the wf list of assoc's that is stored in the workflow. How can I do this?

I am able to get the SegmentBlob by using:
Assoc result = $LLIApi.AttrData._DBGet(str.stringtoInteger(destValuesList[ 3 ]),originalNode.pVersionNum)
destAttrAssoc = str.StringToValue(result.BlobDataRecs[ 1 ].SEGMENTBLOB)
And I am able to update the segmentblob with the wf data but how do I update the data back to the database? I was trying to use the _DBPut by I can not seem to get the dataRecs values? Do you know a simple way of doing these?

Jeff_Lang_(lang_(Delete)_2245920)

You need to look at the objects in the WebAttribute ospace. Look at $WebAttriubute:WebAttribute Action:RunTimeAction and look at all the sub objects whose names start with AttrValue