{"id":2212,"date":"2021-09-30T11:53:12","date_gmt":"2021-09-30T09:53:12","guid":{"rendered":"https:\/\/www.canopsis.fr\/canopsis-v4-3-discover-the-new-dependency-trees-feature-%ef%bf%bc\/"},"modified":"2025-10-02T14:37:17","modified_gmt":"2025-10-02T12:37:17","slug":"canopsis-v4-3-discover-the-new-dependency-trees-feature","status":"publish","type":"post","link":"https:\/\/www.canopsis.fr\/en\/canopsis-v4-3-discover-the-new-dependency-trees-feature\/","title":{"rendered":"Dependency trees in Canopsis V4.3"},"content":{"rendered":"\n

Released at the very end of August, Canopsis 4.3 created a surprise by offering a new feature outside the Roadmap<\/a>: dependency trees! Ready to discover what it can do for your IS? Follow the guide \ud83d\ude09<\/p>\n\n

Before dependency trees…<\/strong><\/h2>\n\n

Before version 4.3, it was possible to select and then observe a group of entities<\/strong>. Canopsis did not allow for the weighting of the latter; it was therefore impossible to give particular importance to one of them within the repository<\/strong>.<\/p>\n\n

Since the upstream impacts of the entities were not represented, the observers were limited to a single floor<\/strong>… Too little to create true dependency trees!<\/p>\n\n

Similarly, the worst-case algorithm<\/strong> was always presented worst-case algorithm. To be clearer, it systematically reflected the least favorable state of all the entities<\/strong> in the repository.<\/p>\n\n

This failure to take into account the criticality of the entities had a direct impact on the criticality of the alarms and could result in a prioritization problem for the pilots!<\/strong><\/p>\n\n

How dependency trees work in Canopsis 4.3<\/strong><\/h2>\n\n

Thanks to the Dependency Trees feature, you can now define an impact level based on the predefined importance of each entity!<\/strong><\/p>\n\n

The importance of an entity<\/strong> can be:<\/p>\n\n