Sadly, no.
It used to be the 'recommendation' of 'consultants' that you try and work to a single page at a time. That would mean using emty case statements to provide nesting / commentary as needed, and expanding where you want to follow the storyline
so something like this
> USER: Validate fields
.--
. ...--> F4 for company ?
. ...--> No company - go to select
.
. company number nam *FIELD
. Employment sequence nam *FIELD
. ** - - - - - - - - - - - -
. ...--> Start date check
. ** - - - - - - - - - - - -
. ...--> end date calcs
. ...--> todays date
. ...--> start date check
. ...--> ended date check to start date
. ...--> ended date check to today
Where the --> indicates (to me at least) that there is something worth expanding
if we z into the second of these we get
> --> No company - go to select
.-CASE
¦-DTL.Company number is blank
¦ 006 SEL Co & Pos by name - Company *
'-ENDCASE
an 'empty' case statement gives you the chance to insert a bit of commentary, and not generate a subroutine, whilst encapsulating a lump of code, thus
. > --> example of a case statement
. .-CASE
. ¦-*OTHERWISE
. '-ENDCASE
and you produce these by keying
ICF (enter) (f3) then
io (enter) then
fd (enter) and placing your text fragment. then the code.
the comment lines ** - - - - - are there purely to place markers inthe generated code delimiting a section of code - that 'date checking' one liner probably contains a huge amount of embedded/ generated code, which is nicely abstracted to that one line entry in the 2e code.
- not quite the answer to your direct question, but one method of engineering a way round it.