Skip to main content

I have a Custom Broker smart object method, Goto, which takes a process ID and activity name as an input parameter.

When executed from the smart object tester on the host server (hostserver1) it works.

In the context of a workflow all events before this smart object event execute - however it seems to 'hang' on the event that is the call for this method.

The environment has a DNS entry for, https://website1 - which resolves to hostserver1.

Log file entries show errors (not entirely in time with when the method is called)  where URLs are formatted as https://hostserver1 instead of https://website1 - mostly to do with 404, 400 etc.

This leads me to think that when smartobject methods of this type are executed a K2 configuration item is involved to help determine URLs, paths etc.

The environment was origianlly set up using hostname1, then the DNS entry was created and the environment was setup again.

If anyone can shed some light on how or whether configuration items play a part in custom broker smart object it would be appreciated.

 

I am expecting something lik, 'yeah go check config item x', or 'check the compiled code for hard references to hostserver1'.

 

Thanks in advance.

 

Justin

Hello,

 

You may want to check the String Table for that workflow in Workspace as shown in the image at the bottom of this post.  The only thing I can think of is that maybe the old hostname is still listed as the default so it is using that in the context of the workflow.  Please let me know what you find.16662iF33828149F0B95DF.png

Hi JimmyBourqa,

 

Thanks for the response.

 

I have checked the page and the server name appears in multiple items:

 

- category server: Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=hostservername;Port=5555...

- Service ObjectTester: (as above)

- SmartFormsServer: (as above)

- SmartObject Server: (as above)

- Workflow Managemnent Server: (as above)

- Workflow Server: (as above)

 

All the other ones have 'https://correctURL.

 

Should this not be the case?

This issue has been resolved.

Essentially:

1. The custom broker code was updated to terminate connections correctly

2. an IPC evernt was added to the workflow to be cancelled - the event called a 2nd workflow - the 2nd workflow executed the Goto method to cancel the first one.

 

I hope this points people in the right direction.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings