CASE PM-166623-19-202704:

Previously, in the Management Console, the category tree loaded the entire catalog each time the module was entered, and save and replicate configuration operations were applied on a record-by-record basis. In organizations with large catalogs, this behavior caused high response times during navigation, and when editing or saving a category, the operation exceeded the maximum allowed execution time and ended with the message “An unknown error occurred, please contact your system administrator.”

The category tree is optimized so that it loads its content on demand: when entering, only the nodes of the first level are shown and each branch displays its elements to expand it. Levels with a large number of elements are presented in sections of 500 records, with the option More at the end of the level to load the next group. This behavior also applies to the category tree of a service and the category selector of a rule’s actions, as well as to the category selectors of templates, cases, and case creators.

Write operations on the catalog are optimized, and now run in bulk instead of on a record-by-record basis. This applies to saving with the option to apply to child categories, renaming, model, financial model, and template approval, replicating additional fields, times, and visibility over a subtree, and associating and disassociating category subtrees to a service.

On the Categories of the agreements in a service, the tree is presented by levels and the associated agreement is displayed as a label on each node. The assignment is made by selecting the category and choosing the agreement in a single selector, which updates only the affected node. In the Categories The option to expand all nodes is preserved, which shows the first section of each level and makes the rest available using the More.

⚐ Note: Category trees are collapsed by default; their levels load as they expand.