You must restart the engine after you apply a breakpoint.

In TIBCO Business Studio™ for BusinessWorks™, breakpoints are dynamic and can be managed during an active debug session. A developer can add, remove, or disable breakpoints while the application engine is running in debug mode. The engine does not need to be restarted for these changes to take effect. This functionality allows for an efficient and interactive debugging process, enabling developers to pause execution at newly identified points of interest without interrupting the entire session.

B. True: This is incorrect. Requiring an engine restart to apply a breakpoint would be highly inefficient and contradicts the standard debugging capabilities provided by TIBCO Business Studio.

1. TIBCO BusinessWorks™ Application Development Guide (Version 6.8, March 2022): In the chapter "Testing and Debugging an Application," the section "Setting Breakpoints" states, "You can set breakpoints on activities before you start the debugger or during the debug session." The ability to set breakpoints "during the debug session" explicitly confirms that a restart is not required. (Refer to the "Debugging the Application" > "Setting Breakpoints" section).

2. TIBCO BusinessWorks™ Application Development Guide (Version 6.6, May 2020): The chapter on "Testing and Debugging an Application" similarly describes the process. In the "Debugging Perspective" section, it details how to interact with a running debug session, including adding breakpoints on the fly without mentioning any requirement for an engine restart. This dynamic capability is a core feature of the debugger.