Frequently Asked Questions

What versions of Gen are supported? VerifIEr works with all current releases of Gen from 6.* upwards.
Can VerifIEr adopt our site standards? Yes, VerifIEr has been designed to be customisable so that it checks compliance to your standards. Customisation is performed at a number of levels:
  • Many of the standard IET supplied checks are parameterised enabling easy customisation via parameter values stored in the database
  • IET provides an implementation service to analyse your requirements and then adapt existing check types or develop new ones.
  • VerifIEr also contains an optional development / customisation module that will enable you to develop your own customised check types
How are customised checks developed? These are developed using a Gen model. A customisation model is supplied with VerifIEr which contains the common services and other objects needed to develop and implement custom checks using Gen action blocks.
Can I check objects prior to upload to the encyclopaedia? Yes, VerifIEr can operate as a Gen toolset or Studio Developer plug-in and therefore check objects in the toolset prior to upload. In addition, it can be configured to automatically verify objects on upload when using the GuardIEn Upload Assistant.
Can it check an entire model? The scope of a VerifIEr check execution can be one or more models, selected objects and objects scoped into a GuardIEn Change Request, Release Pack or System Update.
Can checks be run in batch? Yes, checks can be submitted for batch execution.
Can the use of VerifIEr be restricted to certain individuals? When a check type is defined, you can specify the project authority needed to execute the check for a given object type. For example, you might allow the check to be run on a specific object, but only administrators can run a model-wide check. You can also specify that certain check types have to be executed in batch.
If we have certain objects that are not compliant, will they be flagged in error each time we run a check? If it is acceptable that a certain object is not compliant to one or more check types, the objects can be excluded from the check type. It is also possible to specify that a check type only processes objects specifically included for this check type.
If one or more objects fail a model-wide check, do I have to rerun the whole check once the model has been corrected? VerifIEr provides a check restart facility that will only check objects that have failed a check, thus avoiding the need to recheck objects that have passed the check.
Can VerifIEr check non-Gen objects? Yes, VerifIEr checks can validate data in a database (i.e. audit reports from the GuardIEn database) and any other data that it can access due to the extensive customisation capabilities.
Are the VerifIEr checks the same as the Gen consistency checks? In concept they are similar since the consistency checks are checking the Gen objects against rules. There is not much overlap between the consistency check rules and the standard VerifIEr checks, but VerifIEr can check almost anything that you want, and so if you wanted VerifIEr to perform the same checks as the consistency checker, then this could be done.
Is VerifIEr integrated with GuardIEn? Yes, VerifIEr is closely integrated into GuardIEn, though it can operate as a standalone application for sites that do not have GuardIEn. The benefits of integration with GuardIEn are that the execution or standard checks can become part of the standard development life-cycle. For example, checks can be performed when changes are uploaded from the Gen toolset, on the contents of a GuardIEn Change Request, Release Pack or System Update.