- Active Paging Constraints

Active Paging behaviour operates under prescribed circumstances.

The Paging Pre-Display and Active Dynamics enhancements are only available for a pair of cycles in a Screen function where the outer cycle is a ManyTime Flat screen, and it contains one nested Paging Cycle, with no other cycles nested in either, and no fields in the Flat Cycle after the Paging Cycle.

Supported Structure

Unsupported Structures and Constraints

More than one cycle nested in the ManyTime Flat Cycle.
Fields that are part of the Flat Cycle below the nested Paging Cycle.
An Active Paging screen can only be 'LSCALLed' from the Flat Cycle enclosing it. Such an LSCALL performs a Paging Pre-Display. LSCalling an Active Paging screen from elsewhere is not supported and will cause screen corruption. "Falling into" an Active Paging screen, (i.e. the normal PROIV Timing Cycle) is supported, unless the user then clicks in a Parent Cycle field. In this case, the Active Paging Cycle performs like an normal cycle apart from not clearing on exit.
Paging Cycle cannot be a window.
Paging Cycle must allow Lookup Mode for the Paging Pre-Display to work successfully.

Invalid Structures

A valid structure can be made invalid by:

Pasting or adding a Paging Cycle with the Active Paging property set into an invalid position.
Pasting or adding an extra cycle into a Flat Cycle that has a Paging Cycle as a child.
Changing the properties on a Paging Cycle in an invalid structure through editing, or using the Bulk Manipulation tool.

Note: An invalid Paging Cycle behaves like an existing Paging Cycle. Active Paging does not occur but there are no runtime errors.

Comment on this topic

Topic ID: 500549