Change case category via oscript 2

[zyoung1002]

Hi,

I got a problem that I have to change the category value dynamically for a case(the same idea as document), can I do that via Oscript(because I have to trigger the event script in workflow)?

I just found that most of the solutions are based on LAPI, and can I trigger java script in workflow?

Thanks very much!

 

[appnair]

Not sure what you are asking here.Event Scripts are oscript that get called when any suitable event on the processing of a livelink workflow occurs.You have mostly everything at your disposal so you can do things in the libabry(docs,case etc).
I am not sure where javascript is needed in this.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[zyoung1002]

Thanks, appnair.

I just want to know if I can change the category value of a case via oscript, because I saw a lot of solutions are based on LAPI using java or C#, so I wonder if it has to be done using LAPI, how can I trigger the script code(java or C#)via livelink workflow.

 

[ggriffit]

Yes you can, if you are working with an Event Script in Livelink Workflow you should have all the available resources you need to do this. The sample Code at

https://knowledge.opentext.com/know...bjId=3499041&objAction=ArticleView&viewType=1

shows you how to do this, once you have run the

f.DBGet()

command you can update the contents of

f

before running

f.DBPut()

to save it all back.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[appnair]

my guess is that lapi solutions in java and C# predominantly because of the better availability of those programmers.Also lapi code does not have to be installed on the livelink server,it really is client based in contrast oscript is developed in your own module and has to be installed on the livelink server.Some orgs tend to think negative of oscript so have to live with lapi or web service workarounds.Having said that lapi gives you access to most of library and workflow objects.If the case management frame work did not put its api out you will face difficulties but if it is a container then my guess is that it may still work.I would bet that for your project staying in true oscript will give you the maximum flexibility

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[zyoung1002]

Thanks for all your reply, you guys are really nice.

 

[zyoung1002]

I used this to set the value

f.fData[1].Values[1].(attrID).Values[1] = value

But how can I handle that if the type is date?

 

[ggriffit]

Suggest you look at how an existing Date object is presented in the F Frame and see if you can add a date in there.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[zyoung1002]

Thanks, I have already fixed that.