on ‎2020 Feb 26 9:28 AM
Hello
Yesterday PL16 with Note 2890520 had been released. Does anybody know, where to get more information about the fixes itself? For example "Fix: Pepper Plugin output items." does not tell me enough...
For the testing procedures, before releasing a new PL to productive environment, more information about the fixes itself would be appreciated.
Best Regards
Klaus
Request clarification before answering.
Hello kfrick,
Thanks for this question. I agree this particular description of a fix does not tell a lot unless you have been directly involved in this. In this case, we fixed an issue that could occasionally leave the user stuck in the eft day-end closing without any way to proceed or return. Then a blank pop-up screen from the pepper plug-in was sitting idle above the CCO day-end closing screen.
But I take this question to improve our note going forward so that errors + fixes become clearer. Realistically sometimes it will be impossible to describe complex issue in just one line.
Best regards,
Gunther
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Gunther
Thanks for your answer. I was not involved in that case, but I had exactly your described problem starting on one CCO and a around a week later on a second one. After upgrading to PL16 this had been solved.
I and probably many of us, would appreaciate a better description of the errors + fixes. It would also makes testing much easier before going productive.
Best Regards
Klaus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello kfrick,
Thanks for your feedback. Which is much appreciated because it shows that the release notes seemingly provide a value to you and others. I started an internal discussion and we will make an effort to improve the error / symptom description in our release note.
Best regards,
Gunther
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.