 |
| Fibonacci.Validate |
| For End User Clients |
What the client wants is:
an application implemented to suit their requirements
with pages that guide, assist and check user entries
the flexibility to define the business rules themselves
no need to rely on the vendor or consultant to re-configure
Validate makes this possible with little or no change to the application.
Not all business applications have the degree of configuration that clients want. This is especially true in the user interface: where users meet the system.
Most complex businesses want to be able to define how they do business without re-programming or re-configuring their systems. The cost and/or lead times mean that business is less agile as a result.
The alternative is to train and re-train staff to be aware of business processes and apply them when using the corporate systems.
Fibonacci.Validate is a powerful alternative by allowing non-technical (business) users to define business rules for the user interface, completely externally from the applications. So the business (not IT or the vendor) can define which fields must be entered, what patterns must be used for account codes or phone numbers, what the minimum or maximum permitted values are, or even how different entries on the page relate to one another and interact with each other.
So if the business decides that a certain combination of status and action are no longer valid, the business can apply the rule and prevent that combination of options from being selected. Or if the business decides that when the user selects one of a number of customer types together with one of a number of product types, the colour must be selected, they can set the rule.
|
|
|
 |
| |
| Validation Types |
- Mandatory
- Min/Max Length
- Min/Max Value
- Format
- Patterns
- Lists
- Compare
- Invalid Characters
|
| Other Features |
- Multi-lingual
- Corporate rules
- Consistent messages
- All errors in one message
- Optional database driven rules
- Self-documenting
|
| Simple Example of Use |
|
|
|
