> For the complete documentation index, see [llms.txt](https://cbdebugger.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cbdebugger.ortusbooks.com/readme/release-history/whats-new-with-4.0.0.md). # What's New With 4.0.0 2022-NOV-22 ### Added * ColdBox 7 support * New `TimerDelegate` that can be used to add timer functions to any model * Timer service rewritten to support nesting and included metadata * Ability to open views and layouts from the execution timers in any Code Editor * New `WireBoxCollector` which is only used if enabled. This greatly accelerates the performance of the request collector since before they where in the same collector. * Ability to open CFCs that are profiled by the WireBox Collector in any Code Editor. * Ability to open the Handler events that are profiled by the Request Collector in any Code Editor. * New life-cycle events: `onDebuggerUnload`, `onDebuggerLoad` * Ability for the custom `timeIt()` functions to accept metdata to store in the execution timer * New `Slowest` Queries panel for cborm, acf, and qb/quick * New visualizer total db time as well as request time including percentage of the request time * Ability to export a profiler in json * Ability to sort the visualizer's profilers ### Fixed * Timer service reconstructing the timer hashes and profilers twice. * `timeIt()` helper was not passing the closure correctly * If doing a fwreinit on the visualizer, the current profiler was still being show even thought it was empty. Add an empty check to avoid the big bang! * Empty response codes for Adobe, due to their incredibly weird Response object nesting. * Migration to java random id's for speed ### Changed * Tracers are now streamlined and stored alongside the request profilers * Small UI fixes on request profiler HTTP methods * WireBox collecting is now done by the WireBox collector not the Request Collector. * Adobe 2016 Dropped --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cbdebugger.ortusbooks.com/readme/release-history/whats-new-with-4.0.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.