A customer form becomes a business application when it does more than store records: it enforces business rules, models related data, controls access, and records enough activity for operators to investigate problems. In Uniface 10, build those concerns into the application design rather than treating them as cosmetic additions to a CRUD screen.
1. Put business rules where data is checked
A field’s appearance and its validity are different concerns. Rocket Software’s Uniface 10 Fields documentation describes storage, field syntax, and display properties separately. At runtime, Uniface checks data against the field’s data type and any defined field syntax. Field triggers can handle event processing.
As an Amazon Associate I earn from qualifying purchases.
Use field-level rules for constraints that belong to a single value: a permitted format, an allowed range, or a list of valid values. Uniface documentation describes ValRep lists and ranges as ways to define permitted values. Use event handling or other application logic for rules that depend on multiple fields or a business process; the field guide does not specify a customer-specific rule set for this form.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsFor example, a customer form might need a valid value for a status field as well as a rule governing when a status change is allowed. The first is a field constraint; the second is a process rule. Keeping that distinction clear makes it less likely that a visually restricted control will be mistaken for complete enforcement.
#1 Best Overall
2. Model customers and related records as relationships
A customer rarely exists in isolation. Orders, contacts, or addresses may be associated with a customer, and those associations should be represented in the data model rather than left to assumptions in the form. Rocket’s Uniface Concepts guide, version 9.7, describes relationship objects as defining associations between entities, including key and delete-constraint behavior.
One-to-many relationships
For a one-to-many association, one customer can be related to multiple records in another entity. Model the association with the relevant keys and decide what deletion constraints should apply. The constraint matters because deleting a customer must not leave related records in an unintended state.
Rank #2
Many-to-many relationships
For a many-to-many association, the V9.7 Concepts guide specifies an intermediate entity rather than a direct many-to-many relationship. This is core modeling guidance from an older guide, not a claim about a new Uniface 10.4 release. Confirm implementation details against the documentation for the Uniface release and patch you deploy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Treat access control and validation as server-side responsibilities
Browser-side checks can improve feedback, but they are not a security boundary. Rocket’s Rocket Uniface Web Security Guidelines V10.4 says, “The application should not rely on validation done by the browser.” Validate received input in the application, including requests that might bypass the form’s normal controls.
Rank #3
Authorization should control both what a user can view and what they can do. The V10.4 security guide addresses confidential-data access, data manipulation, unauthorized commands, and privilege escalation. Identify sensitive customer data and relevant roles, check permissions early, and centralize authorization where practical so that screens and actions do not each implement inconsistent access rules.
4. Make significant activity investigable
A maintenance form does not automatically provide a complete audit trail. Logging must be designed and configured. The V10.4 security guide recommends application and server logging and identifies significant events such as logon attempts and database access as useful records.
Choose events that help operators investigate security or operational issues, then configure the relevant application and server logs. Treat these logs as operational evidence: unless you implement and verify an audit mechanism, do not assume they provide a complete, tamper-proof history of every customer change.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →How the four concerns fit together
- Business rules: Define valid field values and formats, then handle rules that depend on other data or process state.
- Relationships: Connect the customer to related entities with keys and deliberate deletion behavior.
- Access and protection: Validate received input and authorize both data visibility and actions.
- Traceability: Configure logging for significant events so activity can be investigated.
The documentation context spans releases: Rocket’s catalog lists Uniface Library 10.4, while the relationship details above come from the V9.7 Concepts PDF; the web-security guidance is V10.4 © 2024. Check the documentation for the exact deployed patch before relying on release-specific syntax or behavior. The four-part structure here is a practical way to organize these design concerns, not a quoted or definitive list attributed to a source author.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
