While Mobileforce products such as CPQ and FSM are mostly customized by configuring the product parameters, and therefore do not required coding. However, sometimes customers (typically users with admin privileges) may have a desire to learn how the products are working in a live environment. Debugging and analytics are two use cases where customers find it valuable to learn how the product parameters interact with the product environment.
To assist with these cases, the Mobileforce apps provide a method to debug their behavior.
This level of debugging and analytics is intended for use by users with admin privileges, and not available to most end users, such as Sellers or Technicians.
Using the Debug Console
In the Mobileforce CPQ application, one can access the Debug Console from within an individual quote. From a quote, scroll to the bottom of the page to view a bug icon in the bottom right of the screen, as shown in the screenshot below
Click the icon to opens up the Form Expression Debug Console popup window with two tabs: "Form Expressions" and "Terminal"
Each expression listed in the table is currently being used with the selected quote. You can hover over any value to view the complete value. You can use this for the Expr and Env columns to view either the full expression for the field or the the environment (context) in which that form expression is being evaluated.
The Terminal tab. provides an interactive command-line (shell like) terminal, where users can enter specific form expressions to evaluate what their value would be. These expressions can then be used throughout the quoting process.
Additionally the Terminal tab displays a history of the expressions that were entered into the terminal console, and the value of the expressions that was returned.
Note to Admins
For debugging client-side form-expressions, it is useful to set ADL property ‘form-debug’ to ‘1’.
This enables a bug icon on the bottom right of your screen. Clicking on this icon will show the status and results for form-expressions. It also provides a form-expression console, although form expressions in that console are executed at the top-level context, not the per-line-item context. This means that it won’t be able to look up values of per-line-item variables like cpq_code.