Lawson Process Designer Logout Issue

For those of you who are already using Lawson Process Designer, you should be aware of a bug that exists in some 10.0.1 and 10.0.2 versions. When going to “Tools -> Logout” after starting LPD logged in, the connection to the logged in server is not actually severed. You can see here that my LPD status says “OFFLINE”, but the connection to my Process Automation Server is still alive and well.

If you look at the console window that pops up when you load designer, you can see that LPD actually threw a NullPointerException when I “logged out.”

The real problem here is that if you return to “Tools-> Login” to login to another server. Because the initial connection was never severed, your new connection to an alternate server is not made. It will appear that you have logged into your alternate server, but you’re actually still connected to the server you first logged in to. I discovered this by taking steps that are fairly common:

1. Log into a production environment and download the latest version of a flow, to make sure I have the newest copy.

2. Log out of production.

3. Make an adjustment to the flow (change the contents of an email, etc).

4. Log in to a test or development environment.

5. Upload my updated flow to test in the test or development environment.

I made a minor change to a flow that I was testing with a client preparing to go live. Luckily “production” in this case was actually “pre-production”. You can imagine my surprise, though, when I received notification that “the changes are working in pre-production now, but I don’t see them working in test”. That is because when I uploaded the flow with designer showing that I was logged into test, I was actually still logged into pre-production. This bug has been corrected in IPD 10.0.3 and above, but I have been told that there will be no correction to earlier versions. To avoid this issue, one can simply close LPD completely instead of using “Tools -> Logout” and then start a new LPD instance to login to their alternate server.

Jonathan Ford, Senior Technology Consultant

Get the latest thought leadership from Avaap delivered to your inbox weekly!

* indicates required

Expert Insights

Trending resources

When the CIO Holds the Key to Business Transformation

When the CIO Holds the Key to Business Transformation

When the CIO Holds the Key to Business Transformation It’s not every day an organization…
Leveraging Change Management When Moving to the Cloud

Leveraging Change Management When Moving to the Cloud

Start with the end in mind: Optimize your future state by leveraging the current state…

For those of you who are already using Lawson Process Designer, you should be aware of a bug that exists in some 10.0.1 and 10.0.2 versions. When going to “Tools -> Logout” after starting LPD logged in, the connection to the logged in server is not actually severed. You can see here that my LPD status says “OFFLINE”, but the connection to my Process Automation Server is still alive and well.

If you look at the console window that pops up when you load designer, you can see that LPD actually threw a NullPointerException when I “logged out.”

The real problem here is that if you return to “Tools-> Login” to login to another server. Because the initial connection was never severed, your new connection to an alternate server is not made. It will appear that you have logged into your alternate server, but you’re actually still connected to the server you first logged in to. I discovered this by taking steps that are fairly common:

1. Log into a production environment and download the latest version of a flow, to make sure I have the newest copy.

2. Log out of production.

3. Make an adjustment to the flow (change the contents of an email, etc).

4. Log in to a test or development environment.

5. Upload my updated flow to test in the test or development environment.

I made a minor change to a flow that I was testing with a client preparing to go live. Luckily “production” in this case was actually “pre-production”. You can imagine my surprise, though, when I received notification that “the changes are working in pre-production now, but I don’t see them working in test”. That is because when I uploaded the flow with designer showing that I was logged into test, I was actually still logged into pre-production. This bug has been corrected in IPD 10.0.3 and above, but I have been told that there will be no correction to earlier versions. To avoid this issue, one can simply close LPD completely instead of using “Tools -> Logout” and then start a new LPD instance to login to their alternate server.

Jonathan Ford, Senior Technology Consultant