How to Create a Violation Report on Relationships or Constraints
To create a violation report:
The Operations on Application Database dialog appears.
The appropriate window appears.
Note that if you use an existing file name, the file will be overwritten without any further warning.
A record is added to the Reports table, enabling you to view the report later.
You can also create constraint violation reports via a USoft action that can for example be called from within batch jobs, the SQL command dialog , or the SqlScript() action:
report-constraint-violations(<path/filename>, [configuration] )
This action creates a constraint violation report and writes it to the specified file, based on the (optional) configuration.
report-relationship-violations( <path/filename>, [configuration] )
This action creates a relationship violation report and writes it to the specified file, based on the (optional) configuration.
The filename parameter is mandatory. If no configuration is supplied, or the configuration cannot be read from the BenchMark tables properly, all constraints/relationships that violate repository rules will be reported.
The filename defined in the configuration is only used by USoft Benchmark. These actions always require a separate filename.