fprgCtx change after livelink 9.7.1 update

lavesh_beerbul

Hello we have noticed in builder that when we are inspecting the feature fprgCtx after update 9 livelink 9.7.1

It is not the same as compared before update. we have less elements than before.

Any ideas will be greatly appreciated

thanks

Find more posts tagged with

Comments

Pramod_Mohandas

Hi Beerbul,

Is there a certain parameter that you are looking for within the program context assoc?

Thanks & Regards,

Pramod Mohandas

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Friday, June 14, 2013 4:02 PM
To: eLink Recipient
Subject: fprgCtx change after livelink 9.7.1 update

fprgCtx change after livelink 9.7.1 update

Posted bylavesh.beerbul@aerowecmworld.com (beerbul, lavesh) On 06-14-2013 06:30

Hello we have noticed in builder that when we are inspecting the feature fprgCtx after update 9 livelink 9.7.1

It is not the same as compared before update. we have less elements than before.

Any ideas will be greatly appreciated

thanks

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful.

lavesh_beerbul

Hello Pramod yes we are looking for elements inside the fprgCtx for example Dsession

After update here is the corresponding fprgCtx as shown below:

Before update here is the corresponding fprgCtx as shown below:

Any help will be greatly appreciated

Pramod_Mohandas

Hi Beerbul,

I am currently running the CS 10 SP2 version and I placed a breakpoint on a simple WebNode Action-Browse script. AFAIK, it is exactly the same as your previous LL 9.7.x version & have everything intact.

Are you sure that the functionality on which you are breaking requires a DAPI session for its execution and that the user is just like any other CS user with normal permissions?

Can you tell me which function is it that you are specifically looking at?

lavesh_beerbul

Hello pramod,

The code i am using is the DAPI.GetNodeByID(.fPrgCtx.Dsession().fsession,DAPI.BY_DATAID,argId).

Before the update 9 of livelink 9.7.1 it was working correctly and i tested also with update 1 of livelink 9.7.1 but in vain. I noticed that as from update 1 it fails.

Everywhere i am using .fPrgCtx in the code it is not working with update of livelink.

Thank you very much for your kind help

Pramod_Mohandas

Are you absolutely sure that those image captures are for the same functionality before and after the update of LL versions?

Also, where are you breaking in your first image capture (your old LL session) ?

lavesh_beerbul

Yes i am sure the first image is after update 9 where there is .fPrgCtx (unreserved) and the second image is before update where .fPrgCtx (PrgSession).

Pramod_Mohandas

Can you please also answer my second query as to in which script are you placing your breakpoint in your older version of LL?

lavesh_beerbul

After update on the builder we get the error as "can only call Scripts or external API Functions" in the script where we get the line "DAPI.GetNodeByID(.fPrgCtx.Dsession().fsession,DAPI.BY_DATAID,argId) ".

This is because in .fPrgCtx there is no Dsession element as i have inspect the .fprgctx in builder.

Therefore before update i put a break point in the same script where it fails and inspect the .fPrgctx and i notice that there is more elements

Ian_Whitfield

Hi Lavesh,

In your screenshot it seems that the fPrgCtx feature does not reference a PrgSession object. Instead it references the Unreserve AuditEvent object which can be found under LLIAPI:LLIApi Root:AuditEvent. Since this is not a PrgSession object it will never contain the DSession script as a feature and the line of code will trace.

Which object is fPrgCtx a feature of in your screenshot? What type of request is this?

There are no known issues relating to this. I would advise breakpointing the line you mentioned again and then go back up the stack to see at which point the prgCtx feature was set to reference the AuditEvent object rather than a PrgSession object.

Regards
Ian