Description of problem: When working with multiple users on a same BPMS instance under different accounts it appears that the Problems section is shared - i.e. whenever I saved some erroneous process/rule , the other logged user (different user) can see the error in his Problem section - which does not seem like desired behavior. Version-Release number of selected component (if applicable): boms 6.0.3 How reproducible: always Steps to Reproduce: 1. Start the business central, and log with X and user Y (i.e. in different browsers) 2. Open Process designer with user X 3. Open process designer with user Y 4. Make sure that process has some errors and save it with user X 5. User Y will see the content in problem section - even if he is working in completely separate project / process Actual results: The Problem section is shared between different logged user. Expected results: The problem section is NOT shared between different logged user - it should be unique per logged user. Additional info:
6.1.0.GA is affected by this. Users should be aware that the section was renamed to Messages in 6.1.
I am not totally sure that this is really an unexpected behaviour. I see the business-central as a collaborative tool. If I am working in a project and I save a process in a inconsistent state I think reasonable that every logged user working in the same BPM Suite instance (and with visibility for that process) see the error. If I am working in a rule of a project, where a different user is working in a process in the same project - and I or the other user save something with errors, we need to inform all users about that or the build will not succeed. Is not that expected ?
I've re tested how it's working with last 6.3.x branch build, and I confirm that both users can see the error. i.e. 1) login with user_a in session1 2) login with user_b in session2 3) user_a opens/creates a drl file, breaks it by typing a non valid sentence, and saves the file. 4) user_a can see the error message 5) user_b can see the error message This is the semantic we have since the first wb version, and my understanding is that since both users can see the projects at the same time, and also work with them, both are interested on knowing if a given project is broken. If not, we can have weird scenarios where user_a breaks the project and user_b believes the project is ok, etc. In my opinion we should keep this semantic.