Upgrading from Earlier Releases › Upgrading from CA Plex r5.1 › Case 3: Changes to the Sequence of Events, Subroutines and Collection Points

Case 3: Changes to the Sequence of Events, Subroutines and Collection Points

The sequence of inherited Event constructs and Subroutines can be altered compared to previous releases. Changes to the sequence of Subroutines have no negative consequences for the generated application. In general, this is also true for Event constructs. However, the sequence of Events may be significant if you referenced the same logical event on multiple Event constructs or used an unqualified Event construct. For example:

Events Handler
       Event
           //unqualified event triggered for every event
             Go Sub Generic Event Processing
   Event Delete
            Go Sub Delete Processing
  Event Delete
            Go Sub More Delete Processing

If the previous sequence of Event constructs is different, then the behavior of the generated application will change. In practice, this functionality is rarely exploited and it is even rarer for the inheritance engine changes to cause significant differences in the sequence. As in other cases, such problems can be identified through testing of the generated application, comparisons of generated source or comparisons of action diagram code.

In principle, similar considerations apply to the sequence of inherited code blocks in Collection Points (Pre and Post Points). Testing by CA has not revealed examples of such results but you should be aware that the possibility exists.