Using the Refresh Option

As you develop an Application Engine program, you may be inserting, renaming, and deleting definitions. In a large program, you can easily lose your place or become disoriented. The Refresh option reorders all the nodes for the current definition according to the following logic:

• For standard program definitions, the MAIN section always appears first (Library program types do not contain a MAIN section because they contain only callable sections).

  The remaining sections appear alphabetically by name, which makes it easy to locate a section within the program definition. At runtime, the system runs sections through Call Section actions within steps, not by the order in which the sections are defined.

• Steps are never automatically reordered in the Definition view; at runtime, they run in the sequence in which you defined them.

• Actions are always logically reordered within a step based on their action type, which defines their runtime sequence.

Note:

When you save a modified definition, the system automatically refreshes the view.

Application Engine inserts any delete requests for a given section into the current project, regardless of the Tools, Options setting in Application Designer.

For example, suppose you delete a section node from the current Application Engine program and then you reinsert a section node and rename it the same name as the section you just deleted. The section object is not inserted into the project, regardless of your Tools, Options setting, because a delete action already exists for this object. To resolve this situation, either remove the delete request manually before inserting the new copy request or reset the proper flags manually in the upgrade project that changes the action type from Delete to Copy.