Understanding Integration PeopleCode That Did Not Migrate
This section discusses the reasons why integration events and subscriptions might not successfully migrate to application classes during the upgrade from PeopleTools 8.47 and earlier systems to PeopleTools 8.48 and higher systems and the Deprecated type service operation handler used to manage such PeopleCode.
Reasons Why Integration PeopleCode Does Not Migrate
Integration events and subscriptions might not successfully migrate to application classes for the following reasons:
-
Use of global variables.
-
Use of component variables.
-
Use of constants.
-
Use of local functions.
-
Inability to determine the return type or the return type is incorrect.
Deprecated PeopleCode Handler
The PeopleSoft system creates a deprecated PeopleCode handler for any integration PeopleCode that cannot be migrated to the PeopleTools 8.48 or higher system.
Deprecated handlers enable you to run PeopleTools 8.47 and earlier PeopleCode (subscription or OnRequest). However, PeopleSoft recommends that you correct the PeopleCode and migrate the code into an Application Class type handler for use in the PeopleTools 8.48 or higher system.