Progress will discontinue Telerik Platform on May 10th, 2018. Learn more

Debug Business Logic

Filter by IDE
Select the Progress AppBuilder client you are currently using for development.

IDE

With Business Logic, you can execute JavaScript code before and after performing CRUD operations on content types in your app. In AppBuilder, you can debug your business logic (cloud code) - you can set breakpoints in the code and log events in the console.

Prerequisites

  • Verify that your preferred AppBuilder client is running and you are logged in.
  • Verify that you have opened the code for your app in AppBuilder.
  • Verify that you have enabled Business Logic for your app.
  • Verify that you have modified the default business logic (cloud code) templates.
  • Verify that you have set an X-Everlive-Debug custom header for the request that you want to debug.

Procedure

In-Browser

  1. In the left-hand menu of your app, click Business Logic.
  2. In the right-hand explorer for your content types, select the content type for which you want to debug the business logic.
  3. Select DebugStart debugging.
  4. Debug your business logic (cloud code).
    For more information about Data, Users, Notifications and Business Logic business logic (cloud code) debugging, see Introduction to Business Logic Debugging.
    Operation Action Description
    Inspect the diagnostic log In the debugger, click Console In the Console pane, you can inspect diagnostic log information such as errors and warnings, console.log() messages and so on.
    Inspect the source files of your application, insert breakpoints and debug your code In the debugger, click Sources and enable debugging, if not enabled In the Sources pane, you can open source files to add breakpoints and modify your code to debug it without affecting the corresponding file in your app.

Windows

  1. Open the Data Navigator.
  2. Expand your account, locate your app and right-click it.
  3. Select Debug Business LogicStart Debugging.
    AppBuilder opens the built-in debug tools.
  4. If prompted, select if you want to enable debugging for the current session or for all future sessions and click Enable Debugging.
  5. Debug your business logic (cloud code).
    For more information about Data, Users, Notifications and Business Logic business logic (cloud code) debugging, see Introduction to Business Logic Debugging.
    Operation Action Description
    Inspect the diagnostic log In the debugger, click Console In the Console pane, you can inspect diagnostic log information such as errors and warnings, console.log() messages and so on.
    Inspect the source files of your application, insert breakpoints and debug your code In the debugger, click Sources and enable debugging, if not enabled In the Sources pane, you can open source files to add breakpoints and modify your code to debug it without affecting the corresponding file in your app.
  6. If you have closed the debug tools and your debug session is still running, reopen the cloud debugger.
    1. In the Data Navigator, expand the Data, Users, Notifications and Business Logic tree, locate your app and right-click it.
    2. Select Debug Business LogicShow Debug Window.
      AppBuilder opens the built-in debug tools.
    3. Repeat Step 5.
  7. (Optional) Restart your debugging session.
    1. In the Data Navigator, expand the Data, Users, Notifications and Business Logic tree, locate your app and right-click it.
    2. Select Debug Business LogicRestart Debugging.
      AppBuilder opens the built-in debug tools.
    3. Repeat Step 5.
  8. If you have finished debugging your code, stop the debugging session.
    1. In the Data Navigator, expand the Data, Users, Notifications and Business Logic tree, locate your app and right-click it.
    2. Select Debug Business LogicStop Debugging.

Visual Studio

  1. Open the Data Navigator.
  2. Expand your account, locate your app and right-click it.
  3. Select Debug Business LogicStart Debugging.
    AppBuilder opens the built-in debug tools.
  4. If prompted, select if you want to enable debugging for the current session or for all future sessions and click Enable Debugging.
  5. Debug your business logic (cloud code).
    For more information about Data, Users, Notifications and Business Logic business logic (cloud code) debugging, see Introduction to Business Logic Debugging.
    Operation Action Description
    Inspect the diagnostic log In the debugger, click Console In the Console pane, you can inspect diagnostic log information such as errors and warnings, console.log() messages and so on.
    Inspect the source files of your application, insert breakpoints and debug your code In the debugger, click Sources and enable debugging, if not enabled In the Sources pane, you can open source files to add breakpoints and modify your code to debug it without affecting the corresponding file in your app.
  6. If you have closed the debug tools and your debug session is still running, reopen the cloud debugger.
    1. In the Data Navigator, expand the Data, Users, Notifications and Business Logic tree, locate your app and right-click it.
    2. Select Debug Business LogicShow Debug Window.
      AppBuilder opens the built-in debug tools.
    3. Repeat Step 5.
  7. (Optional) Restart your debugging session.
    1. In the Data Navigator, expand the Data, Users, Notifications and Business Logic tree, locate your app and right-click it.
    2. Select Debug Business LogicRestart Debugging.
      AppBuilder opens the built-in debug tools.
    3. Repeat Step 5.
  8. If you have finished debugging your code, stop the debugging session.
    1. In the Data Navigator, expand the Data, Users, Notifications and Business Logic tree, locate your app and right-click it.
    2. Select Debug Business LogicStop Debugging.

CLI

  1. In the left-hand menu of your app, click Business Logic.
  2. In the right-hand explorer for your content types, select the content type for which you want to debug the business logic.
  3. Select DebugStart debugging.
  4. Debug your business logic (cloud code).
    For more information about Data, Users, Notifications and Business Logic business logic (cloud code) debugging, see Introduction to Business Logic Debugging.
    Operation Action Description
    Inspect the diagnostic log In the debugger, click Console In the Console pane, you can inspect diagnostic log information such as errors and warnings, console.log() messages and so on.
    Inspect the source files of your application, insert breakpoints and debug your code In the debugger, click Sources and enable debugging, if not enabled In the Sources pane, you can open source files to add breakpoints and modify your code to debug it without affecting the corresponding file in your app.

Next Steps

Edit your business logic (cloud code) or view the business logic (cloud code) log.

See Also

Contact us: +1-888-365-2779
sales@telerik.com
Copyright © 2016-2017, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.