Change Control Number Facilities (CCN) |
DEVELOPER |
 |
Select Admin from the Developer menu and select the CCN tab.
The PROIV source for 22 standard stub functions, (@VIPSB01 - @VIPSB09, @VIPSB11, @VIPSB13 - @VIPSB20, @VIPSB22 - @VIPSB25), plus three with special uses (@VIPSB10, @VIPSB12, @VIPSB21) is delivered with PROIV Developer.
@VIPSB10 is the CCN tab in PROIV Developer System Admin. As delivered it allows CCN functionality to be switched on or off, and this functionality should not be changed, but you may use the screen for any additional purpose that you wish (e.g. displaying or maintaining data from your Change Control System. This screen is only available to users who are set up as PROIV Developer administrators.
@VIPSB12 is the User CCN screen in the PROIV Developer User Tools tab. It is only made visible if CCN functionality is turned on (via @VIPSB10, above). As delivered it has no functionality, but you may use the screen for any additional purpose that you wish (e.g. displaying or maintaining data from your Change Control System. This screen is available to all PROIV Developer users.
@VIPSB21 is provided as part of the bulk manipulation tool for inclusion of custom update code as a stub link. It has its own set of parameters.
The standard stubs are called from PROIV Developer when actions are performed on PROIV objects in PROIV Developer. These stubs pass data about the action to the developer, and pass back a command that can allow the action or abort it, along with a reference (the CCN), which appears in PROIV Developer. These stubs are not called when maintaining Global Messages, but are called for all other objects.
This allows the developer to link an existing Change Control system into PROIV Developer.
The stubs can be changed in any way, except that the parameter list should remain unchanged.
If CCNs are returned, then List driven actions (including Export), History, and Open object can all be driven from a CCN.
The stubs are not overwritten with new releases of PROIV Developer, but it is possible that parameters that are currently spare may become live. If this occurs, PROIV Developer users are informed of what changes to make if they want the new data being passed.
Topic ID: 500049