The Configuration control is a debugging and configuration aid.  The I18N internationalization service used to internationalize controls is specified here.


Debugging On Sets the debug switch to true when checked.  The switch is used primarily for debugging purposes and will cause controls to log debug information in the console.


Show Log Useful when testing on Mobile devices such as the iPad where the browser log is no easy to retrieve real-time

Last Entry First Insert new entries at the top of the log window instead of at the end


Parameters List of parameters which can be accessed by the getParameter() method.  These are meant to be like global (page) variables, and can be used to store configuration parameters for other controls in a single place.


These are the configuration option settings...

This is the result...

The Configuration control gives insight into the details of the controls on the Coach. For example, it lets you know the debug log is on, the views that have been loaded, and what expressions are associated with what controls.

Now, let's say we put a Decimal control on the Coach, and bind it to a String variable...

You can see there is an issue with the Decimal control, which allows you to pin down where the issue is so you can investigate further.


For detailed information on the available methods for this control, access the JS Doc file.

Best Practices

It is best to use this control at the page level (i.e., not nested inside any coach views or layouts). It’s also a good idea to put this control at the top of the page when using the parameters, so that they can be accessed at load time by other controls in the page.


  • Author: Courtney Silva
  • Date Created: June 24, 2015
  • Date Modified: July 27, 2015
Was this article helpful?
0 out of 0 found this helpful