LEARN. PRACTICE. GROW.Concept and mechanism
Adding a field to a form changes presentation; creating a dictionary field changes schema. Removing the field from a view does not delete the column or its data. UI Policies help with declarative field behavior; Client Scripts support interface logic requiring code. A form restriction does not guarantee equivalent behavior in a list or integration. For data invariants, choose a suitable server mechanism and validate relevant channels. Before Business Rules can populate the current record before persistence; after is appropriate for related work that depends on the completed operation. Async does not provide previous like a synchronous rule. Avoid unnecessarily updating current again and creating recursion.
Guided application
For information available at load time, g_scratchpad can carry server-prepared data. For a selection changing during the session, asynchronous GlideAjax can request only the required result. In an exception form, the operator selects fund A and immediately fund B. If A’s response arrives last, the callback should confirm that it still matches the current selection before writing its result. Do not make browser blocking the first solution. In onChange, use isLoading when behavior should not run during loading and handle empty values. Use form APIs instead of fragile DOM dependencies. A record producer provides request-oriented input and creation in the intended table; inspect its destination, variables, and persisted result, not merely page appearance.
An old response for A must not overwrite fund B’s classification.
Common pitfalls
Client logic treated as universal integrity; DOM treated as API; async treated as guaranteed order.
Related topics: Needs, data, and design · Scope, modules, and dependencies · Security and access contracts
Separate experience, integrity, and execution timing.
Reference: Client-side scripting design and processing · CAD blueprint January 2026