# How-To

The following are some how-to examples of typical behavior utilizing some of the standard user exits.

The examples are written for cases of modifying new CM transaction pages, where the function definitions are put into extended JavaScipt files (.xjs) that are meant to contain JavaScript user exits directly for a page.

If, on the other hand, an implementer wishes to modify the behavior of a shipped product page, each of the functions below have a corresponding `ext` function defined in a `/cm/extXXX.jsp` file corresponding to the desired page that will fire after any product function call (see the above example of hiding the Sequence column in the algorithm maintenance page).

- How Do I Control the Initial Focus Within Tab Pages/Grids/Search Pages?
- How Do I Mark Fields that Won't Make the Model Dirty?
- How Do I Control the Triggering of Defaults After a Search?
- How Do I Avoid Automatically Setting Fields to Uppercase?
- How Can I Force the Save Button to be Enabled?
- How Can I Override the Processing After a Change/Add?
- How Do I Prevent the System from Setting Focus to a Widget After an Error?
- How Do I Prevent Attributes from Being Copied into New List Elements?
- How Do I Customize New List Elements?
- How Can I Get My Sequence Numbers to Default Properly on My List Grid?
- How Do I Override the Tab Page Shown After an Error in a List (Grid/Scroll)?
- How Do I Disregard Unwanted Criteria from a Search Triggered by a Search Button?
- How Do I Disregard Unwanted Search Result Columns?
- How Do I Format a Value Based on a Given Format?

Parent topic: UI Javascript User Exits