UpdateWorkPackage(...) causes exception

If I call the UpdateWorkPackage() method on a LAPI_WORKFLOW object I get the exception...Exception in thread "main" com.opentext.api.LLIllegalOperationException: get(name) not implemented for this datatypeI even get this if I call AccessWorkPackage() to get the workpackage and just pass it right back in to UpdateWorkPackage(). Has anyone gotten UpdateWorkPackage() to work? Or is there another way to update fields in the workpackage?

Find more posts tagged with

Comments

Kevin_Ward

Message from Kevin Ward <<A HREF="mailto:kward@opentext.com">kward@opentext.com> via eLink

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

Glenn,

This is most likely a problem with your specific map. I've successfully used these functions on a base workflow map consisting of a few steps and attributes. However, I've not tested them with forms attached to the workflow. I suggest opening a ticket with support (support@opentext.com) and they can help debug the problem. There's a chance it's a bug but in these cases there's often a workaround.

Kevin

-----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: April 22, 2003 11:27 AM
To: eLink Recipient
Subject: UpdateWorkPackage(...) causes exception

UpdateWorkPackage(...) causes exception Posted by SCorUser8 (Heying, Glenn J) on 04/22/2003 11:16 AM

If I call the UpdateWorkPackage() method on a LAPI_WORKFLOW object I get the exception...

Exception in thread "main" com.opentext.api.LLIllegalOperationException: get(name) not implemented for this datatype

I even get this if I call AccessWorkPackage() to get the workpackage and just pass it right back in to UpdateWorkPackage(). Has anyone gotten UpdateWorkPackage() to work? Or is there another way to update fields in the workpackage?

x-scoruser8_-_(deleted)

This is one test that I've done that still causes the exception. I've tried it with a variety of values in the second parameter and still gotten the exception. Would anyone mind taking a look and telling me if you see anything obviously wrong with what I've doing? I have also successfully changed parts of the workpackage and verified the change before calling the update method which still throws the exception on the call.LLValue workPackage;workPackage = new LLValue().setTable();LAPI_WORKFLOW workLAPI;workLAPI = new LAPI_WORKFLOW(gSession);if(workLAPI.AccessWorkPackage(iWfID, 0, workPackage) == LL_OK) { workLAPI.UpdateWorkPackage(iWfID, iWfID, workPackage);}

x-scoruser8_-_(deleted)

Here's the call stack that's reported with the exception. Any idea what I'm doing wrong? As I mentioned earlier, I'm merely Updating with the workpackage returned in AccessWorkPackage. I've verified that the workpackage contains the expected data.at com.opentext.api.LLInstance.get(LLInstance.java:72)at com.opentext.api.LLValue.toValue(LLValue.java:691)at com.opentext.api.LLConnect.unMarshall(LLConnect.java:317)at com.opentext.api.LLConnect.unMarshall(LLConnect.java:328)at com.opentext.api.LLSession.unMarshall(LLSession.java:100)at com.opentext.api.LAPI_WORKFLOW.UpdateWorkPackage(LAPI_WORKFLOW.java:407)

Kevin_Ward

Message from Kevin Ward <<A HREF="mailto:kward@opentext.com">kward@opentext.com> via eLink

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

Glenn,

I don't believe you're doing anything wrong. Livelink should be handling your UpdateWorkPackage correctly. It's looks like a problem inside Livelink that Jeremy can help you debug (I believe you have a ticket with him). The best approach is for us to attempt to replicate the error after obtaining some more detailed information about your system and workflow. There's also a LAPI logging patch which may log useful information but Jeremy will decide if it's necessary or not after having a look.

Kevin

-----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: April 23, 2003 2:12 PM
To: eLink Recipient
Subject: UpdateWorkPackage - more information

UpdateWorkPackage - more information Posted by SCorUser8 (Heying, Glenn J) on 04/23/2003 02:08 PM
In reply to: UpdateWorkPackage(...) causes exception Posted by SCorUser8 (Heying, Glenn J) on 04/23/2003 10:10 AM

Here's the call stack that's reported with the exception. Any idea what I'm doing wrong? As I mentioned earlier, I'm merely Updating with the workpackage returned in AccessWorkPackage. I've verified that the workpackage contains the expected data.

at com.opentext.api.LLInstance.get(LLInstance.java:72)
at com.opentext.api.LLValue.toValue(LLValue.java:691)
at com.opentext.api.LLConnect.unMarshall(LLConnect.java:317)
at com.opentext.api.LLConnect.unMarshall(LLConnect.java:328)
at com.opentext.api.LLSession.unMarshall(LLSession.java:100)
at com.opentext.api.LAPI_WORKFLOW.UpdateWorkPackage(LAPI_WORKFLOW.java:407)

eLink User

Message from Eidson Matthew W Contr AFFTC/ITASC <<A HREF="mailto:Matthew.Eidson@edwards.af.mil">Matthew.Eidson@edwards.af.mil> via eLink

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

Kevin,

A little off the topic but you mentioned a LAPI logging patch?

Can you elaborate on that a little more?

Thanks,

Matt Eidson
AFFTC/ITASC
Livelink Integrator/Developer - Network Systems Analyst
Tybrin Corporation
Office: 661-275-3704
Mobile: 661-810-6091
Nextel DC: 122*11*6004

-----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Wednesday, April 23, 2003 11:33 AM
To: eLink Recipient
Subject: RE UpdateWorkPackage - more information

RE UpdateWorkPackage - more information		Posted by kward (Ward, Kevin) on 04/23/2003 02:32 PM
In reply to: UpdateWorkPackage - more information		Posted by SCorUser8 (Heying, Glenn J) on 04/23/2003 02:08 PM

Message from Kevin Ward <kward@opentext.com> via eLink

Glenn, I don't believe you're doing anything wrong. Livelink should be handling your UpdateWorkPackage correctly. It's looks like a problem inside Livelink that Jeremy can help you debug (I believe you have a ticket with him). The best approach is for us to attempt to replicate the error after obtaining some more detailed information about your system and workflow. There's also a LAPI logging patch which may log useful information but Jeremy will decide if it's necessary or not after having a look. Kevin -----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: April 23, 2003 2:12 PM
To: eLink Recipient
Subject: UpdateWorkPackage - more information

UpdateWorkPackage - more information		Posted by SCorUser8 (Heying, Glenn J) on 04/23/2003 02:08 PM
In reply to: UpdateWorkPackage(...) causes exception		Posted by SCorUser8 (Heying, Glenn J) on 04/23/2003 10:10 AM

Here's the call stack that's reported with the exception. Any idea what I'm doing wrong? As I mentioned earlier, I'm merely Updating with the workpackage returned in AccessWorkPackage. I've verified that the workpackage contains the expected data.

at com.opentext.api.LLInstance.get(LLInstance.java:72)
at com.opentext.api.LLValue.toValue(LLValue.java:691)
at com.opentext.api.LLConnect.unMarshall(LLConnect.java:317)
at com.opentext.api.LLConnect.unMarshall(LLConnect.java:328)
at com.opentext.api.LLSession.unMarshall(LLSession.java:100)
at com.opentext.api.LAPI_WORKFLOW.UpdateWorkPackage(LAPI_WORKFLOW.java:407)

Kevin_Ward

Message from Kevin Ward <<A HREF="mailto:kward@opentext.com">kward@opentext.com> via eLink

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

Sure Matt,

The LAPI code in Livelink has some built-in functionality that logs LAPI information. Specifically, it logs all LAPI data passed to Livelink and all data returned (in assoc format). Unfortunately, this logging is not exposed to the opentext.ini file so it can be turned on. Instead, it must be turned on internally, through a custom module or patch. The patch we have simply sets $APILog = TRUE in the APIDispatch function in Builder. The already existing code then echoes the LAPI input and output to the Livelink thread logs.

It's actually quite rare that Product Specialist's need to use this patch. Most of the time there is either LAPI error codes or the connect logs tell the tale. Where this patch is most useful is when customer's are having problems with a 3rd party application that uses LAPI and the application does not have sufficient logging.

Kevin

-----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: April 23, 2003 2:47 PM
To: eLink Recipient
Subject: RE RE UpdateWorkPackage - more information

RE RE UpdateWorkPackage - more information Posted by eLink on 04/23/2003 02:47 PM
In reply to: RE UpdateWorkPackage - more information Posted by kward (Ward, Kevin) on 04/23/2003 02:32 PM

Message from Eidson Matthew W Contr AFFTC/ITASC <Matthew.Eidson@edwards.af.mil> via eLink

Kevin, A little off the topic but you mentioned a LAPI logging patch? Can you elaborate on that a little more? Thanks, Matt Eidson
AFFTC/ITASC
Livelink Integrator/Developer - Network Systems Analyst
Tybrin Corporation
Office: 661-275-3704
Mobile: 661-810-6091
Nextel DC: 122*11*6004 -----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Wednesday, April 23, 2003 11:33 AM
To: eLink Recipient
Subject: RE UpdateWorkPackage - more information

RE UpdateWorkPackage - more information Posted by kward (Ward, Kevin) on 04/23/2003 02:32 PM
In reply to: UpdateWorkPackage - more information Posted by SCorUser8 (Heying, Glenn J) on 04/23/2003 02:08 PM

Message from Kevin Ward <kward@opentext.com> via eLink

Glenn, I don't believe you're doing anything wrong. Livelink should be handling your UpdateWorkPackage correctly. It's looks like a problem inside Livelink that Jeremy can help you debug (I believe you have a ticket with him). The best approach is for us to attempt to replicate the error after obtaining some more detailed information about your system and workflow. There's also a LAPI logging patch which may log useful information but Jeremy will decide if it's necessary or not after having a look. Kevin -----Original Message-----
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: April 23, 2003 2:12 PM
To: eLink Recipient
Subject: UpdateWorkPackage - more information

UpdateWorkPackage - more information		Posted by SCorUser8 (Heying, Glenn J) on 04/23/2003 02:08 PM
In reply to: UpdateWorkPackage(...) causes exception		Posted by SCorUser8 (Heying, Glenn J) on 04/23/2003 10:10 AM

Here's the call stack that's reported with the exception. Any idea what I'm doing wrong? As I mentioned earlier, I'm merely Updating with the workpackage returned in AccessWorkPackage. I've verified that the workpackage contains the expected data.

at com.opentext.api.LLInstance.get(LLInstance.java:72)
at com.opentext.api.LLValue.toValue(LLValue.java:691)
at com.opentext.api.LLConnect.unMarshall(LLConnect.java:317)
at com.opentext.api.LLConnect.unMarshall(LLConnect.java:328)
at com.opentext.api.LLSession.unMarshall(LLSession.java:100)
at com.opentext.api.LAPI_WORKFLOW.UpdateWorkPackage(LAPI_WORKFLOW.java:407)