"Continue" or "Abort" solution publish should validate that someone else already performed a choice.

Service Center
On our radar

Hi everyone,

We have been facing an issue regarding the solution publish

Nowadays, the solution will stop at step 11 waiting for a user to press "Continue" or "Abort" the solution publish.

Now in small factories, its easy to control the users that will perform this action.

In my case, sometimes we have more than one person doing the continue.

What we found is that the "Continue" option doesn't validate that the solution is already "on going", ending up on a large locks, on espaces,  from one solution to the other, and in consequence a timeout will appear ending the solution publish.

Created on 24 Apr 2018
Comments (4)

Hi Gonçalo,

Thanks for submitting your idea.

Just to clarify, is this a concurrency issue right? You have more than one user trying to hit the "continue" option almost at the same time in the Service Center. Am I correct?

Changed the category to Service Center

Yes that is the problem João :) 

Thanks for pointing it out.

Changed the status to
On our radar

Hi Gonçalo,

Thank you so much for your idea. I’m marking this as “on our radar” since we think this is a good idea.

This isn’t currently on our roadmap but we’ll keep an eye here if this idea continues to grow and get comments from all of you.