Update workflow roles after initiation

Hello:

We have a need to update the user assigned to perform a role to a different user, upon the workflow initiation; This is required to allow the user to assign someone else in the role during his/her absence. Workflow proxy option has a limitation in that one cannot select different users for different workflows that belong to the user; All workflows of the user can only have one proxy user;

Roles defined in our workflow are driven by form template fields that are selected during initiation of the workflow; If we update the latest row (VERSIONNUM=-1) of the table for form template, given the workflow ID, would that be sufficient to make Livelink list the NEW user for all subsequent steps that were originally assigned to the user?

Please let me know your thoughts;

Find more posts tagged with

Comments

Appu_Nair

I would approach this requirement a little differently,but your research shows that you have found what you want to change to make this work,that is commendable.In livelink generally you never mess with updating tables.This is simply bacause livelink uses oscript code to change more than one table to make the software do its things,you may hear terms such as call backs et al.So if I wanted to change a perfomer ,I would use the call

ReassignTask of the WAPI package.One would just simply search for that command  in builder and see the prototype of how OT programmers uss that.  Similarly one would use available functions of form to update the changes you have.  If DB updates were your only way,while it is unsupported one could do this I guess. On a small test server,you would bump up logging with debug=2 and wantlogs=true, you would then use the GUI to change things around and look in the connect logs to see which all tables changed with what you just did in the GUI.Mostly as my esteemed friend Donna would say,if you see a corresponding command in the GUI one could most certainly trace that code in builder and do ones manipulations effectively rather than trying hacks into the database.  If you have third party tools like Web reports work flow extensions,I would check its tag library for any available syntax as well.

Sravan_Kudithipudi

Thank you for your response; The problem though is that we would like the roles and the steps using the role be replaced after the workflow is initiated;

Using reassign a task, we would need to remember the task IDs of step and code is not extendable for other workflows; Also, if there is a subworkflow that gets initiated, tasks would not be reassigned to the new user;

Any other thoughts?

Andrew_Foti

I’m not sure if I understand your question fully. You canalso use a workflow attribute user field instead of roles. Then assign steps basedon that particular attribute. It is better than a role because the attribute(and then future step assignees) can be changed after the workflow is initiatedwhereas roles cannot be changed once a wf starts.

Andrew

From: eLink Entry: Content Server Builder Forum[mailto:componentbuilder@elinkkc.opentext.com]
Sent: Wednesday, 15 September 2010 4:02 PM
To: eLink Recipient
Subject: Update workflow roles after initiation

Update workflow roles after initiation

Posted by welfar01user15 (Kudithipudi, Sravan) On 2010/09/15 01:59

Thank you for your response; The problem though is that we would like the roles and the steps using the role be replaced after the workflow is initiated;

Any other thoughts?

[To post a comment, use the normal reply function]
Topic:	Update workflow roles after initiation
Forum:	Content Server Builder Forum
Livelink Server:	knowledge-wlweb01

Jim_Coursey_(inactive)

You should use user fields on a form. You can have defaultvalues for one or more users, change users in different roles at almost anystep, and flow the same user field entries down to sub-workflows in addition tobeing able to change those users at almost any step in a sub-workflow. Thelatest selected users flow back up to the parent workflow when the sub-workflowends.