Idea ID 2749951
Currently, the creation of a new Knowledge document (whether this is launched via the Knowledge Queue's "New" button or from the incident/problem's "Create Knowledge" feature), happens in the same thread.
I suggest that, consistently with the other Service Manager modules, the creation of a new Knowledge happens in a new thread:
- first, because the current behavior is not practical for users. For example, if a user creates a knowledge from an incident, he can no longer go back and forth between the two threads to do copy-pastes.
- second, the current implementation puts too much load on the same thread, which causes thread memory consumption alerts to be raised, and potentially memory issues.
- third, from a design perspective, reusing the same thread for a different object is not clean at all. This causes risks of reusing or mixing variables from different contexts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.