Create Knowledge in a new thread

Idea ID 2749951

Create Knowledge in a new thread

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.

 

 

 

 

 

3 Comments
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

@sfendri 

In Display Application Option Definition, there is a 'Spread Thread?' field in the RAD setting. It indicates whether the RAD application starts in its own thread. If you defined, threading allows you to open several active windows at once. With current investigation, there is no such function in ruleset settings.

 

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Waiting for Votes
 
Super Contributor.. Super Contributor..
Super Contributor..

Hi Yana Ding,

 

Yes, I confirm what you say. 

Moreover, technically, there are many things to take into consideration if you open the "Create Knowledge" in a new thread:

- First, you need to do it in all situations, i.e.:

-- whether the user clicks the "Contribute Knowledge" button in the navigation bar

--  or if he clicks the "New" button in top of the "Knowledge Queue" form.

- Second, you need to investigate the whole Create Knowledge implementation and fix all the situations where variables from the parent thread are used. For example, the $cachedAuthoringSource variable.

 

--> This is why this is something to be done by Micro Focus, and not by integrators like me.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.