Online Manual

Version Workbench - Freezepoints

  • Published in Version Workbench - Online Manual

Freezepoints are core entities in the Version Workbench application. A Freezepoint entity contains version setup data stored in a table. A Freezepoint can contain Data Selection, Data Sequencing or Processing Option data for one or more environments or pathcodes at a particular moment in time.

A Freezepoint can be generated across pathcodes and environments, independent of the current login environment.

The scope of a Freezepoint can either be specified manually by using formexit Generate from one of the Explorer screens, bound to version content of an OMW project by using rowexit Freezepoint from the OMW Project tab or bound to the version content of a Taskview by using rowexit Freezepoint from the Taskviews tab.

Skip to the following chapters:

1.1 Generating Freezepoints  -  1.2 Exploring Freezepoints  -  1.3 Comparing Freezepoints

1.1 Generating Freezepoints

A Freezepoint can be characterized on the basis of the source of its content. There are four possible sources for a Freezepoint being described by the way they are generated.

1.1.1 Manual Scoping

Formexit Generate on the Option Explorer and Selection Explorer screens will only be available for Freezepoints that are not bound to a Project-, Taskview- or Import scope. Generating a Freezepoint by using formexit Generate from one of the Explorer screens will open the Freezepoint Generation Scoping screen:

Steltix Version Workbench - Freezepoint Generation Scoping

Here you may specify the environment or pathcode to generate the Freezepoint from, which type of versions you wish to include in the scope as well as build include or exclude listings for version or object names that are wildcard enabled.

1.1.2 Project Scope

Using rowexit Freezepoint from the OMW Projects tab of the Version Workbench main screen will present two sequential dialogs to specify the source environment for the Processing Options and the source pathcode for the Data Selection and Data Sequencing. After these dialogs the following popup screen reports the number of versions it is about to generate Freezepoints for if you confirm to proceed with the generation by clicking the specified link:

After generation is finished this same popup screen will look like this:

The generated Freezepoint name is available in the clipboard for use when opening the Freezepoint of choice (Processing Options or Data Selection) in one of the Explorer screens.

1.1.3 Taskview Scope

Using rowexit Freezepoint from the Taskviews tab of the Version Workbench main screen will not present dialogs for source environment and pathcode selection since the source environment in the Taskviews tab screen is used for that purpose. The following popup screen reports the number of versions it will generate Freezepoints for if you confirm to proceed with the generation by clicking the specified link:

After generation is finished this same popup screen will look like this:

The generated Freezepoint name is available in the clipboard for use when opening the Freezepoint of choice (Processing Options or Data Selection) in one of the Explorer screens.

1.1.4 Import Freezepoint

Using formexit Import from one of the Explorer screens will present the following popup screen:

In this screen you can browse the file system and select an import file containing exported Freezepoint data you wish to import into the JDE system where you are currently running Version Workbench. Opening the selected file will present the Confirm Freezepoint Import screen that validates the specified import file format and offers the option to modify the Freezepoint description before confirming to proceed with the import by using the OK button:

1.2 Exploring Freezepoints

Once a Freezepoint is generated you can explore the setup data in the Freezepoint by using one of the Explorer screens. Here is the Selection Explorer as example, the Option Explorer has identical functionality:

Steltix Version Workbench - Freezepoint Selection Explorer
 

The Explorer screens initially load the Default Freezepoint filtered with the current login environment or pathcode. This Default Freezepoint is meant for ad hoc setup exploration. Formexit Ww Freezepoints will open the Work with Freezepoints screen in which you can secure a Freezepoint through a rowexit in order to protect it against regeneration or purge. In order to load a different Freezepoint, click on the Freezepoint name in the top left of the screen (displayed here as Default) to open the Select Freezepoint screen:

Select the Freezepoint you wish to load in the grid and you will return to the Explorer screen looking like this:

The information bitmap left to the Freezepoint name can be clicked and will open a popup window showing available environment or pathcode details of the loaded Freezepoint content. The grid can be queried using the standard JDE features QBE and Sequencing. The QBE checkbox on the left above the grid will extend the QBE possibilities even more:

1.3 Comparing Freezepoints

From any Explorer screen, formexit Compare (a value for the Environment or Pathcode filter is mandatory when formexit Compare is used) will take the current loaded Freezepoint-Environment/Pathcode combination as one part of the comparison and open the Select Compare Freezepoint screen where you can specify the other part for the comparison:

 

When a valid Freezepoint-Environment/Pathcode combination is specified, the OK button will open the Option (or Selection) Compare screen:

When a compare is requested for the first time, or if one of the Freezepoint-Environment/Pathcode combinations taking part in the comparison has been changed since the last time the comparison was queried, the compare is built asynchronously on screen startup. Using the Find button will update the compare build status, show intermediate results and enable any disabled controls during the compare build when the build has finished. Differences are reported in this screen with color coding. Grid lines displayed in red indicate a difference in values, blue and green grid lines indicate a difference based on version existence. Black lines indicate no difference. Clicking on the ‘Differences based on…’ link opens a screen where you can specify which elements should or should not result in a difference marking for the compare query:

1.3.1 Inline Compare for Project Scope

From the OMW Projects tab of the Version Workbench main screen two rowexits, Option Compare and Selection Compare, offer you instant access to the Option Compare or Selection Compare screen. The comparison will be build using the login environment/pathcode for one side of the comparison and you are asked in a dialog to specify the environment/pathcode for the other side of the comparison. Before the Compare screen is launched, you need to confirm to go ahead with Freezepoint and Compare generation for the number of versions detected in the project content:

1.3.2 Export Versions to Project from Compare Grid selection

Formexit To Project is available from every compare screen to allow for a quick export of the versions in your grid selection to a project:

Project status, ownership and role are not filter enabled; these filter criteria are determined by the Development Configuration setup in combination with the current login environment.

Using the Select button will open the following popup screen to confirm adding or checking out the number of versions found in the compare grid selection to the project.

Back to table of contents