Project:
| View Revisions: Issue #17068 | [ Back to Issue ] | ||
| Summary | 0017068: Validation pattern | ||
| Revision | 2011-05-09 12:56 by alostale | ||
| Description | Complex configurations cannot be validated on the fly because while configuring the status is not valid. For example: -AD. In 2.50 this is solved when compiling by WAD Validation. In 3.0 this doesn't make sense as it shouldn't be needed to compile after AD modifications. -Account configuration |
||
| Revision | 2011-05-09 12:55 by alostale | ||
| Description | Complex configurations cannot be validated on the fly because while configuring the status is not valid. There should be a generic validation pattern visible somewhere in the application (top navigation bar?). Modules could define validations. A validation is defined by: -Entities to validate. When any of these entities is modified, the validation status is "to be validated". -Validation process. Is the process that does the verifications and changes the status to "Successfully Validated" or "Validated with errors" |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |