5 Functionality Demonstration- Child Refresh

This topic provides an overview of Child Refresh Functionality.

In the unresolvable-reference.html#GUID-BA41A2CA-2C82-46C1-BDDB-21AED5818DED process, STDCIFDC is refreshed with the latest STDCIFD. The figure below shows the preview of STDCIFD and STDCIFDC main screens before the refresh.

Figure 5-1 STDCIFD- Before Refresh

Description of "Figure 5-1 STDCIFD- Before Refresh"

Figure 5-2 STDCIFDC- Before Refresh

Description of "Figure 5-2 STDCIFDC- Before Refresh"

From the screen preview, it can be noted that in the child screen many changes have been done which had resulted in a very different layout. Many fieldsets which were part of the parent screen have been made hidden and new fieldsets containing new fields have been introduced in the child screen.

Now we load STDCIFD in Workbench in the current release and made some modifications to it as required. A new field COUNTRY AND NATION have been introduced. A preview of STDCIFD after the modifications is shown below. Note the newly added field highlighted.

Figure 5-3 STDCIFD- Post Refresh

Description of "Figure 5-3 STDCIFD- Post Refresh"

Child Refresh of STDCIFDC is done as explained in the unresolvable-reference.html#GUID-BA41A2CA-2C82-46C1-BDDB-21AED5818DED section. The system units(main packages, language xml.sys js ,xsd’s, etc) are regenerated by loading the refreshed RADXML and deployed. All the units need to be regenerated. Preview of STDCIFDC main screen after the refresh is shown below:

Figure 5-4 STDCIFDC- Post Refresh

Description of "Figure 5-4 STDCIFDC- Post Refresh"

Here the user can find that the field added in the parent screen has come in the child screen as well. Meanwhile, other differences we have noticed between the initial parent and child screens have not come up as they were overridden in the child function Id.

Hence we find that the changes done in the parent have come up in the child while retaining the changes done in the child. Note that only screen layout changes have been explained in this demonstration for ease of understandability; this is applicable for all nodes (For Example Call Form, Launch Form, LOVs, etc.).