You can gather information about edited forms before implementing them in your runtime environment through the following ways:
Check for errors with the expression statements within your form fields through the use of error logging.
Use the Form Editor to validate the syntax of individual expression statements. The Form Editor displays syntax error messages from the parser in a pop-up window. For information on using the Form Editor, see the online help that is associated with the Form Editor.
The Identity Manager error logging utility reports to standard output any problems with the syntax of form expressions. Once XPRESS tracing is turned on, you can limit log messages to XPRESS statements for a subset of the form with the <block> tag. To obtain more information about the processing of XPRESS statements, a configuration option in the waveset.properties file, xpress.trace, can be set to true. When this option is set to true, all evaluations of XPRESS statements will generate trace messages to the console. This can be used to debug statements that are evaluated inside a running application whose code cannot be changed to enable tracing through the XPRESS API.
You can turn on XPRESS tracing for all XPRESS fields through either the command line or the Identity Manager Administrator Interface. Turning on tracing this way affects all fields. To limit log messages to a subset of the form, use the <block> tag set to limit error tracing to only code within the <block></block> tags.
Open the config/waveset.properties file for editing.
Search on the line xpress.trace=false.
Change the false value to true.
Save the file.
Restart the application server.
Alternatively, you can use the Identity Manager Administrator Interface to turn on and off error logging.
Login into Identity Manager as Configurator.
Select Debug to open the Debug page.
From the Debug page, select Reload Properties.
To turn tracing off for XPRESS, set the xpress.trace value to false, and reload the waveset.properties file.