Hi everyone, Does anyone know why clicking on a related action might

Krassi,

Are there any relevant errors in your app-server logs, that correspond to the time from when you click on the actions?

Hi Alok,

That's the strange thing, there are absolutely no errors in both server.log and application-server.log. Are there any specific tempo error logs I can double-check?

Krassi,

Is this happening for one particular action or all related actions?

Did something change in the environment recently that would have triggered this behavior?

It happened for me as well for couple of times. However, simply logging out and logging in back solved my issue.

Hi Alok, based on my Firebug logs, it looks like a firewall issue to me. We have a site-to-site VPN onto the website, so we use the internal IP of the server, instead of the public one. This is the same issue that happens on paging grids on the same server. Is there anything we can do to remove this behaviour and make this work?

Krassi,

I believe you need to set the following property correctly in custom.properties:
conf.suite.SERVER_AND_PORT=

It needs to be setup as either the web-server Alias or <App_Server>:<PORT>.

Also, ensure that you use the same URL to access the site, so that you dont run into this issue.

Hi Alok,

This is not an option due to the NHS having a NAT firewall (i.e. one-way traffic). Thus, this makes it very difficult to test anything on tempo. Can we leave the option empty for SERVER_AND_PORT? Would that default to URLs using relative paths (i.e. localhost/tempo etc?)

Hi Krassi,

Unfortunately, the conf.suite.SERVER_AND_PORT property is mandatory and failure to configure the property as documented will affect several components withing the Application.

This is a Required Configuration per the following link:
forum.appian.com/.../Post-Install_Configurations.html

Hi Alok,

What this means is that Appian Tempo will no longer work behind any NAT firewall, which will be a significant issue for us and I suspect a lot of your clients. Can you log an enhancement ticket for Tempo to use relative paths or is this something you want as part of the platform going forward?

I had also faced simillar issue, The reason was i was accessing the application using http instead of https.