//addInfoMessage(), gs.log

//Push messages from the server up to the client form using gs.addInfoMessage() or gs.addErrorMessage().
//Write to table "syslog" with gs.info(), gs.warn(), or gs.error().
//Write to table "syslog" but with a custom Data Source using gs.log(), gs.logWarning, or gs.LogError(); here the custom data source is "Phoenix".

//Use the "Debug Now" custom UI Action to execute this script synchronously in your current user session..
//The "Execute Now" button will run this script asynchronously, in a different session, so you will not see form messages, for example.
gs.addErrorMessage("My Error Message From Server"); //Server-Side code that pushes a message back up to the client: Wide message at top of form in Red.
gs.addInfoMessage("My Info Message From Server"); //Server-Side code that pushes a message back up to the client: Wide message at top of form in Blue.

//SERVER SIDE DEBUGGING
gs.log("My log message"); //Log message to table: syslog.
gs.info("My info message"); //Equivalent to gs.log.
gs.error("My error message");
gs.warn("My warning message");

gs.log("My Phoenix informational message", "Phoenix"); //Log message to table "syslog", Source "Phoenix".

//Shown below form on client, if "System Diagnostics - Session Debug" is turned ON for the "log" object type.
gs.debug("My gs.debug message"); //Also shown in the separate Session Log window.