CPO integration with Remedy

[Tiberio Martinez]

Hi all,

I am integrating CPO with Remedy.  

I already copied the Remedy binaries into CPO and from CPO I can see all the Remedy forms so client, authentication, and rights are correct, but when I select a form I cannot see any fields.   

Has anyone seen this before? Any ideas?

Thx

[Tuan Tran]

I ran into this problem before.  But, it's working now for me with a newer version of CPO (3.4)

Which version of CPO are you running?

[Tiberio Martinez]

Thanks, Tuan

I'm running 3.4.  

No patches installed.

[deepti.musunuru1]

I am running CPO 3.4 version and have the same issues. If you have figured out the solution, could you please share that information. 

[Tiberio Martinez]

Hi, Deppti.

We applied Patch5 and it now shows Error 90:  "fetching the forms from the Remedy Server.".

We are still working with Cisco trying to figure out what is wrong.  

Regards,

T

[Tuan Tran]

The engineers are looking into the scenario.  We are able to reproduce the issue.  Hopefully, there will be a fix for it soon.

[deepti.musunuru1]

Do you happen to have a timeline on when this issue will be fixed?

[Tuan Tran · Accepted solution]

Please check out Process Orchestrator Patch 6. It addresses the following issue.

"CSCve74881 - Fix the server errors when fetching forms and fields in Remedy Adapter"

[Tiberio Martinez]

Yes!

I applied the Patch 6 today and the integration started working straightaway.

We also received reports from the Remedy team about a memory leak created by the CPO client.  I'll keep an eye on it for now and will report back the results.

So far, the issue seems resolved.

Thanks for your help!

[Tuan Tran]

That is great to hear.  :)

BTW, if you receive any additional information from the Remedy team about memory leak, please forward the information.

Thanks,

-Tuan

[Tiberio Martinez · Accepted solution]

CPO has been running for more than a week and the Remedy team has not complained so I think it is safe to assume that the memory leak issue was also solved by Patch 6.

Thanks for your help!

T