SSOs and the PROIV Timing Cycle |
DEVELOPER |
 |
|
SSOs and the PROIV Timing Cycle |
DEVELOPER |
|
The PROIV Timing Cycle has been updated to support the automatic creation, management and deletion of SSO objects in the following ways:
The PROIV Virtual Machine creates local SSO objects immediately after the completion of the Function Entry Logic. This allows for any setup prerequisites to be executed before object creation.
The PROIV Virtual Machine tears down local SSO objects immediately after the completion of the Function Exit Logic.
Unlike ActiveX controls, SSO objects are available for use by all PROIV Function types and not limited to Screens.
SSO objects created in a caller function may be accessed by a called function by specifying their SSO Tag Names as Input Parameters in an interface map for the called function.
SSO Tag Names cannot be specified as output parameters in a function interface map.
If a PROIV Function is called recursively, SSO objects created by a previous call to a function become inaccessible across recursive calls to the same function. New SSO objects are created by successive calls to that function.
SSO objects created by the current call to a function remain accessible until completion of Function Exit Logic for the current call that was made to that PROIV Function. The calling PROIV function, if there is one, has its’ SSO objects reinstated as it resumes execution following a recursive call.
SSO Tag Names cannot be specified as input parameters to a PROIV task.
Topic ID: 500572