Markup Language Skeleton Customization › Model Customization › Integration with the CA 2E Model

Integration with the CA 2E Model

From r8.0 onwards, users apply customization directly to screen elements in the model itself, meaning that when a skeleton is generated for a screen that contains those elements, the element-specific customizations are automatically applied to the skeleton.

Element-level customization can be applied at the following levels:

• Field-level

  When a skeleton screen is generated having screen fields, the customization is selected. Screen element customization overrides field level customizations.

• Header/footer-level

  Element customization can be applied to a Define screen format (DFNSCRFMT) function based over the *Standard header/footer file. This customization will apply to every function and allows common customizations to be applied across multiple screens.

• Display-file-level

  When a skeleton screen is generated having display fields, the customizations are selected. Display-file-customization is implemented in place of the normal *BODY and *HEADER elements that are generated for all skeletons.

• Record-format-level

  When a skeleton screen is generated having record format levels, the customizations are selected. Record-format-customization is implemented in place of the first *TR element that is generated for all skeletons.

• Screen-element-level

  When a skeleton screen is generated having a screen-element level, the customizations are selected. Screen-element-customizations are implemented in place of the *INPUTFIELD, *OUTPUTFIELD, *DYNAMICFIELD or *OUTPUTTEXT elements that are generated for the screen element.

Note: Because it is not possible to associate element customization with a specific header/footer, element customization applied to fields on any header/footer will apply to every screen in the model, whether they use that header/footer or a different one.

Model-level customization data is held in two files within Web Option:

YELMCSTRFP

This file contains the actual customization data that is created by users. The data in this file can be used by different elements in different models. The data in this file can include variables, which are replaced at MLS generation time with skeleton-specific data.

YSCRELMRFP

This file contains links between the elements in each model and the customization data held in YELMCSTRFP.

The customization data held in YELMCSTRFP can be edited using the YWRKELMCST (Work with Element Customization Data) command.