Setting User Picker attribute through oscript in workflow

Hi,

I am new to oscript development. And I am trying to set value in User picker type workflow attribute using script, but have been unsuccessful in doing so till now. Can someone help me with a script to save user picker attribute value?

Thanks.

Find more posts tagged with

Comments

eLink User

Can you elaborate with some word document,screen caps?The question is not fully understandable by the forum.For me I am confused on the userpicker attribute.in your question.Do you have that piece HTML going,but are you saying that you can selact a user using that but nothing your ll workflow can use.

If you elaborate you will probably get better answers and don't worry about your "newnsess" in this.

.....appu appnair appunair

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Thu, Mar 10, 2016 at 1:20 PM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

Setting User Picker attribute through oscript in workflow Posted byJohnson, DuranOn 03/10/2016 02:16 PM

Hi,I am new to oscript development. And I am trying to set value in User picker type workflow attribute using script, but have been unsuccessful in doing so till now. Can someone help me with a script to save user picker attribute value? Thanks.
[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Content Server: Knowledge Center

Duran_Johnson

I am trying to write a script which can populate a workflow attribute which is of type User Field, by that I mean that when I see the workflow attributes, I want to see the user name populated. I am easily able to populate Text Fields using the same script, but not able to populate the user Attribute. I know user attribute is type Integer and I am getting the user id from the KUAF table. Now the challenge is how to show that user name in the WF Attributes. I also saw at some places that I would need XML Workflow Extensions to do this, and at this point of time we cannot go by buying that module. Isn't there a script that can do this?

Thanks.

eLink User

I am still not getting it? If I have a wf screen on which I put a User Attribute (wf attribute ) and I show that step to the user in a browser

the user is going to invoke the user picker thingy that you talk about.Then they will be taken to a search screen where they type in a user by last name ,first name etc.

This is what you want to be automatic?

Or is the WF front ended by a form template/webform?

if you have the wf data structure then just like you assign the text attribute is how you assign the user attribute.

Inside livelink wflow the user attribute is stored with kuaf.id .Just like you get the id from kuaf you can

get the other parts like name,firstname etc.

Perhaps more learned people will advise I give up

.....appu appnair appunair

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Thu, Mar 10, 2016 at 3:49 PM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

Re Setting User Picker attribute through oscript in workflow Posted byJohnson, DuranOn 03/10/2016 04:46 PM

I am trying to write a script which can populate a workflow attribute which is of type User Field, by that I mean that when I see the workflow attributes, I want to see the user name populated. I am easily able to populate Text Fields using the same script, but not able to populate the user Attribute. I know user attribute is type Integer and I am getting the user id from the KUAF table. Now the challenge is how to show that user name in the WF Attributes. I also saw at some places that I would need XML Workflow Extensions to do this, and at this point of time we cannot go by buying that module. Isn't there a script that can do this?Thanks.
[To post a comment, use the normal reply function]
Topic: Setting User Picker attribute through oscript in workflow
Forum: Content Server Development Forum
Content Server: Knowledge Center

Duran_Johnson

Thanks Appu. I got it finally. Yes, you are right, User attribute is set in the same way as a Text Attribute, except that small [1] which needs to be there.

for text field: valueAssoc.Values[ 1 ].(id).Values = "text"

for user field: valueAssoc.Values[ 1 ].(id).Values[1] = userID

Thanks.

Hans Stoop

Hi Duran,

I haven’t done anything with WF attributes in a long while, but I think the proper way to code it is

for text field: valueAssoc.Values[ 1 ].(id).Values = {"text"}

for user field: valueAssoc.Values[ 1 ].(id).Values = {userID}

An WF attribute can have multiple values and therefore the values should always be a list even when it contains only one value.

Hans

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Freitag, 11. März 2016 06:11
To: eLink Recipient
Subject: Re Re Setting User Picker attribute through oscript in workflow

Re Re Setting User Picker attribute through oscript in workflow

Posted by Johnson, Duran On 03/11/2016 12:07 AM

Thanks Appu. I got it finally. Yes, you are right, User attribute is set in the same way as a Text Attribute, except that small [1] which needs to be there.

for text field: valueAssoc.Values[ 1 ].(id).Values = "text"

for user field: valueAssoc.Values[ 1 ].(id).Values[1] = userID

Thanks.

[To post a comment, use the normal reply function]
Topic:	Setting User Picker attribute through oscript in workflow
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

eLink User

Hans is correct as always.Think of it as a list {,entry1,entry2,entry3} then the GUI would put the + icon (MVA)

I also think I would have understood if you said it was a event script or some other way.In work flows usually people

write custom code in general event scripts,performer event scripts and sub map event scripts they are all oscript

all said and done.I also do workflows with forms/form templates and generally use javascript to do some

of the assignments etc.

.....appu appnair appunair

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Fri, Mar 11, 2016 at 3:19 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

RE Re Re Setting User Picker attribute through oscript in workflow Posted byStoop, HansOn 03/11/2016 04:19 AM

Hi Duran, I haven’t done anything with WF attributes in a long while, but I think the proper way to code it is for text field: valueAssoc.Values[ 1 ].(id).Values = {"text"}for user field: valueAssoc.Values[ 1 ].(id).Values = {userID}An WF attribute can have multiple values and therefore the values should always be a list even when it contains only one value. Hans From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Freitag, 11. März 2016 06:11
To: eLink Recipient
Subject: Re Re Setting User Picker attribute through oscript in workflow

Re Re Setting User Picker attribute through oscript in workflow

Posted by Johnson, Duran On 03/11/2016 12:07 AM

Thanks Appu. I got it finally. Yes, you are right, User attribute is set in the same way as a Text Attribute, except that small [1] which needs to be there.

for text field: valueAssoc.Values[ 1 ].(id).Values = "text"

for user field: valueAssoc.Values[ 1 ].(id).Values[1] = userID

Thanks.

[To post a comment, use the normal reply function]
Topic:	Setting User Picker attribute through oscript in workflow
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

[To post a comment, use the normal reply function]
Topic:	Setting User Picker attribute through oscript in workflow
Forum:	Content Server Development Forum
Content Server:	Knowledge Center