5.2.3 Bypass Base Release Functionality

This topic offers an overview of how to bypass Base Release Functionality.

There are auto-generated functions like FN_SKIP_<RELEAE_TYPE> which would determine whether or not a particular hook needs to be called.

The developer also has an option to bypass the base release hook if need be.

For example, if the validations are written in UTPKS_UTDFNDRL_KERNEL.FN_PRE_CHECK_MANDATORY are not required or not suitable for the Cluster release, the system provides an option to bypass the code written by the Kernel team.

Similarly, a Custom release can also bypass the code written by Kernel and Custom Releases. This can be achieved by calling procedures PR_SET_SKIP_<RELEASE_TYPE> and PR_SET_ACTIVATE_<RELEASETYPE>.

These procedures will be made available in the main package and the development teams of Customization teams can use these procedures to skip and reactivate the hooks of parent release.

The developer should refrain from adding validations or checks in the Pre Stage of any function, such as Fn_Pre_Check_Mandatory, and instead focus on implementing all validations in the Fn_Post_Default_and_Validate stage.

For Example: The flow for the Mandatory Stage for STDCIFD:

Figure 5-2 Flow of control explaining skip logic in packages

Description of "Figure 5-2 Flow of control explaining skip logic in packages"